Jump to: navigation, search

Difference between revisions of "MoDisco/Wishlist"

(Miscelaneous)
 
(4 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
== Infrastructure ==
 
== Infrastructure ==
 
===Model Browser===
 
===Model Browser===
* Externalize the TreeView, the ContentProvider. This is necessary to be able to use the browser within CNF.
 
* Have an option on a link to display the children directly under the parent, without the node corresponding to the link. This is necessary to be able to use the browser within CNF.
 
* Possibility to customize the left panel to hide some metaclasses
 
 
* Possibility to give parameters to queries executed from the browser
 
* Possibility to give parameters to queries executed from the browser
 
* The concept of "profile" to group a list of Facets and UICustomizations (to be able to apply them at once).
 
* The concept of "profile" to group a list of Facets and UICustomizations (to be able to apply them at once).
* Possibility to modify the model from the browser (add/remove children)
+
* Refactoring writing facility : to be able to register successive user actions in Model Browser (attributes modifications, drag and drop, ...) and to automatically traduce them in an ATL (or Java) file (in generalizing : an action on an instance will become a rule on the associated metaclass). It is a kind of macro registering mode just as in VBE (Word, Excel, ...).
  
 
===Discovery Manager===
 
===Discovery Manager===
Line 14: Line 11:
 
* A "global" discoverer which automatically detects from a project which resources can be analyzed by available discovers. The result could be displayed in a wizard which allows selecting the discoverers to launch.
 
* A "global" discoverer which automatically detects from a project which resources can be analyzed by available discovers. The result could be displayed in a wizard which allows selecting the discoverers to launch.
 
* Add a generic parameter to manage an input monitor (IProgressMonitor). Goal is to be able to manage cancel action when a discovery process has been correctly encapsulated into a Job. -> implies to refactor existing discoverers to check cancel flag.
 
* Add a generic parameter to manage an input monitor (IProgressMonitor). Goal is to be able to manage cancel action when a discovery process has been correctly encapsulated into a Job. -> implies to refactor existing discoverers to check cancel flag.
 +
* A parameter to specify the destination of the result
  
===Miscelaneous===
+
===Miscellaneous===
 
* Provide a MoDisco perspective
 
* Provide a MoDisco perspective
 
<br>
 
<br>
  
 
== Technologies ==
 
== Technologies ==
===A J2EE component===
+
 
* metamodels and discoverer for web.xml
+
* metamodel and discoverers for configuration files for main frameworks(Struts, JSF, Hibernate, Spring, Maven, ...)
+
 
===An Eclipse component===
 
===An Eclipse component===
 
* a metamodel of an Eclipse project
 
* a metamodel of an Eclipse project
 
* a discoverer to create a model out of an Eclipse project
 
* a discoverer to create a model out of an Eclipse project
===A JSP component===
 
* a metamodel of a JSP
 
* a discoverer to create a model out of a JSP
 
  
 
<br>
 
<br>

Latest revision as of 03:26, 22 January 2012

This page lists things people would like to see addressed/fixed in MoDisco.

Infrastructure

Model Browser

  • Possibility to give parameters to queries executed from the browser
  • The concept of "profile" to group a list of Facets and UICustomizations (to be able to apply them at once).
  • Refactoring writing facility : to be able to register successive user actions in Model Browser (attributes modifications, drag and drop, ...) and to automatically traduce them in an ATL (or Java) file (in generalizing : an action on an instance will become a rule on the associated metaclass). It is a kind of macro registering mode just as in VBE (Word, Excel, ...).

Discovery Manager

  • A wizard to create "Discovery" project (plug-in project, with dependencies to modisco.common.core and to modisco.discoverersmanager)
  • A "global" discoverer which automatically detects from a project which resources can be analyzed by available discovers. The result could be displayed in a wizard which allows selecting the discoverers to launch.
  • Add a generic parameter to manage an input monitor (IProgressMonitor). Goal is to be able to manage cancel action when a discovery process has been correctly encapsulated into a Job. -> implies to refactor existing discoverers to check cancel flag.
  • A parameter to specify the destination of the result

Miscellaneous

  • Provide a MoDisco perspective


Technologies

An Eclipse component

  • a metamodel of an Eclipse project
  • a discoverer to create a model out of an Eclipse project


Use cases

  • M2M heuristics in existing Java->UML chain for filtering Java classes/interfaces and obtain lightweight UML models from huge Java legacy (criteria : util classes, ihm classes, low references/lines number, ... etc)
  • JUnit 3 -> JUnit 4 automated refactoring