Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Buckminster Project/Buckminster Roadmap"
Line 1: | Line 1: | ||
+ | {{Backlink|Buckminster Project}} | ||
=== Buckminster Milestone 3. Completion Q1 2006 === | === Buckminster Milestone 3. Completion Q1 2006 === | ||
Line 17: | Line 18: | ||
* Better editors for several basic formats (tentative: use Eclipse Forms) | * Better editors for several basic formats (tentative: use Eclipse Forms) | ||
− | |||
** [[Resource Map|RMAP]] Editor | ** [[Resource Map|RMAP]] Editor | ||
− | |||
** [[Component Specification|CSPEC]] Editor (more generally expressed: a 'Buckminster Component Editor' that is extendable and is the umbrella editor for all component aspects) | ** [[Component Specification|CSPEC]] Editor (more generally expressed: a 'Buckminster Component Editor' that is extendable and is the umbrella editor for all component aspects) | ||
− | |||
** [[Component Query|CQUERY]] Editor (rewrite of the existing editor to conform to Forms) | ** [[Component Query|CQUERY]] Editor (rewrite of the existing editor to conform to Forms) | ||
Revision as of 19:02, 8 September 2006
< To: Buckminster Project
Buckminster Milestone 3. Completion Q1 2006
- -Clean up and restructure- CSPEC and some related mechanisms
- Remove 'targets' concept (outdated)
- Remove use of 'buckminster' URL as a query vehicle (only internally used and is better modeled differently)
- Add component name/version attributes to the data
- In principle this is redundant information, but there are times when it can be necessary and/or useful. However, it must be described on exactly when and how the data is used and what happens when it conflicts with implicit information. There are also implications for CQUERY advisor nodes.
- Complete the CSPEC and associated functionality
- Define actions XML & Model/interface (including persistence model
- Implement action driven evaluation using performers
- A basic 'update site' provider
- Headless/packaging docs
- Generally clean up
- Add sections on calling directly from Java and from Ant
Not yet prioritized items to complete before the 1.0 final release. Completion Q2 2006
- Better editors for several basic formats (tentative: use Eclipse Forms)
- Create Trailblazers for common usecases
- Replace metadata persistence mechanism
- Use a DB (e.g. Derby) instead of XML
- Integrate full Manifest services (checksums etc) into Bill-of-materials
- General refactoring
- Makes headless core product much smaller
- Improves separation of concern
Misc possibilities - undecided and no timeframe
- Disconnect headless entirely from Buckminster, possibly offer for general RCP use
- Turn into article: 'Implementing a headless framework' and 'Implementing a headless progress monitor'