It seems (as I suspected) that we all have different opinions on the docking window frameworks that are available. No doubt they all have there own advantages and disadvantages. When you boil it down, I suppose that we really have two (2) decisions to make:
[1] Do we want to integrate a docking window framework into OpenJUMP? [2] Which docking window framework do we want to use? I think we may need to give the interested parties some more time to review the available frameworks before we make a decision. However, I would like to make the following offer: If the group decides to introduce a docking window framework into the OpenJUMP core (which I think should be handled by an informal vote) I would be willing to do the following: - Completely integrate the InfoNode docking window framework into a branch of the OpenJUMP SVN for review and testing by other developers and users. - Configure the layout of the new TaskFrame as desired by the majority of the users. - Complete the conversion of the attribute table, output window, and info window to the docking window framework. If the group decides to use another docking window framework, I would be willing to do the following: - Rip the InfoNode docking window framework code out of BizzJUMP, and use whatever the rest of the OpenJUMP community is using. - Contribute bug patches and improvements to the docking window framework integration and assist with the conversion of the attribute window, output window, and info window. Having said all that, I don't know that our choice of a docking window framework makes a huge difference to the end user. I believe the basic functionality will remain the same. Please remember that I have already been working with the InfoNode API, and have completed at least a partial integration. If there is not a really good reason to use another framework I'd appreciate it if the group could build on my existing work. If there are strong opinions about using another framework, I would hope the proponents of the framework would be willing to put forth the effort needed to complete the integration. As always, the thing we lack most is developer time. I don't want to pee in anyone's bowl of cheerios, I'm just trying to save myself some wasted man hours. When it's all said and done, its worth the sacrifice to me to use whatever docking window framework the community decides to use, even if it means undoing some of my effort so far. I'd like to keep BizzJUMP synched as closely as I can to OpenJUMP. The Sunburned Surveyor ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
