There is some code in OpenJUMP that "listens" for child components to be added to the Workbench in order to detect when a Task has been added. I think this is likely a violation of the "separation of GUI and model" principle. (Unless we view a task solely as a GUI component.)
I wonder if there would be objections to adding an event to signify task creation that did not depend on listening for Swing operations in this way. The event could be fired by a new class called TaskFacotry or something similar. The TaskFactory class would call the createTask method of the WorkbenchFrame and then fire the event. This would allow us to do some neat things in the future, such as potentially add a task but delay displaying it on the workbench. It would also allow us to immediately decouple "listeners" for task creation from the GUI. At some point I'd like to add a plug-in for task management, which would use this listening mechanism. I also already have code in the pluggable rendering system I designed that could be decoupled in this way. At any rate, I wonder if there would be strong opposition to adopting this type of change in the core, if I worked it up. If there are good reasons not to do this, I won't even consider it. The Sunburned Surveyor ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
