GSoC 2008 ArgoEclipse Week 2 Status Report *** Achieved ***
* Resolved Issue 34 - Opening two editors causes exception When the user attempts to open a second diagram editor they are now told that only one Diagram editor may be opened at once and asked if they would like to close the other editor. If they choose to close the other editor it is saved (if it is dirty) and closed, allowing the new editor to be opened. If they choose not to close the other editor, a PartInitException is thrown, and a dialog is shown to the user telling them why the editor could not be opened, additionally the Eclipse error editor is shown. It seems that there is no way to actually stop the editor from being opened at all. * Resolved Issue 33 - Double clicking attempts to open new editor when one already ArgoEditorInputs with the same Paths are now considered equal. This allows Eclipse to locate the existing editor and bring it to the front instead of attempting to open a new editor. * Resolved Issue 28 - OCL error when creating new project The NewFileWizard was calling Actions.getInstance().getActionNew().run() to create the project. The Action returned is a HybridAction, HybridActions were recently modified so that all the code within their run() methods is run on the Swing Event Dispatch thread async (EventQueue.invokeLater()). This was causing it to return immediately, and then the Wizard would open the DiagramEditor, which in turn would attempt to load the project which doesn't actually exist yet because the code to create it was called async from the Action. The wizard no does these actions itself instead of relying on an action to do it. * Resolved Issue 22 - Duplicate Edit/Select menu Removed the actionSet extension which was duplicating a menu added by the editors action bar contributor. Resolved Issue 18 - Provide shortcut new Argo file The ArgoEclipse perspective now contributes a shortcut to the new Argo File wizard to the New menu when the perspective is active. * Modified the PersistenceManage removing its dependency on Swing's JOptionPane. Instead the ProjectBrowser is no responsible for showing the confirmation dialog on the Swing side and the DiagramEditor is responsible for showing it on the SWT side. * Modified the ArgoProject class. It's save methods no longer simply call through to the ProjectBrowser implementations. Instead ArgoProject now implements the save logic itself and throws exceptions on errors. They also now return a string representing the repair reports. * Modified the DiagramEditor to show SWT dialogs (ErrorDialog etc) of exceptions are thrown from the ArgoProject save methods. *** Goals *** * Fix any remaining dialog positioning issues * Fix problems with and enhance the View menu * Display repair reports to the user on save * Begin work on Outline view integration * Clean up import wizard UI --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
