I believe that OpenJUMP was originally designed with an "MDI" (Multiple Document Interface) architecture, where each "document" was a single Task. I was curious if our porgrammers and users felt that this was a useful concept that we should adhere to. Are supplemental views and dialogs (like the Output Window and the Feature Info Dialog) task centric?
Does it ever make sense to display a window or dialog that isn't related to information in the active Task? I'm curious, because it will change how I choose to integrate a docking window framework into BizzJUMP. I'm thinking that the TaskFrame class is the appropriate parent of the docking window tree. It only makes sense to have the WorkbechFrame as the parent of the dociking window framework if we will be displaying child tabs in the Workbench Frame. There are basically two (2) ways I can approach the docking window framework integration: [1] Make the WorkbenchFrame the parent of the docking window tree. In this scenario tasks would be child tabs of the WorkBenchFrame, and other "views" related to all tasks (if any exist) would also be displayed as tabs. [2] Make the TaskFrame class the parent of the docking window tree. In this scenario tasks would remain in their current implementation as an InternalFrame. Each InternalFrame would be the parent of its own docking window tree. Thank you for your suggestions. The Sunburned Surveyor ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
