Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [henshin-dev] Excluded subtypes for nodes

Hi again,


Am 26.09.2011 12:59, schrieb Christian Krause:
> Hi,
>
> It would be nice to have a syntax in the graphical editor for this
> though -- currently it is not possible to specify this. We could
> extend the syntax for node names/types, I guess, but the editing
> operations are not exactly trivial.

Please have a look at our forum, where I proposed a visualization for
such cases already! Actually, did anyone noticed it already?


>
> On a related subject, I was thinking about introducing a new
> stereotype for nodes: <<update>>. Meaning: create such a node unless
> one exists already; so it is like a combination of <<create>> and
> <<forbid>>.
For my understanding, "update" presumes the existence of the artifact to
be updated. 
Furthermore, in order to prevent island solutions for very specific
cases, please consider the proposed notations in the forum and carefully
consider different cases and combinations that can occur.
It took me some time to find a valid and predominantly consistent
visualization, so I would be happy if you either improve the proposed
notation or consistently change it as a whole.

regards,
Stefan

>
> Ciao,
> Christian
>
> On 09/26/11 12:51, Christian Krause wrote:
>> Of course. Thanks, Gregor.
>>
>> On 09/26/11 12:22, Gregor Bonifer wrote:
>>> Hi Christian,
>>>
>>> it should be possible to just add a NAC containing a rule-node
>>> mapped to the LHS' unit-node. This should provide a negated type
>>> constraint that ensures that the matched unit is not a rule.
>>>
>>> Regards,
>>> Gregor
>>>
>>> Am 26.09.2011 12:00, schrieb Christian Krause:
>>>> Hi,
>>>> I would like to add the following feature to Node:
>>>>
>>>> - excludedSubTypes: EClass 0..*
>>>>
>>>> The meaning is that for an object to be able to be matched, it must
>>>> not inherit from any of the classes in this list (but of course it
>>>> still must implement the class specified in the "type" attribute).
>>>>
>>>> A concrete example: I want to define a transformation for the
>>>> Henshin generator model. One rule should map a "TransformationUnit"
>>>> to a "GenUnit". Another rule should map "Rule" to "GenRule". For
>>>> the first rule I need to specify somehow that the matched unit is
>>>> not a rule; so I need to exclude the subType "Rule" here.
>>>>
>>>> The required modifications to the editors and the interpreter are
>>>> minimal. Ok with you?
>>>>
>>>> Ciao,
>>>> Christian
>>>> _______________________________________________
>>>> henshin-dev mailing list
>>>> henshin-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/henshin-dev
>>>>
>>>
>>> _______________________________________________
>>> henshin-dev mailing list
>>> henshin-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/henshin-dev
>>
>
> _______________________________________________
> henshin-dev mailing list
> henshin-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/henshin-dev


Attachment: signature.asc
Description: OpenPGP digital signature


Back to the top