mlhim-specs-dev team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 210
committer: Timothy W. Cook <timothywayne.cook@xxxxxxxxx>
branch nick: mlhim-specs
timestamp: Mon 2011-10-17 18:20:42 -0500
message:
  Beginnning re-work of MLHIM 2.3.0 specifications document.  Added the Ecore-Acceleo.txt file describing how we can leverage Acceleo driving code generation off of the Ecore model.
added:
  documents/Ecore-Acceleo.txt
modified:
  mlhim-ref-man-2.x.y-enUS.odt


--
lp:mlhim-specs
https://code.launchpad.net/~mlhim-specs-dev/mlhim-specs/main

Your team MLHIM Specifications Developers is subscribed to branch lp:mlhim-specs.
To unsubscribe from this branch go to https://code.launchpad.net/~mlhim-specs-dev/mlhim-specs/main/+edit-subscription

=== added file 'documents/Ecore-Acceleo.txt'
--- documents/Ecore-Acceleo.txt	1970-01-01 00:00:00 +0000
+++ documents/Ecore-Acceleo.txt	2011-10-17 23:20:42 +0000
@@ -0,0 +1,49 @@
+Acceleo Uses in MLHIM2
+======================
+
+1) Generate Java from Ecore model.
+
+2) Generate Python from Ecore model.
+
+3) Generate XML Schemas from Ecore model.
+
+4) Generate Ruby from Ecore model?
+
+The generators shouldlive in mlhim-specs BZR repository as follows:
+
+1) mlhim-specs/org.mlhim2.acceleo.pim.gen.java
+
+2) mlhim-specs/org.mlhim2.acceleo.pim.gen.python
+
+3) mlhim-specs/org.mlhim2.acceleo.pim.gen.xml
+
+4) mlhim-specs/org.mlhim2.acceleo.pim.gen.ruby
+
+The generated code should live in the mlhim-specs BZR repository as follows:
+
+1) mlhim-specs/org.mlhim2.java
+
+2) mlhim-specs/org.mlhim2.python
+
+3) mlhim-specs/org.mlhim2.xml
+
+4) mlhim-specs/org.mlhim2.ruby
+
+I believe that those follow the naming conventions, in general for Eclipse, EMF,
+Acceleo?
+
+After the above steps are accomplished.  We will want to extend the mlhim2.ecore
+with some example CCDs built as Ecore models.  
+
+Then general idea is that the class names in the CCD model come from the 'name' 
+attributes in the XMind CCD.  So these will need to be hand coded.  Once a 
+couple are complete then EMF can generate EMF.Editors in order to create 
+instances.  This puts us in good shape to having proof-of-concept 
+implementations.
+
+Any questions, corrections, issues please contact me.
+
+Tim  -- timothywayne.cook@xxxxxxxxx  
+
+
+

=== modified file 'mlhim-ref-man-2.x.y-enUS.odt'
Binary files mlhim-ref-man-2.x.y-enUS.odt	2011-06-18 12:40:44 +0000 and mlhim-ref-man-2.x.y-enUS.odt	2011-10-17 23:20:42 +0000 differ