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 "Mint"

(Mint is a proposed open source component in the Eclipse Modeling Framework Technology (EMFT) project whose goal is to improve out-of-the-box user experience when developing EMF-based solutions.)
 
m
Line 1: Line 1:
==1. Introduction==
+
==Introduction==
  
Mint is a proposed open source component in the Eclipse Modeling Framework Technology (EMFT) project whose goal is to improve out-of-the-box user experience when developing EMF-based solutions. For the most part, this is accomplished by extending Java Development Tools (JDT) with EMF-specific enhancements.
+
Mint is a proposed open source component in the [http://www.eclipse.org/modeling/emft/ Eclipse Modeling Framework Technology (EMFT)] project whose goal is to improve out-of-the-box user experience when developing EMF-based solutions. For the most part, this is accomplished by extending Java Development Tools (JDT) with EMF-specific enhancements.
  
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process document) and is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment on and/or join the component. Please send all feedback to the eclipse.technology.emft newsgroup (please prefix the subject with [mint]).  
+
This proposal is in the Project Proposal Phase (as defined in the [http://www.eclipse.org/projects/dev_process/development_process.php Eclipse Development Process] document) and is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment on and/or join the component. Please send all feedback to the [news://news.eclipse.org/eclipse.technology.emft eclipse.technology.emft] newsgroup (please prefix the subject with [mint]).  
  
==2. Background==
+
==Background==
  
 
The EMF SDK comes with basic structured editors that allow for development of Ecore models and subsequent generation of related Java code. Furthermore, EMF supports creating Ecore models from Javadoc-annotated source code. However, there are opportunities for tighter integration with existing development tools, particularly JDT, given EMF's meta-data-driven nature. While providing a full-scale model-driven application development environment is not part of the EMF's charter (rather, it is left up to extenders and add-on providers), we believe that several relatively small enhancements would go a long way toward improving out-of-the-box experience when developing EMF-based applications.
 
The EMF SDK comes with basic structured editors that allow for development of Ecore models and subsequent generation of related Java code. Furthermore, EMF supports creating Ecore models from Javadoc-annotated source code. However, there are opportunities for tighter integration with existing development tools, particularly JDT, given EMF's meta-data-driven nature. While providing a full-scale model-driven application development environment is not part of the EMF's charter (rather, it is left up to extenders and add-on providers), we believe that several relatively small enhancements would go a long way toward improving out-of-the-box experience when developing EMF-based applications.
  
==3. Scope==
+
==Scope==
  
 
The functionality initially contributed:
 
The functionality initially contributed:
Line 25: Line 25:
 
Note that the scope can be further augmented as warranted by community interest.
 
Note that the scope can be further augmented as warranted by community interest.
  
==4. Description==
+
==Description==
  
 
The initial contribution provides usability enhancements in the following areas:
 
The initial contribution provides usability enhancements in the following areas:
Line 39: Line 39:
 
# Ecore-specific Java 5 Annotations, designed to closely resemble the Javadoc-based annotations currently in use, will allow registered annotation processors to translate annotation changes to their corresponding Ecore/GenModels. This will automate the model-reload-generate cycle that is frequently employed when developing EMF-based applications (especially when annotated Java code is used as the model source).
 
# Ecore-specific Java 5 Annotations, designed to closely resemble the Javadoc-based annotations currently in use, will allow registered annotation processors to translate annotation changes to their corresponding Ecore/GenModels. This will automate the model-reload-generate cycle that is frequently employed when developing EMF-based applications (especially when annotated Java code is used as the model source).
  
==5. Relationship with other Eclipse-based Projects==
+
==Relationship with other Eclipse-based Projects==
  
 
Initially, Mint builds upon the functionality provided by the EMF project itself. However, it is envisioned that Mint could benefit from contributions made by the Search component, particularly in the area of Java search integration.
 
Initially, Mint builds upon the functionality provided by the EMF project itself. However, it is envisioned that Mint could benefit from contributions made by the Search component, particularly in the area of Java search integration.
Line 47: Line 47:
 
On the whole, features and enhancements contributed by Mint should be applicable to other projects that base their models around Ecore, such as the Graphical Modeling Framework (GMF). Model-specific solutions can be developed when necessary (e.g., GMF-specific navigation actions for the various GMF editors).
 
On the whole, features and enhancements contributed by Mint should be applicable to other projects that base their models around Ecore, such as the Graphical Modeling Framework (GMF). Model-specific solutions can be developed when necessary (e.g., GMF-specific navigation actions for the various GMF editors).
  
==6. Organization==
+
==Organization==
  
===a. Initial committers===
+
===Initial committers===
  
 
Peter Nehrer, [http://www.eclipticalsoftware.com Ecliptical Software Inc.]
 
Peter Nehrer, [http://www.eclipticalsoftware.com Ecliptical Software Inc.]
  
===b. Code contributions===
+
===Code contributions===
  
 
* [http://www.eclipticalsoftware.com/emf/#jdt JDT Extensions for EMF] from Ecliptical Software Inc.
 
* [http://www.eclipticalsoftware.com/emf/#jdt JDT Extensions for EMF] from Ecliptical Software Inc.
  
===c. Interested parties===
+
===Interested parties===
  
 
* Ed Merks, IBM
 
* Ed Merks, IBM
Line 64: Line 64:
 
Interested parties are welcome to add themselves to the list above as interested parties or to suggest changes to this document.
 
Interested parties are welcome to add themselves to the list above as interested parties or to suggest changes to this document.
  
===d. Developer community===
+
===Developer community===
  
 
The initial set of committers is expected to grow given the component's focus on improving EMF-based development in general. Any EMF user with ideas on how to improve EMF-related tooling is encouraged to contribute.
 
The initial set of committers is expected to grow given the component's focus on improving EMF-based development in general. Any EMF user with ideas on how to improve EMF-related tooling is encouraged to contribute.
  
==7. Tentative Plan==
+
==Tentative Plan==
  
 
* 2007-11: Initial release to EMF team for study and feedback
 
* 2007-11: Initial release to EMF team for study and feedback

Revision as of 22:29, 23 October 2007

Introduction

Mint is a proposed open source component in the Eclipse Modeling Framework Technology (EMFT) project whose goal is to improve out-of-the-box user experience when developing EMF-based solutions. For the most part, this is accomplished by extending Java Development Tools (JDT) with EMF-specific enhancements.

This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process document) and is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment on and/or join the component. Please send all feedback to the eclipse.technology.emft newsgroup (please prefix the subject with [mint]).

Background

The EMF SDK comes with basic structured editors that allow for development of Ecore models and subsequent generation of related Java code. Furthermore, EMF supports creating Ecore models from Javadoc-annotated source code. However, there are opportunities for tighter integration with existing development tools, particularly JDT, given EMF's meta-data-driven nature. While providing a full-scale model-driven application development environment is not part of the EMF's charter (rather, it is left up to extenders and add-on providers), we believe that several relatively small enhancements would go a long way toward improving out-of-the-box experience when developing EMF-based applications.

Scope

The functionality initially contributed:

  1. Java model decoration
  2. Structured viewer filters for generated Java code
  3. Java search integration
  4. GenModel-to-Java navigation actions
  5. Java Editor enhancements

Additional functionality considered:

  1. Logical structure providers for debugging
  2. Java refactoring integration
  3. Java 5 Annotations and annotation processors

Note that the scope can be further augmented as warranted by community interest.

Description

The initial contribution provides usability enhancements in the following areas:

  1. Structured viewers displaying Java elements, such as Java Editor's Content Outline or the Package Explorer, can be configured to highlight generated Java members (such as types, methods, and member variables). Additionally, generated members that were explicitly customized can also be highlighted.
  2. Viewer filters are provided to selectively hide generated, customized, or non-generated members can be applied to structured viewers displaying Java elements (such as those mentioned above).
  3. Searching for Java element references (currently packages and types) reports GenModel elements from which the elements were generated. For instance, searching for references to a generated factory implementation reports the GenModel package from which the factory was generated.
  4. Default GenModel editor provides additional context menu items that allow for navigation to corresponding generated types. For instance, right-clicking an GenClass allows one to open the generated interface, implementation class, item provider, and test case (if any).
  5. Java Editor allows for one-click customization of generated method. That is, right-clicking a generated method and selecting Source -> Customize EMF-Generated method creates a corresponding *Gen() method and annotates the original as @generated NOT. This is a common decoration pattern that allows for easy re-use of generated code in customized methods.

Additional enhancements considered for implementation will cover the following areas:

  1. Ecore-aware logical structure providers, used by the Debug framework to allow the user to view structured data in a more abstract form, will display EObject or Resource containment trees in a more succinct manner (for easy navigation). Alternatively, the data may be displayed according to the hierarchy provided by the registered item provider adapter factory.
  2. Java refactoring participants, which are invoked whenever a Java element is being refactored, may be able effect the corresponding refactoring on the Ecore/GenModel. This is particularly applicable to cases where the Ecore model is generated from annotated Java code.
  3. Ecore-specific Java 5 Annotations, designed to closely resemble the Javadoc-based annotations currently in use, will allow registered annotation processors to translate annotation changes to their corresponding Ecore/GenModels. This will automate the model-reload-generate cycle that is frequently employed when developing EMF-based applications (especially when annotated Java code is used as the model source).

Relationship with other Eclipse-based Projects

Initially, Mint builds upon the functionality provided by the EMF project itself. However, it is envisioned that Mint could benefit from contributions made by the Search component, particularly in the area of Java search integration.

Furthermore, incremental code generation based on Java 5 Annotations may be possible with an annotation processor utilizing the JET2 functionality. More investigation is required to determine if this is feasible and how it could be implemented.

On the whole, features and enhancements contributed by Mint should be applicable to other projects that base their models around Ecore, such as the Graphical Modeling Framework (GMF). Model-specific solutions can be developed when necessary (e.g., GMF-specific navigation actions for the various GMF editors).

Organization

Initial committers

Peter Nehrer, Ecliptical Software Inc.

Code contributions

Interested parties

  • Ed Merks, IBM
  • Lucas Bigeardel

Interested parties are welcome to add themselves to the list above as interested parties or to suggest changes to this document.

Developer community

The initial set of committers is expected to grow given the component's focus on improving EMF-based development in general. Any EMF user with ideas on how to improve EMF-related tooling is encouraged to contribute.

Tentative Plan

  • 2007-11: Initial release to EMF team for study and feedback
  • 2007-12: First public release for community study

References

  1. JDT Extensions for EMF by Ecliptical Software Inc.

Back to the top