Suggest component names based on the graph.
Add pre-defined templates too, to inject a whole instance (with the keywords, the name attribute, a default name and the value being preselected).

Add a new wizard that creates a bash script with CURL instructions and examples of REST usage.
Using a bash script may be a first solution for ordered boostrap of a instances within an application.

We will seriously need such tests to prevent regressions.
It is too complicated and painful to test by hand.

In linshareExternal, External should not be highlighted.

1. Create a new valid project, with a graph and so on.
2. Create a brand new file (graph or instances) that is not referenced by the other files.
3. Add an error in this new file.

The builder will never try to validate it.

In the following snippet, the port property should be highlighted just like name.
It is not.

instance of vm {
    name: vm1;  # the VM name

    instance of server {
        name: server;
        port: 9878;

        instance of web-app1 {
            name: web-app1-1;
        }
    }
}

And an action to toggle comments.
Empty lines should be ignored.

Add the XML content type for the graph-ui file extension.

When removing the Roboconf nature from a project, all the markers created by the builder should be deleted.

When using the Eclipse tooling for Roboconf, right clicking on any project shows the "add nature" menu. This is really annoying as most of the workspace projects are not Roboconf ones. It would be better if these actions were only visible when there exist a "src/main/model" directory.

Notice: the "add nature" menu does not appear on projects which already have it.

With Oxygen, creating a new facet or component results in an invalid name.

aql:'Component_'+container.components->size()

And creating a facet or a component always results in the creation of a facet.
It seems the Sirius model is not working anymore.

The rendering is just better with JPG files.
PNG tricks are very annoying.

https://bintray.com seems like a good solution. And it is free for OSS projects.
See http://blog.bintray.com/2014/03/11/hosting-your-eclipse-update-site-p2-on-bintray-com/

Sirius perspective not found... 👿

A Roboconf project has a custom structure.
There should be a wizard to create such a project with Eclipse.

Do we need a project nature?
If so, add actions on the project to add/remove this nature.

For the moment, some exceptions remain silent.

Update the formatter to automatically remove trailing spaces, except on the currently edited line.

That's for instance and graph files.

Create a command file in your Eclipse workspace.

# Create a new VM...
Define vmName  = vm_worker $(SMART_INDEX)
Create vm as ${vmName}

# ... with a single worker
Create worker as worker under ${vmName}

# Start everything
Deploy and start all $(vmName)

The following errors are shown: Instance names must respect the following pattern: [a-zA-Z_](\w|-| |.)* Instance: ${vmName}. This error should not be shown. There is no error in this file.

No error marker is set on the resource or in the text editor.
Maybe an issue with location resolution. No issue with graph files.

Select File > New > Project...
The wizard to create a diagram project for Roboconf is not listed. It only appears when we select File > New > Roboconf. It should appear in both.

The title says it all.
Other issues will be created to deal with other features of this or these editors.

We may have to load when is under the target directory as well.

They are on the project.
They should be on the file.

Source > Correct Indentation

Currently, the field is empty by default.
It should be net.roboconf by default. That wll prevent an error from appearing when a user type in a user name, and it will be possible to edit this field quite easily if it does not match. For new beginners, this will not be a problem to let this field untouched.

Too many steps otherwise...

And run it before code generation...

And not ASCII...

When the auto-completion submits a list of components, we should be able to read their descriptions, if they are available. We suggest to parse the direct comments that preceed a component (or a facet) definition.

The icon for runtime dependencies should be refreshed.
It does not look as good as the other ones.

Only if there is a POM.

This new wizard should create...

• ... a Java Maven structure.
• ... a sample Target Handler.
• ... an optional .gitignore or .svnignore.
• ... a pom.xml file.
• ... a metadata.xml file.

The wizard should also have an option at the end to run mvn eclipse:eclipse.
If not checked, a single Maven project will be generated.

It would be a good idea to put as much as possible in the tooling-core module (in the platform).

TODO: should be highlighted in a different color.

The label should be deduced from the imported variable names.
A service is the best option to implement it.

Auto-completion for:

• Component block
• Facet block
• Facet keyword
• Component and facet properties
• Component and facet names for imported variables
• Variables names for imports
• Known installers
• Component facets
• Component and facet inheritance

This will be the occasion to verify how our parser supports broken graph definitions. 👀

And update the (c) headers in XML files.