Community
Participate
Working Groups
In order to provide a "dogfooding" scenario, Vex should be able to edit the Eclipse project plan (see http://wiki.eclipse.org/Development_Resources/Project_Plan). A plug-in should be created which contains the plan.xsd, a CSS stylesheet and the configuration of Vex. The CSS stylesheet should reuse the CSS from the plug-in org.eclipse.vex.xhtml.
The plan.xsd references the xhtml1-* schema. Therefor the schema should be available locally. For example in the WST standard schema plug-in would be an apropriate place to contain a local copy of the XHTML schema (see bug 366467).
I'm definitely interested to see your results. Be advised that--anecdotally--committers don't seem to be interested in IDE-based tools for editing Eclipse project-specific information. You should also be aware that I have generating project plans based on information specified in the portal replacement in plan for the new project management infrastructure (see Bug 366479).
(In reply to comment #2) > I'm definitely interested to see your results. > > Be advised that--anecdotally--committers don't seem to be interested in > IDE-based tools for editing Eclipse project-specific information. I am totally aware of that, and I am no exception to this rule. > > You should also be aware that I have generating project plans based on > information specified in the portal replacement in plan for the new project > management infrastructure (see Bug 366479). Anyway, the project plan XML is a good real-world example for the use of multiple schemas in one document.
Just added the new plug-in org.eclipse.vex.projectplan to our feature. It is possible to open and edit an existing project plan. The creation of a new project plan is still work in progress.
Implemented the creation of new documents based on XML schema, so a new project plan can now be created using the "New Document Wizard".