To Do List

• 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
• Implement correctly the Preferences
• Solve this bug, that affects the diagram editor
• Automated test coverage (JUnit)

• 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)

• Headless (non-graphical) build for the plugin

• 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

• RCP build of a standalone modeling application equivalent to ArgoUML
• Remove all the Swing Dialogs
• Multiple editors (an editor for each model) / this implies multiple model
• Multiple editors (an editor for each diagram), do we want this?
• Speed up initialization (not much can be done here, maybe a more lightweight model, and to split the plugin)

• 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
• Add extension points so that other users/developers can extend the functionality of this plugin

Completed ToDos

• 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?