[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[jwt-dev] AW: JWT metamodel extension spec
|
Hi Marc, hi all,
thanks for the JWT metamodel extensions spec. I'll have a look at it soon.
Concerning your problems with the display just a short explanation:
Everything that is displayed in the workflow editor (doesn't matter whether
it is properties or model elements themselves) is only visible, if it is
defined in the selected view.
You can find the tool agil-view on the Eclipse CVS. There you can load any
.view-file (like business.view or technical.view) and can select which parts
shall be displayed. Every time you add a new property or a new model
element, these views need to be created again with the selection of the new
property/model element - otherwise it won't be shown somewhere in the
editor.
Currently the agil-view is a Swing-tool. It should be changed into an
Eclipse plugin using SWT, but we didn't have the resources for that until
now.
Best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: Marc Dutoo [mailto:marc.dutoo@xxxxxxxxxxx]
Gesendet: 19 May 2008 17:03
An: 'Florian Lautenbacher'; csaad@xxxxxxx
Betreff: Re: JWT metamodel extension spec
Hi Christian, Florian
I'd like to know
* how to make visible dynamic and static additions to the
WEMetaModel.ecore in the Outline and in the property view. I've found the
Outline class, I've generated the model and edit and it works well including
saving, but nothing is displayed...
* Chris, how what I say pans out with your ideas about JWT metamodel .
Regards,
Marc
Marc Dutoo a écrit :
> Hi all
>
> I've written about JWT metamodel extension specifications at the
> bottom of http://wiki.eclipse.org/index.php?title=JWT_Metamodel ,
> mainly on
> * "goals" : summarize all JWT members' goal for such extensions.
> Obviously everyone's welcome for giving some feedback !
> * "design" : summarize my latest tries at hacking the JWT WE
> metamodel and writing sample extensions. I've still to upload the
> actual stuff as a bugzilla.
>
> To make it short, for now what I like is an "aspects" relation on
> ModelElement (or at least Action) to an "Aspect" dynamic interface,
> and dynamic EMF extensions. I've also tried simple properties.
>
> Feedback welcome !
>
> Regards,
> Marc
>