basically integrate IS

[dumoulin]

The aim is to provide a converter between the IDEModularApplication stored in the IDE and an ExplorationApplication in the IS.

Then the IDE will be enable to use the IS Swing client :

• when open action is called in the IDE, the application explorer of the IS is opened for choosing an application, then data are converted, and the application is opened in the IDE
• when save action is called in the IDE, the application is converted and give to the structure of the IS, and the IS stored the application at the correct place according to the version.
• when manage action is called in the IDE, the IS Swing client window is opened, and the user could export the components on the server

[dumoulin]

r1744 brings a simple façade to the IS. Be sure to update the IS sources and the lwm to work with it.

[dumoulin]

An exploration application is well saved, but the constants aren't, because we should associate a default exploration to store them.

[dumoulin]

r2017: more improvements.

[dumoulin]

with r2058, an exploration application is completely stored in the IS, including constants values in exploration data.

[dumoulin]

with r2233, constants and codes can also be linked to method (as to field).