PTP/planning/2.0/TODO

1. Need to fix model events:
   • Random node icons change to running
   • Remove all terminated jobs doesn't remove processes from nodes in UI
   • What needs to happen for handleRuntimeShutdownStateEvent in AbstractRuntimeResourceManager?
2. Dynamic launch page problems.
3. What to do about errors. e.g. if job submission fails?
4. Asynchronous job submission
5. Asynchronous debug launch
6. Two names showing up in machine properties
7. NPE when removing terminated jobs
8. Launch manually option does not work.
9. "Not Already Started" message
10. Unable to find resource manager factory
11. Deal with stdout.
12. Cancel RM start if there is an error
13. ResourceManager view doesn't display until all RM's have started.
14. Delay in starting RM
15. Fix UI views (maybe RM view should be used to select other views)
16. Unique model ID's using RM type + RM name
17. Ability to edit a resource manager configuration
18. Preference to automatically hide the RM/queue dropdowns in the parallel tab if there is only one active RM and the RM only has one queue.
19. Add new process icon to indicate stdout available
20. The progress view doesn't work properly with 2 or more RMs.
21. Allow commands to be extended. e.g. The INIT command should be extensible to allow additional attributes to be supplied. This will require providing a hook (extension point?) into the RM package when commands are created.
22. Add a field to the proxy preference page that allows arguments to be supplied to the proxy on launch.
23. Provide a per-job console that will allow the user to supply standard input to the executing application. The console will be enabled using a launch configuration option (default will be no console). The console will redirect stdin/stdout to the proxy via a separate socket connection. It will be up to the proxy to ensure that the I/O is sent/received from the correct job, and also which processes receive stdin (if required, this can be supplied as a RM-specific launch attibute). This will be separate to the process view display of stdout.
24. Add a message view. This will display error messages that are sent from the proxy (regardless of other action taken as a result of the message). Messages will be categorized into the following levels: FATAL, ERROR, WARNING, and INFO. Colors will be used to distinguish the different level.
25. Event throttling. This will be implemented in the proxy base class, and will provide automatic flow control to prevent event overload of the UI. Eclipse will queue events on arrival. If events of a particular type reach a high water make on the event queue, a STOP_EVENTS command will be sent to the proxy. The STOP_EVENTS command will only apply to the event type. Once the events have been processed, a START_EVENTS command will be sent.
26. The #defines used by the C proxy code to match attribute ID's will be moved to a common header file for use by other proxy implementations.
27. The totalview startup mechanism will be implemented in the PTP debugger.