Re: [henshin-dev] Henshin Editor

[Enrico Biermann <enrico@xxxxxxxxxxxxxxx>]

Hello Johannes,

the default (empty) model is displayed when there was an error opening
your .henshin file.
The only cause I can think of is that Muvitor wasn't updated which
should have happened automatically because of the editor's dependency on
the newer version 0.9.1.

All my tests on local examples worked. Could you sent me your ecore and
henshin files so I can determine why it doesn't work with the updated
editor?

Regards,
Enrico

On 13.04.2011 23:49, Johannes Tietje wrote:
> Hello Enrico,
>
> I updated my editor from the update site but it seems the editor can't
> print my rule file properly---have any specifics of rule layouting
> fundamentally changed? The only thing visible (besides no imported
> packages or transformation units) is a transformation system named
> "default", although "my" transformation system in that rule file is
> named "transformation system".
>
> I try to reset the editor to the old version.
>
> Regards,
> Johannes
>
>
> Am Mittwoch, den 13.04.2011, 18:58 +0200 schrieb Enrico Biermann: 
>> Hello Johannes,
>>
>> thanks for the clarification. I assumed the bug you mentioned was for
>> the GMF-based editor not the GEF-based one.
>> Anyway, it should be fixed in editor version 0.8.3 available via the
>> update site (http://tfs.cs.tu-berlin.de/software/)
>>
>> Regards,
>> Enrico
>>
>> On 13.04.2011 17:55, Johannes Tietje wrote:
>>> Hi Enrico,
>>>
>>> I have a bug to file for the graphical editor, as I explained in another
>>> mail, because when I have a transformation unit containing two rules,
>>> where the unit and the rules have one common parameter,
>>>
>>> transformation unit "u1"
>>> -> parameter "a"
>>>
>>> -> rule "b"
>>>    -> parameter "b.a"
>>> -> rule "c"
>>>    -> parameter "c.a"
>>>
>>> I can only graphically connect one rule parameter to the parameter of
>>> the surrounding unit---if I try to connect the second rule parameter to
>>> the parameter of the unit, the first connection gets deleted. This only
>>> happens, if I want the rule parameters to be "output" parameters. (Where
>>> the edge leads from the rule to the unit.)
>>>
>>> Greetings,
>>> Johannes
>>>
>>> Am Dienstag, den 12.04.2011, 15:58 +0200 schrieb Enrico Biermann:
>>>> Hello Amalia,
>>>>
>>>> the editor which was used in the paper is not the official GMF-based
>>>> graphical editor but a GEF-based one.
>>>>
>>>> You can use the following update site to download this editor
>>>> (requires existing Henshin installation):
>>>>
>>>> http://tfs.cs.tu-berlin.de/software/
>>>>
>>>> You need the two features "Muvitor" and "Henshin Editor". After
>>>> installation you should be able to choose either the tree-based editor
>>>> or the GEF-based graphical editor when opening *.henshin files. If you
>>>> have problems with the update site or the editor let us know.
>>>>
>>>> Regards,
>>>> Enrico
>>>>
>>>> On 12.04.2011 14:37, Amalia Sanusi wrote: 
>>>>> Hello,
>>>>>
>>>>>  
>>>>>
>>>>> I am currently starting to work on Henshin. But the problem is that,
>>>>> I don’t have the Henshin Editor shown in this paper:
>>>>> http://journal.ub.tu-berlin.de/index.php/eceasst/article/viewFile/528/530. There’s only a palette with Rule, Edge, Attribute, and the package. I tried to open the perspective but Henshin is not there.
>>>>>
>>>>>  
>>>>>
>>>>> The version that I used is the most recent one (0.7.0). Am I missing
>>>>> something here?
>>>>>
>>>>>  
>>>>>
>>>>> ---
>>>>>
>>>>> Kind regards,
>>>>>
>>>>>  
>>>>>
>>>>> Amalia Sanusi
>>>>>
>>>>>  
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>> _______________________________________________
>> 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