Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-ocl.dev] Latest commits

Adolfo,

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=485142.

In general, using PropertyDatum seems to imply that the Dependency Graph has
already been created. What I propose is an API/Class that could be use in
alternative creation of "dependency graphs" or equivalent.

Regards,

Horacio Hoyos Rodríguez
EngD Student
University of York

http://www.york.ac.uk/docs/disclaimer/email.htm

-----Original Message-----
From: mdt-ocl.dev-bounces@xxxxxxxxxxx
[mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Adolfo Sanchez-Barbudo
Herrera
Sent: 04 January 2016 13:13
To: mdt-ocl.dev@xxxxxxxxxxx
Subject: Re: [mdt-ocl.dev] Latest commits

Could you refine your requirements?. Much better could you create a bugzilla
with them, so that there is an isolated change related to the bugzilla
number ?

Some comments/doubts from your original question.
- Do you want property reads/writes, or the corresponding property datum
reads/writes ?
- AbstractDatum currently has a reference to a TypedModel. Is that OK for
you, or do you need the Domain ?

Cheers,
Adolfo.
--
On 04/01/2016 12:28, Horacio Hoyos Rodriguez wrote:
> Hi,
>
> Thanks too for merging all our efforts.
>
> Adolfo, while revising QVTpToQVTg, can you try to make the property
> analysis functionality a separate class or static methods I could
> reuse in my version of the scheduler?  Maybe a method with signature
> "Map<Domain, List<Property>> getAccesedProperties(Mapping m)", that
> returns the accessed properties, by domain, of the mapping and another
> getSettedProperties (or similar) to get the properties being set in
> the mapping?
>
> Cheers,
>
> Horacio Hoyos Rodríguez
> EngD Student
> University of York
>
> http://www.york.ac.uk/docs/disclaimer/email.htm
>
> -----Original Message-----
> From: mdt-ocl.dev-bounces@xxxxxxxxxxx
> [mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Adolfo
> Sanchez-Barbudo Herrera
> Sent: 04 January 2016 11:55
> To: mdt-ocl.dev@xxxxxxxxxxx
> Subject: Re: [mdt-ocl.dev] Latest commits
>
> Hi Ed,
>
> Thanks for making this happen.
>
> Now that everything is in master, and seizing the new year we are
> starting, I've done a clean up of local and remote branches.
>
> Prior to stress the new scheduler, I want to do a new review/clean up
> of the QVTp2QVTg component. I presume that the amount of cases we have
> in hands should be enough to accept the changes.
>
> Since we are kinda of "stable" state, I'll start to launch bugzillas +
> branches to track every change and/or failure I consider you should
> look at.
>
> My OCL2QVTp still relies on Epsilon, I'm unsure that we need to change
> this now, but I'm happy to translate it to java if you wanted.
>
> Regards,
> Adolfo.
>
> On 02/01/2016 19:04, Ed Willink wrote:
>> Hi
>>
>> I've pushed a variety of work in progress contributions to QVTd GIT
>> master. They rely on OCL tag I201601021212 available as
>>
>> http://www.eclipse.org/modeling/download.php?file=/modeling/mdt/ocl/d
>> o wnloads/drops/6.1.0/I201601021212/mdt-ocl-Update-I201601021212.zip
>>
>>
>> http://www.eclipse.org/downloads/download.php?file=/mmt/qvtd/download
>> s
>> /drops/0.13.0/I201601021342/mmt-qvtd-incubation-Update-I201601021342.
>> z
>> ip
>>
>>
>> The new Java-based scheduler from me
>> The Java versions of QVTc2QVTu, QVTu2QVTm and QVTu2QVTp from
>> Horacio/me More CS2AS tests/fixes from Adolfo
>>
>> There are now four QVTdMtcTests that do not need Epsilon support; two
>> go the whole way from QVTc to Java.
>>
>> Currently Epsilon/Java-based functionality co-exists via boolean
>> arguments/duplicate methods in MtcBroker.
>>
>> M5 is in four weeks time. I will probably delete all Epsilon related
>> functionality for M5.
>>
>>      Regards
>>
>>          Ed
>> _______________________________________________
>> mdt-ocl.dev mailing list
>> mdt-ocl.dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> _______________________________________________
> mdt-ocl.dev mailing list
> mdt-ocl.dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
> _______________________________________________
> mdt-ocl.dev mailing list
> mdt-ocl.dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev

_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev


Back to the top