Community
Participate
Working Groups
I don't see any reason why the primary method for creating perspectives should be via an IPerspectiveFactory. Creating a perspective within the application (whether Eclipse or an RCP app) is more more efficient, more intuitive and has less potential for bugs. Since perspectives are currently read from an XML file, it doesn't seem like it would be too much of a stretch to allow an XML file to be used as the definition for a perspective in the org.eclipse.ui.perspectives extensions point. Additionally, if the "Save As..." option could (optionally) be directed to a seperate XML file (rather than embedding it in the worbench settings xml file), developers could create/modify perspectives easily. No matter how good the layout API, it just can't compete with me running the app, dragging and dropping views exactly where I want them, and clicking "save as". This also opens the door for users to pass perspectives around via an XML file, but I don't think that's as important.
Nice idea.
Sounds like your "tree" PW
Yes, one of the most 'model-ish' parts of the presentation is the Perspective which does indeed -simply- run off of its defined XML spec. At minimum Export/Import should be fairly easy. I'm less sure that we can produce a schema that would cover the current XML format as defined but I haven't looked...
Removing outdated target milestone.