motionmodeling-bugs Mailing List for Motion Modeling
Status: Alpha
Brought to you by:
sducas
Menu
▾
▴
motionmodeling-bugs — Please, report bugs.
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: <sd...@ne...> - 2005-02-24 11:51:44
|
If you want to know more about UML14 or Diagraminterchange the best think = is not to look directly at MOF definitions... You can download all specifi= cations from OMG site in PDF... By ------------------------------------------------------------- NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, Tool= bar... Web/Wap : www.netcourrier.com T=E9l=E9phone/Fax : 08 92 69 00 21 (0,34 =80 TTC/min) Minitel: 3615 NETCOURRIER (0,16 =80 TTC/min) |
|
From: <sd...@ne...> - 2005-02-24 11:47:31
|
Hi Buns, you're last question was: can you explain me the directory structure of the uml14 src dir (dilayouting, diutils, metamodel, plugin, trashmgmt) ? =21=21 THIS PART IS PARTICULARY UNDER DEV=21=21=21=21=21 This will be changed, but briefly: dilayouting: - Provide Diagram Interchange Based layouting: You can define policy for= node that contain others...What to do when a child is moved, resized, how= to share a gain af size with childrens...This part will be completly refa= ctored (but I don't know how nore when) and putted in a Diagram Interchang= e specific layer.... diutils: - For the moment, only a concrete implementation of Point and Dimension = interfaces from the Diagram Interchange (these are components not entities= so a point is like an integer but not a UML entity (like class, associati= on...)) metamodel: -Contain the implementation of the MetaModel core Extension point... This is where UML14 modeling packages are loaded, exported... look at UML14 plugin.xml you see that UML14 extend the MetaModel extension= point with this class... I didn't try to extend metamodel with javascript= but this is not valuable for the moment because the metamodel logic is on= ly to deal with the MDR... plugin: - With eclipse every plugin can have a class that control youre plugin l= ifecycle (look at plugin.xml) UML14Plugin is this class for the UML14 Plug= in and CorePlugin (in the core plugin)....Core Plugin .... - trashmgmt This part will be moved to an eventual MDR specific layer.... This part as to answer to a simple problem : How to undelete??? Is seems simple but it was very hard because it was like undeleting in a M= ySQL environement... So briefly (look at the code for more...)... Instance= s are never deleted directly, instead all their associations are removed a= nd stocked to put them again if needed... Then the trash is putted in a ma= p... so when clients want to access directly to the objects (Like ...Packa= ges.getAllOfType()....) they have to check if the object is not trashed...= But when they navigate to object (80% of the time) evrything is transparant.... By.... ------------------------------------------------------------- NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, Tool= bar... Web/Wap : www.netcourrier.com T=E9l=E9phone/Fax : 08 92 69 00 21 (0,34 =80 TTC/min) Minitel: 3615 NETCOURRIER (0,16 =80 TTC/min) |
|
From: <sd...@ne...> - 2005-02-24 11:31:23
|
Hi Buns, You're next questions are: >why stardard libs as mof.jar, jmi.jar, mdrapi.jar ... are in the uml14 >plugin (not in MM core) ?? aren't they common libs ? don't i need them >in the bpmn plugin ? There is two reasons: - The first is conceptual : the core is metamodel independent AND model ac= cess technology independant (JMI,MDR, javabeans...)... So the core code ha= s no dependencies toward thise libs... The best solution is to make a MDR specific plugin that UML14 one will be = depends on... - The second is technical: I already tried UML1.3 and UML1.4 at the begini= ng of MM development and MDR cause a bug when it's binary is common to UML= 13 and UML14 : some classes of UML13 has the same name of UML14 so when lo= ading an UML14 model you have a sort of CastException or IllegalClassExcep= tion... whereas the OSGI framework under eclipse garantee that if binaries= are not common the whole =22ClassPath=22 of the =22bundle=22 (look to OSG= I to know more about bundles...) so evrything is perfect... So for making so good solution describe above, we will have to modify MDR = (I already modified it for other stuffs...) so that he can handle OSGI cap= abilities and we can have a clean MOF/JMI and MDR specifics layers.... NEXT QUESTION : NEXT MESSAGE... ------------------------------------------------------------- NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, Tool= bar... Web/Wap : www.netcourrier.com T=E9l=E9phone/Fax : 08 92 69 00 21 (0,34 =80 TTC/min) Minitel: 3615 NETCOURRIER (0,16 =80 TTC/min) |
