Hi guys.
So Benjamin Arezki is working on PetitJava and FAST for Java and I'm very happy about that. Now I want to make a well structured project with an opportunity to integrate it into Moose.
Can anyone suggest me what to do with the configuration? Because it's hard for me to understand me all the shenanigans with metacello. Should I store each package separately, add all of them into a baseline and then add them with versions to a 'version'?
I'd really like to make a good use of my project, but I need help form you (especially Doru ;) )
Cheers! Uko
-- View this message in context: http://moose-dev.97923.n3.nabble.com/Configuring-FAST-metacello-tp4028315.ht... Sent from the moose-dev mailing list archive at Nabble.com.
Hi Yuriy,
Good news. I would be happy to help. I will try to make a bit of time sometime next week. Please ping me on Wednesday, if I did not react until then.
Cheers, Doru
On Tue, Aug 6, 2013 at 8:53 PM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
Hi guys.
So Benjamin Arezki is working on PetitJava and FAST for Java and I'm very happy about that. Now I want to make a well structured project with an opportunity to integrate it into Moose.
Can anyone suggest me what to do with the configuration? Because it's hard for me to understand me all the shenanigans with metacello. Should I store each package separately, add all of them into a baseline and then add them with versions to a 'version'?
I'd really like to make a good use of my project, but I need help form you (especially Doru ;) )
Cheers! Uko
-- View this message in context: http://moose-dev.97923.n3.nabble.com/Configuring-FAST-metacello-tp4028315.ht... Sent from the moose-dev mailing list archive at Nabble.com. _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thanks
On 9 серп. 2013, at 23:55, Tudor Girba tudor@tudorgirba.com wrote:
Hi Yuriy,
Good news. I would be happy to help. I will try to make a bit of time sometime next week. Please ping me on Wednesday, if I did not react until then.
Cheers, Doru
On Tue, Aug 6, 2013 at 8:53 PM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote: Hi guys.
So Benjamin Arezki is working on PetitJava and FAST for Java and I'm very happy about that. Now I want to make a well structured project with an opportunity to integrate it into Moose.
Can anyone suggest me what to do with the configuration? Because it's hard for me to understand me all the shenanigans with metacello. Should I store each package separately, add all of them into a baseline and then add them with versions to a 'version'?
I'd really like to make a good use of my project, but I need help form you (especially Doru ;) )
Cheers! Uko
-- View this message in context: http://moose-dev.97923.n3.nabble.com/Configuring-FAST-metacello-tp4028315.ht... Sent from the moose-dev mailing list archive at Nabble.com. _______________________________________________ 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
Hi Doru,
so I'm pinging :)
uko
On 9 серп. 2013, at 23:55, Tudor Girba tudor@tudorgirba.com wrote:
Hi Yuriy,
Good news. I would be happy to help. I will try to make a bit of time sometime next week. Please ping me on Wednesday, if I did not react until then.
Cheers, Doru
On Tue, Aug 6, 2013 at 8:53 PM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote: Hi guys.
So Benjamin Arezki is working on PetitJava and FAST for Java and I'm very happy about that. Now I want to make a well structured project with an opportunity to integrate it into Moose.
Can anyone suggest me what to do with the configuration? Because it's hard for me to understand me all the shenanigans with metacello. Should I store each package separately, add all of them into a baseline and then add them with versions to a 'version'?
I'd really like to make a good use of my project, but I need help form you (especially Doru ;) )
Cheers! Uko
-- View this message in context: http://moose-dev.97923.n3.nabble.com/Configuring-FAST-metacello-tp4028315.ht... Sent from the moose-dev mailing list archive at Nabble.com. _______________________________________________ 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
Pong :).
I took a look at the configuration, and I think you need three different projects: - FASTCore -> FAMIX (which we do not have yet, but we should add it) - FASTJava -> FASTCore, PetitJava - FASTPharo -> FASTCore
This implies three different configurations.
The little visualization you have should be packaged in a separate project altogether.
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
On Thu, Aug 15, 2013 at 3:49 PM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
Hi Doru,
so I'm pinging :)
uko
On 9 серп. 2013, at 23:55, Tudor Girba tudor@tudorgirba.com wrote:
Hi Yuriy,
Good news. I would be happy to help. I will try to make a bit of time sometime next week. Please ping me on Wednesday, if I did not react until then.
Cheers, Doru
On Tue, Aug 6, 2013 at 8:53 PM, Yuriy Tymchuk yuriy.tymchuk@me.comwrote:
Hi guys.
So Benjamin Arezki is working on PetitJava and FAST for Java and I'm very happy about that. Now I want to make a well structured project with an opportunity to integrate it into Moose.
Can anyone suggest me what to do with the configuration? Because it's hard for me to understand me all the shenanigans with metacello. Should I store each package separately, add all of them into a baseline and then add them with versions to a 'version'?
I'd really like to make a good use of my project, but I need help form you (especially Doru ;) )
Cheers! Uko
-- View this message in context: http://moose-dev.97923.n3.nabble.com/Configuring-FAST-metacello-tp4028315.ht... Sent from the moose-dev mailing list archive at Nabble.com. _______________________________________________ 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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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
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-devhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
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
Ok, so as far as I understand - we'll release Moose 4.8 and then I can start to integrate FAST into Moose 5?
Uko
On 17 серп. 2013, at 09:15, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Well, you can start splitting the project anyway.
Doru
On Tue, Aug 20, 2013 at 11:55 AM, Yuriy Tymchuk yuriy.tymchuk@me.comwrote:
Ok, so as far as I understand - we'll release Moose 4.8 and then I can start to integrate FAST into Moose 5?
Uko
On 17 серп. 2013, at 09:15, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
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-devhttps://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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes, so I'll add corresponding projects to the Moose team on SmalltalkHub, OK?
Uko
On 20 серп. 2013, at 13:00, Tudor Girba tudor@tudorgirba.com wrote:
Well, you can start splitting the project anyway.
Doru
On Tue, Aug 20, 2013 at 11:55 AM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote: Ok, so as far as I understand - we'll release Moose 4.8 and then I can start to integrate FAST into Moose 5?
Uko
On 17 серп. 2013, at 09:15, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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
Hi everyone!
I've done quite a lot of work on FAST restructuring and now there are 3 separate projects: http://www.smalltalkhub.com/#!/~Moose/FASTCore http://www.smalltalkhub.com/#!/~Moose/FASTPharo http://www.smalltalkhub.com/#!/~Moose/FASTJava An image with everything loaded can be fetched from here: https://ci.inria.fr/moose/job/FAST-On-Moose/lastSuccessfulBuild/artifact/FAS...
Feedback is appreciated :)
Uko
On 20 серп. 2013, at 13:00, Tudor Girba tudor@tudorgirba.com wrote:
Well, you can start splitting the project anyway.
Doru
On Tue, Aug 20, 2013 at 11:55 AM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote: Ok, so as far as I understand - we'll release Moose 4.8 and then I can start to integrate FAST into Moose 5?
Uko
On 17 серп. 2013, at 09:15, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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
great!
thanks a lot for your continuous implication in the project
nicolas
On 08/30/2013 12:14 PM, Yuriy Tymchuk wrote:
Hi everyone!
I've done quite a lot of work on FAST restructuring and now there are 3 separate projects:
- http://www.smalltalkhub.com/#!/~Moose/FASTCore http://www.smalltalkhub.com/#%21/%7EMoose/FASTCore
- http://www.smalltalkhub.com/#!/~Moose/FASTPharo http://www.smalltalkhub.com/#%21/%7EMoose/FASTPharo
- http://www.smalltalkhub.com/#!/~Moose/FASTJava http://www.smalltalkhub.com/#%21/%7EMoose/FASTJava
An image with everything loaded can be fetched from here: https://ci.inria.fr/moose/job/FAST-On-Moose/lastSuccessfulBuild/artifact/FAS...
Feedback is appreciated :)
Uko
On 20 ????. 2013, at 13:00, Tudor Girba <tudor@tudorgirba.com mailto:tudor@tudorgirba.com> wrote:
Well, you can start splitting the project anyway.
Doru
On Tue, Aug 20, 2013 at 11:55 AM, Yuriy Tymchuk <yuriy.tymchuk@me.com mailto:yuriy.tymchuk@me.com> wrote:
Ok, so as far as I understand - we'll release Moose 4.8 and then I can start to integrate FAST into Moose 5? Uko On 17 ????. 2013, at 09:15, Yuriy Tymchuk <yuriy.tymchuk@me.com <mailto:yuriy.tymchuk@me.com>> wrote: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 <mailto: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 <mailto: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 <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com <http://www.tudorgirba.com/> "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev-- www.tudorgirba.com http://www.tudorgirba.com/
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch mailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 30 серп. 2013, at 14:36, Nicolas Anquetil Nicolas.Anquetil@inria.fr wrote:
great!
thanks a lot for your continuous implication in the project
Well, I'm responsible for what I've created :). Thank you for helping me during main development stage.
Uko
nicolas
On 08/30/2013 12:14 PM, Yuriy Tymchuk wrote:
Hi everyone!
I've done quite a lot of work on FAST restructuring and now there are 3 separate projects: http://www.smalltalkhub.com/#!/~Moose/FASTCore http://www.smalltalkhub.com/#!/~Moose/FASTPharo http://www.smalltalkhub.com/#!/~Moose/FASTJava An image with everything loaded can be fetched from here: https://ci.inria.fr/moose/job/FAST-On-Moose/lastSuccessfulBuild/artifact/FAS...
Feedback is appreciated :)
Uko
On 20 серп. 2013, at 13:00, Tudor Girba tudor@tudorgirba.com wrote:
Well, you can start splitting the project anyway.
Doru
On Tue, Aug 20, 2013 at 11:55 AM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote: Ok, so as far as I understand - we'll release Moose 4.8 and then I can start to integrate FAST into Moose 5?
Uko
On 17 серп. 2013, at 09:15, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Cool I'm trying to parse ADA so may be after we will see if we can get FASTAda :)
On Aug 30, 2013, at 12:14 PM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
Hi everyone!
I've done quite a lot of work on FAST restructuring and now there are 3 separate projects: http://www.smalltalkhub.com/#!/~Moose/FASTCore http://www.smalltalkhub.com/#!/~Moose/FASTPharo http://www.smalltalkhub.com/#!/~Moose/FASTJava An image with everything loaded can be fetched from here: https://ci.inria.fr/moose/job/FAST-On-Moose/lastSuccessfulBuild/artifact/FAS...
Feedback is appreciated :)
Uko
On 20 серп. 2013, at 13:00, Tudor Girba tudor@tudorgirba.com wrote:
Well, you can start splitting the project anyway.
Doru
On Tue, Aug 20, 2013 at 11:55 AM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote: Ok, so as far as I understand - we'll release Moose 4.8 and then I can start to integrate FAST into Moose 5?
Uko
On 17 серп. 2013, at 09:15, Yuriy Tymchuk yuriy.tymchuk@me.com wrote:
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Nicolas Anquetil -
Stéphane Ducasse -
Tudor Girba -
Yuriy Tymchuk