Non-moose entities in Moose

List overview All Threads
Download

newer

older

roassal rendering problem

Jenkins build became unstable: ...

Yuriy Tymchuk

7 Nov 2013 7 Nov '13

7:04 p.m.

Show replies by date

Nicolas Anquetil

7 Nov 7 Nov

7:12 p.m.

depends what you want to do with them? you can always just store them in properties (like the values of a metric) no ? nicolas On 11/07/2013 07:04 PM, Yuriy Tymchuk wrote:

...

Hi everyone. Does anybody has a suggestion of how to work with objects which classes do not subclass Moose entity? For example I need a Date as one of the properties. Is there a common solution for that? Cheers Uko _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Nicolas Anquetil -- RMod research team (Inria)

Yuriy Tymchuk

7:25 p.m.

Is there something special I should do for it? Because I’ve added pragma like: <MSEProperty: #date type: #Date> To the parent entity uko On 07 Nov 2013, at 19:12, Nicolas Anquetil <Nicolas.Anquetil(a)inria.fr> wrote:

...

depends what you want to do with them? you can always just store them in properties (like the values of a metric) no ? nicolas On 11/07/2013 07:04 PM, Yuriy Tymchuk wrote:

-- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Andre Hora

7:58 p.m.

On Thu, Nov 7, 2013 at 7:25 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:

...

Is there something special I should do for it? Because I’ve added pragma like: <MSEProperty: #date type: #Date> To the parent entity

I think this is wrong. The type should be either primitive property defined in Fame (#Boolean, #Number, #String) or a class of your meta-model (FAMIXClass, FAMIXMethod, etc). A simple solution is use the type #Number, and convert the date to a number, for example using: Date today asDateAndTime asUnixTime. "1383778800" (DateAndTime fromUnixTime: 1383778800) asDate " 7 November 2013" Maybe there is another solution that I'm not aware :)

...

uko On 07 Nov 2013, at 19:12, Nicolas Anquetil <Nicolas.Anquetil(a)inria.fr> wrote:

depends what you want to do with them? you can always just store them in properties (like the values of a

metric) no ?

nicolas On 11/07/2013 07:04 PM, Yuriy Tymchuk wrote: > Hi everyone. > > Does anybody has a suggestion of how to work with objects which classes

do not subclass Moose entity? For example I need a Date as one of the properties. Is there a common solution for that?

Cheers Uko _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ 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 https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Andre Hora

Tudor Girba

9:48 p.m.

Exactly. The current solution would be to store the value as a memento from which you can build your real object afterwards. In the case of Date, this would be either a number or a string. Doru On Thu, Nov 7, 2013 at 7:58 PM, Andre Hora <andrehoraa(a)gmail.com> wrote:

...

On Thu, Nov 7, 2013 at 7:25 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote;wrote:

Is there something special I should do for it? Because I’ve added pragma like: <MSEProperty: #date type: #Date> To the parent entity

uko On 07 Nov 2013, at 19:12, Nicolas Anquetil <Nicolas.Anquetil(a)inria.fr> wrote:

depends what you want to do with them? you can always just store them in properties (like the values of a

metric) no ?

nicolas On 11/07/2013 07:04 PM, Yuriy Tymchuk wrote: > Hi everyone. > > Does anybody has a suggestion of how to work with objects which

classes do not subclass Moose entity? For example I need a Date as one of the properties. Is there a common solution for that?

Cheers Uko _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ 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 https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Andre Hora _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "Every thing has its own flow"

Yuriy Tymchuk

10:07 p.m.

On 07 Nov 2013, at 21:48, Tudor Girba <tudor(a)tudorgirba.com> wrote:

...

Exactly. The current solution

What is the other possible situation?

...

would be to store the value as a memento from which you can build your real object afterwards. In the case of Date, this would be either a number or a string. Doru On Thu, Nov 7, 2013 at 7:58 PM, Andre Hora <andrehoraa(a)gmail.com> wrote: On Thu, Nov 7, 2013 at 7:25 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: Is there something special I should do for it? Because I’ve added pragma like: <MSEProperty: #date type: #Date> To the parent entity I think this is wrong. The type should be either primitive property defined in Fame (#Boolean, #Number, #String) or a class of your meta-model (FAMIXClass, FAMIXMethod, etc). A simple solution is use the type #Number, and convert the date to a number, for example using: Date today asDateAndTime asUnixTime. "1383778800" (DateAndTime fromUnixTime: 1383778800) asDate " 7 November 2013" Maybe there is another solution that I'm not aware :) uko On 07 Nov 2013, at 19:12, Nicolas Anquetil <Nicolas.Anquetil(a)inria.fr> wrote:

depends what you want to do with them? you can always just store them in properties (like the values of a metric) no ? nicolas On 11/07/2013 07:04 PM, Yuriy Tymchuk wrote:

-- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ 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 https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Andre Hora _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Alexandre Bergel

9:43 p.m.

You need maybe to reset the meta tower. Try to execute: MooseModel resetMeta Alexandre On Nov 7, 2013, at 3:25 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:

...

depends what you want to do with them? you can always just store them in properties (like the values of a metric) no ? nicolas On 11/07/2013 07:04 PM, Yuriy Tymchuk wrote:

-- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ 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 https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3822

days inactive

3822

days old

moose-dev@list.inf.unibe.ch

Manage subscription

6 comments

5 participants

tags (0)

participants (5)

Alexandre Bergel
Andre Hora
Nicolas Anquetil
Tudor Girba
Yuriy Tymchuk