| Issue | Description | Comment from Core team (Tonda) |
| 89852 | API which notifies new events in the output windows | Not planned. Problematic because Output Window APIs are not easily extensible. |
| 28862 | Add in-line error feature to API | Not planned at the moment, this is not a priority issue; also UI spec would have to be created first covering specific real use cases |
| 88775 | Don't save project properties if they were not changed | Not planned. Rather a P3 performance bug, not an enhancement, and it requires large changes. |
| 33162 | Allow to listen on subtrees | PLANNED, Radek Matous will work on it, as well as on "listening on non-existing files". |
| 60862 | Provide an API for adding icon in the output window tab | Not planned. Problematic because Output Window APIs are not easily extensible. |
| 70280 | Review of actions work | Not planned. Strong argument would have to be brought to us to reconsider. |
| 90508 | Add logging level based message filtering | Not planned. This is not realistic to do in a general way in Output. You should do it in your code. Adding buttons to Output is possible via APIs. After you do the filtering of the stream, you will reload it in the Output. |
| 90512 | Add support for creating links | Not planned. This requirement goes against the philosophy of Output Window, which is basically only a fast viewer of possibly very large stream. Output Window does not know anything about the semantics of the text it displays. |
| 90513 | Add support for displaying process output and log files. | Not planned. Sounds like you need to create a utility class on your side, to handle the many log files you have in web/j2ee areas. |