[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [viatra-dev] MWE-based transformation chain workflow
|
Hi,
basically, a single thing: the ability to integrate tools like source code prettifier to the end of the workflow, as such integrations already exist.
I know MWE provides only small benefits (luckily for a small integration cost), that’s why I am aiming at producing reusable components (and discussion of the problematic points). This will allow us in the future to replace MWE with a different approach, that is a more natural fit of our stack.
Cheers,
Zoli
-- Zoltán Ujhelyi
Software Developer
IncQueryLabs Ltd.
> On 26 Jun 2015, at 08:37, István Ráth <rath@xxxxxxxxxx> wrote:
>
> Hi,
> On 25 Jun 2015 at 18:29:06, Ujhelyi Zoltán (ujhelyiz@xxxxxxxxxx) wrote:
>
>> >> * We replace our existing syntax with explicitly modelled control structures: sequence, decision, loop (and optionally parallelism), and additional data flow can be done using a publish-subscribe model. This would remove most channels from the existing version.
>> > Are these structures already defined in MWE or are we inventing a new script language?
>> Sadly, no such structures are predefined (with the exception of sequence :) ).
> If this is the case, what exactly is the advantage of integrating to MWE rather than just define a new Java/Xtend API for orchestrating transformation chains?
>
> cheers
> Istvan
>
>
> --
> István Ráth
> Research Fellow
> Fault Tolerant Systems Research Group
> Budapest University of Technology and Economics
> http://inf.mit.bme.hu/en/members/rath
> rath@xxxxxxxxxx
> _______________________________________________
> viatra-dev mailing list
> viatra-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/viatra-dev
