UmpleImporter support for USE

[GoogleCodeExporter]

Umple currently has logic to construct metamodels from the ECore XML format. 
Extending that to support the USE language is a logical step forward, as USE 
also has a close relationship to the metamodel but uses its own syntax rather 
than XML.

This benefits USE developers and helps bring them into the  Umple system.

This requires extending the ECore importer to also handle USE files, and 
possibly writing code to distinguish USE files from ECore files.

Original issue reported on code.google.com by Astronomix@gmail.com on 7 Mar 2014 at 4:11

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 7 Mar 2014 at 5:46

• Added labels: Component-SemanticsAndGen, Diffic-Med

[GoogleCodeExporter]

Instead of using the same mechanism as the ECore importer, this is now going to 
be implemented as an extension to the main Umple grammar. This makes it easier 
to use, as it is now a one step process: USE code -> generated code, rather 
than USE code -> Umple code -> generated code.

Original comment by Astronomix@gmail.com on 21 Mar 2014 at 12:27

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Now supports USE classes (r3753) and simple attributes (r3757).

Original comment by Astronomix@gmail.com on 21 Mar 2014 at 3:48

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 21 Mar 2014 at 6:34

• Changed state: Ongoing

[GoogleCodeExporter]

An example Use file is this
http://sourceforge.net/apps/mediawiki/useocl/index.php?title=Quick_Tour

When I try to use the in UmpleOnline it does not work. Probably because of the 
inability to mix Umple and USE.

However we need USE to work fluidly with Umple. So for example when I import a 
use file, it will create some classes. Then I should be able to use Umple 
syntax (e.g. as a mixing) to add some other stuff.

What I propose is the following:

1. Bracket use syntax with 'begin use;' and 'end use;' Later on we could 
bracket other difficult alternate syntax in a similar way to allow blending 
with Umple.

2. When you want to read a pure use file (that won't have these) this can be 
accomplished as follows: In the command line main program, or anywhere 'use' 
statements occur in umple to incorporate new files, the code should look at the 
extension, and if it is 'use' it would inject 'begin use;' and 'end use;' into 
the stream as it reads the file. Then the Umple parser would be able to read 
the file natively and the user wouldn't know that the 'begin use' and 'end 
use;; where there. But if the user wanted to truly mix syntax he could still do 
that.

3. You may find it doesn't work in Umpleonline because umpleonline uses the 
umplesync main program (in the same file). Perhaps there is an issue with that.

Otherwise

Original comment by TimothyCLethbridge on 21 Mar 2014 at 7:40

[GoogleCodeExporter]

I noticed that it wasn't working in UmpleOnline on my local machine too; which 
was because it was injecting a line at the end "// end of model" and the USE 
grammar didn't support comments. Those are now added, and USE works fine in my 
local UmpleOnline but not the server, I'm not sure why. (This is the work in 
r3772).

I added a significant subset of the USE association functionality in r3810.

Original comment by Astronomix@gmail.com on 28 Mar 2014 at 7:08

[GoogleCodeExporter]

A quick tour of USE is here.

http://sourceforge.net/apps/mediawiki/useocl/index.php?title=Quick_Tour

Original comment by TimothyCLethbridge on 12 May 2014 at 1:01

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 27 Jun 2014 at 6:18