google-code-export / alloy4eclipse Goto Github PK

What steps will reproduce the problem?
1. Run A4E on win32
2. Visualize an A4 instance
3. The A4 graph pane is black

What is the expected output? What do you see instead?
The A4 graph pane should show the A4 instance graph

What version of the product are you using? On what operating system?
0.1.7 from SVN

Please provide any additional information below.
With 64-bit linux (ubuntu 7.0.4) and RSA 7.0.0.3,
A4E works fine A4/SAT4J.

I recently started using A4E on win32 where I experienced this problem.
The article below suggests a simple fix
Fix is 
http://www.eclipse.org/articles/article.php?file=Article-Swing-SWT-Integration/i
ndex.html

In A4E's case, applying this article suggests the following changes:

public class MultiPageEditor extends MultiPageEditorPart implements
IResourceChangeListener{

    /**
     * @author [email protected]
     * @per Reducing Flicker
     * @see
http://www.eclipse.org/articles/article.php?file=Article-Swing-SWT-Integration/i
ndex.html
     */
    static {
        if (Platform.OS_WIN32.equals(Platform.getOS())) {
            System.setProperty("sun.awt.noerasebackground", "true");
        }
    }

...

    /**
     * Creates page 2 of the multi-page editor,
     * which contains a frame with the graph.
     * 
     * @author [email protected]
     * @per Using the SWT/AWT Bridge
     * @see
http://www.eclipse.org/articles/article.php?file=Article-Swing-SWT-Integration/i
ndex.html
     */
    void createPage2() {

                IEditorInput input;
                input=editor.getEditorInput();

                Composite swtAwtComponent = new Composite(getContainer(),
SWT.EMBEDDED | SWT.NO_BACKGROUND);
                java.awt.Frame frame = SWT_AWT.new_Frame(swtAwtComponent );

                /**
                 * @per Creating a Root Pane Container
                 * @see
http://www.eclipse.org/articles/article.php?file=Article-Swing-SWT-Integration/i
ndex.html
                 */
                javax.swing.JApplet applet = new javax.swing.JApplet();
                frame.add(applet);

                javax.swing.JPanel panel = new JPanel();

                MyVizGUI viz = new MyVizGUI();
                viz.run(MyVizGUI.evs_loadInstanceForcefully,
Util.getFileLocation((IResource)input.getAdapter(IResource.class)));

                panel=viz.getGraphPanel();
                if (panel!=null)
                    applet.add(panel);  

                FillLayout layout = new FillLayout();
                swtAwtComponent.setLayout(layout);

                int index = addPage(swtAwtComponent);
....

It is currently possible to visualize as a graph the solution because the
output file (xml) is saved somewhere.

It should not be difficult to open that xml file in an editor.

- if eclipse has an xml view, the editor will be of great help
- if there is no xml editor, I guess the default editor will be used.

That feature should appear similarly to the show graphical view.

One very nice feature of JDT is the hability to "fold" the code inside a
method or comments, etc.

The background to do this is available at:
http://www.eclipse.org/articles/Article-Folding-in-Eclipse-Text-Editors/folding.
html

It should not be that difficult to add to A4E.

It happened to me to build a model and trying to check a property.

At first, the property was violated, and a counter example has been generated.

At last, the model was good enough to satisfy the property.

The answer was UNSAT/No counter model found.

But the panel was still showing the previous counter model.

I believe that in that case, the viz panel should be automatically closed
in A4E.

However, I need some feedback on this.

--Daniel

In the current SVN code (release 0.0.5 on update site), there is an issue
that appears when an Alloy file is reopened in an editor: a null pointer
exception will prevent the editor to display correctly.

It will open any non already opened file too.

*The only workaround currently is to close eclipse and start it again!*

That issue must be fixed ASAP.

There is currently no easy way for A4E user to know which version of A4
ships with the plugin.

We need to find a way to allow the user to check that information easily.

What steps will reproduce the problem?
1. Type model:
module mm0

open util/ordering[State] as ordering

abstract sig Event {}
one sig WriteFile, CreateFile extends Event {}

sig State {}

pred show {}
2. Look at the outline window.

What is the expected output? What do you see instead?

It should contain signatures Event, WriteFile, CreateFile and State.
Predicate show should also come up. However, none of these show up.
Signatures, Predicates, etc are empty.

What version of the product are you using? On what operating system?

Linux 32Bit, A4E 0.2.18, Eclipse 3.2.1.

Please provide any additional information below.

See attached screenshot.

A4E forces the display of the A4 VizGUI as a small view in the Eclipse
workbench.
The view happens to be very small in most typical configurations and this
makes A4E visualizations
difficult to use when we have large instances to display.

Suggestion: allow the user to specify which workspace part A4E should use
to load A4 vizgui views.

The contextual menu could be improved:

- view answer should be disabled when the command has not been launched yet.
- the label of the menu should be command specific. For instance, it should
mention "Show models" or "Show counter examples" depending of the cases.

The problem was discovered in the context of issue #27 but the APIs
involved are completely different; hence a separate issue.

There is a pathological case:
-------------
module test1
sig A {}
c1:check { no A }

-------------

vs.

-------------
module test2
sig A {}
c1:check { no A }


-------------

launching test1/c1 fails
launching test2/c1 works.

In test1/c1, I get this stack trace:


org.eclipse.jface.text.BadLocationException
    at org.eclipse.jface.text.TreeLineTracker.fail(TreeLineTracker.java:1072)
    at
org.eclipse.jface.text.TreeLineTracker.offsetByLine(TreeLineTracker.java:362)
    at
org.eclipse.jface.text.TreeLineTracker.getLineOffset(TreeLineTracker.java:1139)
    at
org.eclipse.jface.text.AbstractLineTracker.getLineOffset(AbstractLineTracker.jav
a:169)
    at
org.eclipse.jface.text.AbstractDocument.getLineOffset(AbstractDocument.java:848)
    at
fr.univartois.cril.alloyplugin.editor.AlloyTreeContentProvider.feedAnnotations(A
lloyTreeContentProvider.java:141)
    at
fr.univartois.cril.alloyplugin.editor.AlloyTreeContentProvider.changed(AlloyTree
ContentProvider.java:157)
    at fr.univartois.cril.alloyplugin.core.ALSFile.fireChange(ALSFile.java:58)
    at
fr.univartois.cril.alloyplugin.core.AlloyLaunching.updateALSFile(AlloyLaunching.
java:233)
    at
fr.univartois.cril.alloyplugin.core.AlloyLaunching.parse(AlloyLaunching.java:181
)
    at
fr.univartois.cril.alloyplugin.core.AlloyLaunching.launchParser(AlloyLaunching.j
ava:72)
    at
fr.univartois.cril.alloyplugin.ProjectBuilder.parseALSFileFull(ProjectBuilder.ja
va:84)
    at
fr.univartois.cril.alloyplugin.ProjectBuilder.access$1(ProjectBuilder.java:81)
    at
fr.univartois.cril.alloyplugin.ProjectBuilder$SampleDeltaVisitor.visit(ProjectBu
ilder.java:127)
    at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:67)
    at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:76)
    at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:76)
    at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48)
    at
fr.univartois.cril.alloyplugin.ProjectBuilder.incrementalBuild(ProjectBuilder.ja
va:102)
    at fr.univartois.cril.alloyplugin.ProjectBuilder.build(ProjectBuilder.java:42)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:603)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:167)
    at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:230)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:233)
    at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:2
52)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:285)
    at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:154)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:217)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

In the current release, all problems are reported in the console.

The usual way to report compilation problems is to notify the users through
the problem view.

If Alloy4 reports an error in line 22 while the file has only 21 lines
(it happens if there is an error in line 22), then the marker will not show
up in Eclipse Editor.

However, the marker will appear in Eclipse problems view.

Not sure if this should be considered as an upstream Alloy4 problem or
something that we should manage.

A4's Execute menu has a "Show Metamodel" command that should be available
in A4E

Put a command on the "Commands" folder in the A4E outline view to execute
all commands. Alternatively, alloy multiple command selections & provide a
mechanism to execute all selected commands.

A4 ships with sample A4 models.

They are useful to help modeling a new system.

A4E does not have for the moment any way to open those sample models.

They are not even uncompressed for the A4 jar file.

I guess that it is possible in Eclipse to open a file within a jar file
(such feature is used in JDT to access the source code that ships with a
library).

I am not sure however that the file browser can search files within an archive.

This need to be investigated.

Felix chang added a keyboard accelerator for that in A4 (Ctrl-B).

Ctrl-B is "build all" within Eclipse.

So the same accelerator cannot be used.

--Daniel

There is currently no way to configure alloy.

Alloy options should be editable the eclipse way through the
Window/Preferences menu.

It might be nice to also have some project specific settings.

The plugin misses the toolbar from the visualization panel in the original
Alloy 4 GUI.

It is for instance impossible to go through the models of the specification.

Since a menu is now available for the theme selection, it should be easy to
add the other actions there.

The A4 VizGUI has a zoom function that scales both the instance graph as
well as the fixed legend in the top left corner.
WIth large instance graphs, it is convenient to zoom out the view which
makes the legend very difficult if not impossible to see.

Suggestion: create an A4E property viewer that shows the same information
as the legend in the current A4 VizGUI view.

A4 allows the user to interact with an instance using an evaluator.

The same feature should be available also in A4E.

The evaluator is likely to appear as a specific Console in A4E.

- Editor open on an ALS file.
- Create a new A4 model using the wizard.

Before being able to start writing in the new editor, a message dialg with
"Error" appears.

From the error log view, one can see the following:
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:3563)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java
:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ecli
pseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLau
ncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
Caused by: java.lang.NullPointerException
at
org.eclipse.ui.internal.console.IOConsolePartitioner$QueueProcessingJob.runInUIT
hread(IOConsolePartitioner.java:536)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
... 23 more


It looks like an AWT/SWT issue?

Windows user feedback needed on this.

The semantic of a folder in Alloy models is roughly the same as Java packages.

So it would make sense to have folders within Alloy projects to appear with
the Java package icon.

Furthermore, the Ouput folders could be hidden (the same way CVS folders
are), unless users really wants to access the xml files inside them.

There are several textfields corresponding to paths in the filesystem.

It would be nice to have a Browse button associated with each of these fields.

What steps will reproduce the problem?
1. Load a test Alloy spec that has a solution instance
2. Select the solution *.xml file
3. Context menu => open with Alloy Answer Viewer

What is the expected output? 
A new Eclipse viewer with the A4 visualization

What do you see instead?

At line 360, viewer == null.
This will cause a NPE.

Thread [main] (Suspended (breakpoint at line 360 in MultiPageEditor))   
    MultiPageEditor.addPage(String, URL) line: 360  
    MultiPageEditor.createPage2() line: 252 
    MultiPageEditor.createPages() line: 386 
    MultiPageEditor(MultiPageEditorPart).createPartControl(Composite) line: 276 
    EditorReference.createPartHelper() line: 596    
    EditorReference.createPart() line: 372  
    EditorReference(WorkbenchPartReference).getPart(boolean) line: 566  
    EditorReference.getEditor(boolean) line: 214    
    WorkbenchPage.busyOpenEditorBatched(IEditorInput, String, boolean, int)
line: 2595  
    WorkbenchPage.busyOpenEditor(IEditorInput, String, boolean, int) line: 2528 
    WorkbenchPage.access$10(WorkbenchPage, IEditorInput, String, boolean, int)
line: 2520  
    WorkbenchPage$9.run() line: 2505    
    BusyIndicator.showWhile(Display, Runnable) line: 67 
    WorkbenchPage.openEditor(IEditorInput, String, boolean, int) line: 2500 
    OpenWithMenu.openEditor(IEditorDescriptor) line: 288    
    OpenWithMenu.access$0(OpenWithMenu, IEditorDescriptor) line: 280    
    OpenWithMenu$2.handleEvent(Event) line: 184 
    EventTable.sendEvent(Event) line: 66    
    MenuItem(Widget).sendEvent(Event) line: 928 
    Display.runDeferredEvents() line: 3348  
    Display.readAndDispatch() line: 2968    
    Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 1930    
    Workbench.runUI() line: 1894    
    Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 422    
    PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149   
    IDEApplication.run(Object) line: 95 
    PlatformActivator$1.run(Object) line: 78    
    EclipseAppLauncher.runApplication(Object) line: 92  
    EclipseAppLauncher.start(Object) line: 68   
    EclipseStarter.run(Object) line: 400    
    EclipseStarter.run(String[], Runnable) line: 177    
    NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not
available [native method]   
    NativeMethodAccessorImpl.invoke(Object, Object[]) line: 64  
    DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43  
    Method.invoke(Object, Object...) line: 615  
    Main.invokeFramework(String[], URL[]) line: 336 
    Main.basicRun(String[]) line: 280   
    Main.run(String[]) line: 977    
    Main.main(String[]) line: 952   

Please use labels and text to provide additional information.

At line 360, the state of viz[0] is consistent with the call to
viz[0].loadXML(...) from line 348. However, since the Swing/SWT
visualization runs asynchronously w.r.t. there is a significant potential
for a race condition with the thread that executes the code in
MultiPageEditor, line 359:

final VizViewer viewer = viz[0].getViewer();

If this code executes "too early", then viewer == null and we get NPE at
line 360.

The workaround is either to ask the A4 developers to make getViewer() a
blocking call to ensure it returns a non-null answer once the Swing/SWT
thread has performed the necessary update work or for A4E to define a
wrapper to do this.

It would be nice to launch all the commands when Run as is selected on the
"Commands" root tree.

Currently, the only solution to launch all the commands is to select them
all or to use Run as on the file itself.

For the moment, code completion is static: it only provides completion for
A4 keywords.

It would be much useful to have it dynamic, by propsoing for instance also
all signatures in the code completion.

The plugin reports an error with any util module imported.

module foo

open util/boolean as boolean
...

shows an error on the module line that says "IOException occurred:
/models/util/boolean.als (no such file or directory)".  

When double clicking on Signatures,Facts, Functions, etc, the expected
behavior is to expand/collapse the tree. 

This is a regression bug.

It was possible to launch a command by double clicking on it.
It no longer works in 0.1.1 release.

Please fix this ASAP.

There is currently no way to graphically view Alloy models or counter examples.

The easiest way to proceed I guess is to include Alloy graphical view in
one Eclipse view.

The hard way would be to rebuild it from scratch using GEF.

I think we should try the easiest way first :)

It would be nice to have a basic "text format" option in the editor.
Most of the work is to indent properly the code.
I have no idea of the difficulty of that task.

The Console window was recently updated to provide feedback on elapsed time
for checking an Alloy assertion, however it does not provide elapsed time
for generating Vars and Clauses.  Both of these should be displayed, as
they are in the Alloy Analyzer.

Also, new assertion checks should not overwrite feedback from previous
checks.  As in the Alloy Analyzer, feedback should persist to facilitate
comparing successive checks, as changes are made to an Alloy spec.

When the models are large, it is better to be able to choose which run or
check command should be launched.

Maybe one possibility would be to have a specific view with all the
commands that allow to run each of them or all of them.

In Alloy4 RC9, there is a new feature based on unsat core.

When the solver is answering unsat, it is possible to highlight the part of
the specification that is responsible for the inconsistency.  

It would be nice to include that feature for milestone 2.

One of the major interest in using Eclipse is the support for refactoring.

Basic refactoring support is provided almost for free within Eclipse.
http://www.eclipse.org/articles/Article-LTK/ltk.html

A simple refactoring such as "Rename" should be possible in the current
editor without much trouble.

We can't access the solver MiniSat with UnSat Core via JNI.

Salut,

Attached are proposed patches solving two practical issues:
1) applying a visualization theme
2) restrict the a4e context menu to *.xml files in Alloy-natured projects

Caveat: (1) is an ugly hack but it's darn useful...

Ciao,
-- Nicolas.

There is no visual information available when installing Alloy 4 feature.

For instance, new features installed in Eclipse can be visible on the
"About eclipse platform" dialog box.

It would be nice to have the Alloy Icon showing up there when the Alloy4
feature is installed.

Currently, when doing a "Run as Alloy model" is chosen, the Run command is
not remembered by Eclipse, i.e. it is not possible to just click on the run
button to do it again.

Finding a way to do it would be nice.

Here is a link that might help:
http://www.eclipse.org/articles/Article-Launch-Framework/launch.html

When running all commands, the right panel location gets populated with
many command views.

It would be nice to have an action that allows to close all those views.

Another idea would be to close them when closing the editor containing
those commands.

It is possible to go to the next model in A4.

That feature is currently not available in A4E.

A next model action should be added to A4E VizView.

When running a command with a model or a counter example, if the correct
option is selected, a Viz panel is generated.

Unfortunately, it does not show up so the user needs to select it to show
the result.

What steps will reproduce the problem?
1. Open Eclipse 3.3.1.1, get A4E 0.2.18
2. Restart eclipse
3. Try to start a new project or change perspective to Alloy

What is the expected output? What do you see instead?

I would expect a Alloy new project option to show up as well as an Alloy
perspective but this doesn't happen.

What version of the product are you using? On what operating system?

A4E 0.2.18, Eclipse 3.3.1.1, Gentoo Linux AMD64.

What steps will reproduce the problem?

Good case :

1. select an als file in project view.
2. choose Run as ... Alloy Specification
3. hit CTRL F11
4. the command is repeated.

Bad case :

1. Open the als file in an editor
2. launch the command directly in the outline view
3. hit CTRL F11
4. Eclipse asks for the type of command to execute

We should have the same consistent behavior there.
I suspect that we are loosing the type of the Launch when launching the
command from the outline view.
The extension of the file in the project view provides the right type to
the launch.

What steps will reproduce the problem?
1. Run A4E 0.2.5 on the following simple example:

sig A {}
c1: check { no A }

2. In the A4E outline view, select "Check c1 [SAT]" and show counter example

3. No counter example. There is an error:

java.lang.IllegalArgumentException: Illegal secondary id (cannot be empty
or contain a colon)
    at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:3502)
    at
fr.univartois.cril.alloyplugin.core.ExecutableCommand.displayAns(ExecutableComma
nd.java:413)
    at
fr.univartois.cril.alloyplugin.launch.ui.DisplayCommandAnswerAction.run(DisplayC
ommandAnswerAction.java:105)
    at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
    at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionCont
ributionItem.java:539)
    at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.
java:488)
    at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContribution
Item.java:400)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
    at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java
:78)
    at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ecli
pseAppLauncher.java:92)
    at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLau
ncher.java:68)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:43)
    at java.lang.reflect.Method.invoke(Method.java:615)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
    at org.eclipse.core.launcher.Main.run(Main.java:977)
    at org.eclipse.core.launcher.Main.main(Main.java:952)

IBM RSA 7.0.0.3 (Eclipse 3.2.x)

The code for AWT/SWT integration is based on the initial proposal of the
Albireo project: http://www.eclipse.org/albireo/

That project is now in Eclipse incubator.

Final release of A4E should rely on that project, when a first stable
release will be out.

Note that AWT/SWT is a big issue, and we won't go ahead with Albireo until
the project provides evidences that it increases AWT/SWT bridge stability
on all platforms. 

When being in an Alloy 4 perspective, the new Alloy model and new Alloy
Project should be available by default from the project explorer contextual
menu, without having to go to Other...

in release 0.1.5, a dependency to EMF was introduced.

A ResourceDialog available in emf.common.ui is used to browse the theme files.

It would be nice to find a feature equivalent object in jface or basic
Eclipse plugins.

The new release candidate of A' (RC15) provides a new keyword: private.

For details about that new keyword, see
http://alloy.mit.edu/alloy4/kb/private.php

Consequences for A4E:
Eclipse users are almost certainly Java users and I would say that they are
likely quite used to the graphical representation of public/private members
in classes in the Java outline view (green triangle for public, red for
private).

Now that the notion of private elements appear in A4, we need to have the
same kind of decorators for A4 elements in the outline view :)

From a more low level point of view, the new keyword need to be added to
the editor machinery to be correctly identified in the editor rendering.

The A4 jar file will be available in A4E plugin in a few minutes.

In order to implement quick fix, refactoring, etc., it is necessary to
create an AST manageable with Eclipse API.

All the details are available from:
http://www.eclipse.org/articles/article.php?file=Article-JavaCodeManipulation_AS
T/index.html

after executing a command in the evaluator console, the caret is not
displayed after the "> " prefix to wait for the new command but at the
beginning of the command result.

it is not a big problem but it would be nice to fix that issue for M3 or M4.