Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Buckminster Project/Buckminster Roadmap"

(Not yet prioritized items to complete before the 1.0 final release. Completion Q2 2006)
Line 2: Line 2:
 
=== Buckminster Milestone 3. Completion Q1 2006 ===
 
=== Buckminster Milestone 3. Completion Q1 2006 ===
  
* {{Strikeover|'''-Clean up and restructure-''' [[Component Specification|CSPEC]] '''and some related mechanisms'''}}
+
* {{Strikeover|'''-Clean up and restructure-''' [[Buckminster Component Specification|CSPEC]] '''and some related mechanisms'''}}
 
** {{Strikeover|Remove 'targets' concept (outdated)}}
 
** {{Strikeover|Remove 'targets' concept (outdated)}}
 
** {{Strikeover|Remove use of 'buckminster' URL as a query vehicle (only internally used and is better modeled differently)}}
 
** {{Strikeover|Remove use of 'buckminster' URL as a query vehicle (only internally used and is better modeled differently)}}
 
** {{Strikeover|Add component name/version attributes to the data}}
 
** {{Strikeover|Add component name/version attributes to the data}}
*** {{Strikeover|''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 [[Component Query|CQUERY]] advisor nodes''.}}
+
*** {{Strikeover|''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 [[Buckminster Component Query|CQUERY]] advisor nodes''.}}
* '''Complete the [[Component Specification|CSPEC]] and associated functionality'''
+
* '''Complete the [[Buckminster Component Specification|CSPEC]] and associated functionality'''
** {{Strikeover|Define [[CSPEC Action|actions]] XML & Model/interface (including persistence model}}
+
** {{Strikeover|Define [[Buckminster CSPEC Action|actions]] XML & Model/interface (including persistence model}}
 
** {{Strikeover|Implement action driven evaluation using actors}}
 
** {{Strikeover|Implement action driven evaluation using actors}}
 
** {{Strikeover|Improve CSPEC generators to include actions. Build of PDE artifacts in special}}
 
** {{Strikeover|Improve CSPEC generators to include actions. Build of PDE artifacts in special}}
Line 20: Line 20:
  
 
* Better editors for several basic formats (tentative: use Eclipse Forms)
 
* Better editors for several basic formats (tentative: use Eclipse Forms)
** [[Resource Map|RMAP]] Editor
+
** [[Buckminster 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)
+
** [[Buckminster 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)
+
** [[Buckminster Component Query|CQUERY]] Editor (rewrite of the existing editor to conform to Forms)
  
 
* '''Create Trailblazers for common usecases'''
 
* '''Create Trailblazers for common usecases'''
Line 36: Line 36:
 
* '''Disconnect headless entirely from Buckminster, possibly offer for general RCP use'''
 
* '''Disconnect headless entirely from Buckminster, possibly offer for general RCP use'''
 
** Turn into article: 'Implementing a headless framework' and 'Implementing a headless progress monitor'
 
** Turn into article: 'Implementing a headless framework' and 'Implementing a headless progress monitor'
 +
[[Category:Buckminster]]

Revision as of 11:34, 21 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 actors
    • Improve CSPEC generators to include actions. Build of PDE artifacts in special
    • Update the documentation to reflect new generation and CSPEC elements
  • 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)
    • RMAP Editor
    • CSPEC Editor (more generally expressed: a 'Buckminster Component Editor' that is extendable and is the umbrella editor for all component aspects)
    • CQUERY Editor (rewrite of the existing editor to conform to 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
    • Make headless core product much smaller
    • Improve 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'

Back to the top