To Do List
Help finish EUML model subsystem (UML 2.x using Eclipse UML2 plugins). This is shared with !ArgoUML, but arguably more important for ArgoEclipse since UML2/EMF support is needed for interoperability with other Eclipse plugins.
Reverse engineering Eclipse resources in ArgoEclipse;
- Remove Eclipse unused menus
- Split some actions in global actions, available also when the editor isn't active;
- Add underscore shortcuts ( _ ) to the menus
Finish implementation of ArgoEclipse Preferences tabs
- Solve this bug, that affects the diagram editor
- Automated test coverage - particularly for GUI components
The possibility to drag and drop eclipse resources into ArgoEclipse
Key shortcuts (eg. the Delete key is used in ArgoUML to delete targets, this should be available in ArgoEclipse too)
Some other default Eclipse actions should be implemented: Eclipse navigation instead of ArgoEclipse navigation (back and forward actions), ArgoUML properties should be a page in Preferences
- Convert ArgoUML modules to Eclipse extensions - especially for the common case of code generation and reverse engineering
- Add extension points so that other users/developers can extend the functionality of this plugin
- Replace all Swing Dialogs with SWT equivalents
- Multiple editors (one editor per project/model) This implies support for multiple open projects in ArgoUML.
- Multiple editors (one editor per diagram), do we want this?
- Speed up initialization. This requires reworking various ArgoUML components to not require all initialization to be done first (ie better use of lazy initialization).
Remove ProjectBrowser dependencies
- The possibility of ArgoUML to use streams instead of java.io.Files, this way it will be easier to interact with Eclipse the proper way, it will be possible to open resources over networks or Internet
Implement New Wizard
Implement Export Wizards
Implement Import XMI
Implement Import Sources
Break Model classes into multiple model classes
Review the Model Classes and the GUI classes, review the implementation
Split the plugin in more plugins
RCP application vs. ArgoEclipse plugin, should be different? The ArgoEclipse plugin will use Eclipse plugins that shouldn't be in an RCP application?
- --RCP build of a standalone modeling application equivalent to ArgoUML--
- --Headless (non-graphical) build for the plugin--