Thanks Simon,
this info is important.
Cheers,
Alexandre
On 12 Apr 2010, at 15:27, Simon Denier wrote:
Hi Gabi
Just from experience, if you send mooseModel to all entities in a
large model, it can take a long time. So if you run into
scalability problem, it may come from that. Now depending on your
use case, there might be other solutions.
On 12 avr. 2010, at 19:57, Tudor Girba wrote:
> Hi Gabi,
>
> Ahh, now I understand. Any entity answers to mooseModel, so you
> can do:
>
> FAMIXClass>>someMethod
> self mooseModel ...
>
>
> Great that you are using the Pharo version. Just for
> convenience, you can find the latest development image here:
>
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
>
> Please let us know if you have further problems.
>
> Cheers,
> Doru
>
>
> On 12 Apr 2010, at 18:18, Gabriela Arevalo wrote:
>
>> Hi Doru,
>>
>> Thanxs for answering so quick.
>>
>> I am attaching an jpg to illustrate my problem :)
>>
>> If I evaluate MooseModel root, I get an instance of MooseModel
>> that contains all the existing models. In the image you see
>> that there are two models: Collections and
>> SequenceableCollection, and SequeanceableCollection is selected
>> to be the current one of the analysis.
>>
>> How can I access to that model if I am coding any property in a
>> class? I checked the entities to know if each entity knows the
>> model which belongs to, but it seems not.
>>
>> In the long past we could do ModelManager uniqueInstance
>> currentModel, but now, how do I know that information?
>>
>> I am using Pharo version. I used the VW version during the
>> weekend, but it seems that there are some code broken and I
>> could not manage to make it work.
>>
>> Cheers,
>>
>> Gabi
>>
>> 2010/4/12 Tudor Girba <tudor.girba(a)gmail.com>
>> Hi Gabi,
>>
>> Nice to hear from you :).
>>
>> ModelManager was replaced by just another Model that holds
>> Models. To get to it, you do "MooseModel root" and if you want
>> to see allModels from there, you do "MooseModel root allModels".
>>
>> Yes, properties are defined using pragmas.
>>
>> Which Moose are you using? Pharo or VW?
>>
>> Cheers,
>> Doru
>>
>>
>> On 12 Apr 2010, at 02:11, Gabriela Arevalo wrote:
>>
>> Hi guys,
>>
>> I have two basic questions regarding the implementation of Moose
>> 1) How do we manage now the currentModel (the selected Model in
>> the Moose UI)?
>> A long time ago :) :), we have had the ModelManager class and
>> we could do ModelManager uniqueInstance currentModel
>>
>> 2) Properties: I have seen that we are using pragmas from the
>> instance side. Is it right? Or are there any other way of
>> specifying them?
>>
>> Cheers,
>>
>> Gabi
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>>
www.tudorgirba.com
>>
>> "Beauty is where we see it."
>>
>>
>>
>>
>
> --
>
www.tudorgirba.com
>
> "We cannot reach the flow of things unless we let go."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch