Yes, I followed Stef's suggestion. Moreover at the beginning I wasn't so sure about what I'm doing, so I didn't want to mess directly with FAMIX
Uko
Надіслано з iPhone
16 серп. 2013 о 22:08 Tudor Girba tudor@tudorgirba.com написав(ла):
The AST should certainly be separate, like it is now. But, it would be more effective to have the FAMIX entity directly linked with the AST. I used this pattern on a couple of projects and it makes querying quite cheap.
Cheers, Doru
On Fri, Aug 16, 2013 at 6:19 PM, Nicolas Anquetil Nicolas.Anquetil@inria.fr wrote:
As I remember it, it was a suggestion of Stephane and Marcus to isolate FAST from FAMIX
nicolas
On 08/16/2013 03:42 PM, Tudor Girba wrote:
Also, I do not quite understand the need for the FAMIX wrapper classes from FAST-Model. For example, you have "FAMIXSourcedEntity subclass: #FASTBehaviouralEntity"
Why was FAMIXBehaviouralEntity not enough?
Doru
-- Nicolas Anquetil -- RMod research team (Inria)
Moose-dev mailing list Moose-dev@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev