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"

Line 1: Line 1:
 
{{Backlink|Buckminster Project}}
 
{{Backlink|Buckminster Project}}
  
=== Not yet prioritized items to complete before the 1.0 final release. Completion Q4 2006 ===
+
Through 2007, the Project will aim for a significant elaboration or extension of functionality at roughly three-month intervals.   Our roadmap for the next 9-12 months appears below.  The roadmap is currently organized thematically, and the project team is currently considering re-factoring the roadmap so that each theme can be advance in parallel.
  
* Better editors for several basic formats (tentative: use Eclipse Forms)
+
==Milestone 1.1
** [[Buckminster Resource Map|RMAP]] Editor
+
===Theme: Usability
** [[Buckminster 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 Query|CQUERY]] Editor (rewrite of the existing editor to conform to Forms)
+
  
* '''Create Trailblazers for common usecases'''
+
*Graphical editors for the RMAP and CSPEC
* '''Replace metadata persistence mechanism'''
+
**”Form” style editors with Eclipse look and feel
** Use a DB (e.g. Derby) instead of XML
+
**Intuitive and with extensive help
* '''Integrate full Manifest services (checksums etc) into Bill-of-materials'''
+
           
* '''General refactoring'''
+
*Graphical representation of a Component Model
** {{Strikeover|Make headless core product much smaller}}
+
**Can view a complete model spanning many components
** Improve separation of concern
+
**Should be zoomable
  
=== Misc possibilities - undecided and no timeframe ===
+
*Graphical representation of the resolve process
 +
**Provides feedback to the user during the resolve process
 +
**The graph of chosen paths can be persisted
  
* '''Disconnect headless entirely from Buckminster, possibly offer for general RCP use'''
+
==Milestone 1.2
** Turn into article: 'Implementing a headless framework' and 'Implementing a headless progress monitor'
+
===Theme:  Support for wider range of component models
[[Category:Buckminster]]
+
*WAR and EAR recognition
 +
**project models produced by CSPEC actions
 +
**Reuse models supported by Eclipse Web Tools Project
 +
**Target common servers. Tomcat, Jboss, JOnAS
 +
**Commercial servers, such as Websphere, Weblogic, Oracle
 +
*Support for Ivy projects
 +
*Support for Java Modules (JSR277), subject to JSR finalization
 +
 
 +
==Milestone 1.3
 +
===Theme: Support for additional languages
 +
*PHP/Python/Perl, C
 +
**Repository provider for CPAN
 +
**Support LAMP (Linux Apache MySQL PHP) component stack
 +
   
 +
*Additional component models
 +
**Recognize CDT generated projects
 +
**Perhaps recognize automake/auotconf/configure projects

Revision as of 20:58, 5 October 2006

< To: Buckminster Project

Through 2007, the Project will aim for a significant elaboration or extension of functionality at roughly three-month intervals. Our roadmap for the next 9-12 months appears below. The roadmap is currently organized thematically, and the project team is currently considering re-factoring the roadmap so that each theme can be advance in parallel.

==Milestone 1.1 ===Theme: Usability

  • Graphical editors for the RMAP and CSPEC
    • ”Form” style editors with Eclipse look and feel
    • Intuitive and with extensive help
  • Graphical representation of a Component Model
    • Can view a complete model spanning many components
    • Should be zoomable
  • Graphical representation of the resolve process
    • Provides feedback to the user during the resolve process
    • The graph of chosen paths can be persisted

==Milestone 1.2 ===Theme: Support for wider range of component models

  • WAR and EAR recognition
    • project models produced by CSPEC actions
    • Reuse models supported by Eclipse Web Tools Project
    • Target common servers. Tomcat, Jboss, JOnAS
    • Commercial servers, such as Websphere, Weblogic, Oracle
  • Support for Ivy projects
  • Support for Java Modules (JSR277), subject to JSR finalization

==Milestone 1.3 ===Theme: Support for additional languages

  • PHP/Python/Perl, C
    • Repository provider for CPAN
    • Support LAMP (Linux Apache MySQL PHP) component stack
  • Additional component models
    • Recognize CDT generated projects
    • Perhaps recognize automake/auotconf/configure projects

Back to the top