Re: AW: [jwt-dev] Restricting nodes as children of the main Activity

[Josh <public.web.josh@xxxxxxxxx>]

Thanks everyone for taking a look at this.  I think I have been using the 0.5 version and there seems to be some significant changes between that and 0.6.

To circumvent some small problems I had integrating (based either on my lack of knowledge of JWT or missing functionality that suited my needs) I have made some small tweaks within my 0.5 local copy.  Once I have a sec to switch to 0.6, I would love the opportunity to help in any way I can.  

Is there a VDD or the like that describes the high level changes between 0.5 & 0.6?  My plan here is to re-integrate with 0.6, and then see where I stand.  If I see that I still need to bring some of my tweaks over, I will articulate them here for remarks.

Thanks again!

On Tue, Nov 17, 2009 at 4:33 AM, Marc Dutoo <marc.dutoo@xxxxxxxxxxx> wrote:

Hi Josh

Chris is the expert here, so I'm afraid he's right.

However, if you manage to make it work by making changes to the JWT source code (*), we could use it as a basis to add it as a feature in the next version.

(*) Source code of JWT 0.6 "Galileo" (Eclipse 3.5) : from the CVS anonymously, using the JWT_0_6 version or the v060 branch, as described at :
http://wiki.eclipse.org/index.php/CVS_Howto
http://wiki.eclipse.org/JWT_CVS

Regards,
Marc

Christian Saad a écrit :

Hi Josh,

to this point there is unfortunately no possibility that I know of to accomplish this behavior without altering the source code of JWT in the way you described. Since the modification of the behavior is probably something that should be possible in our context, we’ll put this on our todo list for one of the next versions. Thanks for the suggestion!

Regards,

Chris

*Von:* jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] *Im Auftrag von *Josh
*Gesendet:* Montag, 16. November 2009 05:27
*An:* jwt-dev@xxxxxxxxxxx
*Betreff:* [jwt-dev] Restricting nodes as children of the main Activity

Hello! I am sending this question to this group at the recommendation of Marc Dutoo (A copy also exists on the JWT community forums.

Following the lead of the EPC view sample, I have successfully created my own view and have happily been extending the metamodel for some custom needs. I've hit an obstacle that I was hoping someone here might have a workaround for.... Quick background: I created an extension plugin that defines my metamodel (extending off of jwt-we) and have some custom actions (extending from ActivityNode). There is some more subclassing I do from there. For example: ActivityNode <--- TypeA_CustomNode ActivityNode <--- TypeB_CustomNode Similarly, I also extended the StructuredActivityNode: StructuredActivityNode <--- CompositeNode The desired functionality: I would like to be able to create an Activity that I can add nodes of TypeA to, as well as my CompositeNode, but I would like to restrict nodes of TypeB from being drop directly to the main Activity, and constrain them only to the CompositeNode. (Type A can be placed anywhere) Problem: Running through the code it seems because ActivityNode is the superclass, the CreateChild Request is fulfilled by the ScopeLayoutEditPolicy, which, though no fault of its own, only cares about the ActivityNode being added to the Activity. I would love to be able to inject the logic to cancel the command if the ActivityNode is of TypeB, but I can't do that. Is there any combination of EditPolicies or extension points that could realize this type of behavior? Thanks in advance for any help you can offer!!

------------------------------------------------------------------------

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
 

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev