roassal still loads fuel

List overview All Threads
Download

newer

older

grease-core extensions that exist...

cleaning moose

Tudor Girba

15 Mar 2013 15 Mar '13

7:28 a.m.

Show replies by date

Martin Dias

15 Mar 15 Mar

10:59 a.m.

...

Hi, Roassal still loads Fuel in Pharo 2.0, and this makes the package dirty, because it already exists in Pharo. Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Vanessa Peña Araya

4:54 p.m.

...

Hi We didn't announce the new 1.9 version yet (we are very very close). But actually it's available if Roassal want to try it. If ConfigurationOfRoassal would use '1.9' or #stable or #development, then it shouldn't be dirty. Additionally, the method ROFuelExporter>>exportView:onFileNamed: can remove the workaround that was needed with Fuel 1.8, and just do: FLSerializer serialize: view toFileNamed: filename Hope to help Martin On Fri, Mar 15, 2013 at 7:28 AM, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: Hi, Roassal still loads Fuel in Pharo 2.0, and this makes the package dirty, because it already exists in Pharo. Cheers, Doru -- www.tudorgirba.com <http://www.tudorgirba.com> "Next time you see your life passing by, say 'hi' and get to know her." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@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

Tudor Girba

4:07 p.m.

...

Hi, But as far as I understand is better not to load anything as 2.0 includes Fuel, isn't it? Ok, I'll change to FLSerializer serialize: view toFileNamed: filename Thanks, Vanessa. On 03/15/2013 05:59 AM, Martin Dias wrote: Hi We didn't announce the new 1.9 version yet (we are very very close). But actually it's available if Roassal want to try it. If ConfigurationOfRoassal would use '1.9' or #stable or #development, then it shouldn't be dirty. Additionally, the method ROFuelExporter>>exportView:onFileNamed: can remove the workaround that was needed with Fuel 1.8, and just do: FLSerializer serialize: view toFileNamed: filename Hope to help Martin On Fri, Mar 15, 2013 at 7:28 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:

_______________________________________________ Moose-dev mailing listMoose-dev@iam.unibe.chhttps://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

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

Martin Dias

4:27 p.m.

It depends, if you remove the metacello dependency, then it people won't be able to install on an image previous to Pharo 2.0. Is that the idea? On Fri, Mar 15, 2013 at 4:07 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:

...

-- 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

Tudor Girba

4:32 p.m.

No :). We should just ensure that it does not get loaded in Pharo 2.0 with the Metacello mechanism. Cheers, Doru On Fri, Mar 15, 2013 at 4:27 PM, Martin Dias <tinchodias(a)gmail.com> wrote:

...

wrote:

_______________________________________________ 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"

Martin Dias

5:09 p.m.

On Fri, Mar 15, 2013 at 4:32 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:

...

No :). We should just ensure that it does not get loaded in Pharo 2.0 with the Metacello mechanism.

Well, if you evaluate in latest Pharo 2.0: Gofer new squeaksource3: 'Fuel'; configuration; load. (ConfigurationOfFuel project version: #stable) load. the only package installed is ConfigurationOfFuel. Each package of fuel 1.9 default configuration already comes in the image.

Vanessa Peña Araya

5:24 p.m.

@Doru I just commited, can you try please? Vanessa. On 03/15/2013 11:07 AM, Tudor Girba wrote:

...

Yes, I would say it is better to not use anything, because you actually do not need those details. @Vanessa: could you take care of creating a new baseline (and pointing #development to it) without Fuel? Cheers, Doru On Fri, Mar 15, 2013 at 4:54 PM, Vanessa Peña Araya <van.c.pena(a)gmail.com <mailto:van.c.pena@gmail.com>> wrote: Hi, But as far as I understand is better not to load anything as 2.0 includes Fuel, isn't it? Ok, I'll change to FLSerializer serialize: view toFileNamed: filename Thanks, Vanessa. On 03/15/2013 05:59 AM, Martin Dias wrote:

Hi We didn't announce the new 1.9 version yet (we are very very close). But actually it's available if Roassal want to try it. If ConfigurationOfRoassal would use '1.9' or #stable or #development, then it shouldn't be dirty. Additionally, the method ROFuelExporter>>exportView:onFileNamed: can remove the workaround that was needed with Fuel 1.8, and just do: FLSerializer serialize: view toFileNamed: filename Hope to help Martin On Fri, Mar 15, 2013 at 7:28 AM, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: Hi, Roassal still loads Fuel in Pharo 2.0, and this makes the package dirty, because it already exists in Pharo. Cheers, Doru -- www.tudorgirba.com <http://www.tudorgirba.com> "Next time you see your life passing by, say 'hi' and get to know her." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________ Moose-dev mailing list Moose-dev(a)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(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Tudor Girba

4:32 p.m.

Thanks. I did not yet take a look, but I started a Moose build. Doru On Fri, Mar 15, 2013 at 5:24 PM, Vanessa Peña Araya <van.c.pena(a)gmail.com>wrote;wrote:

...

@Doru I just commited, can you try please? Vanessa. On 03/15/2013 11:07 AM, Tudor Girba wrote: Yes, I would say it is better to not use anything, because you actually do not need those details. @Vanessa: could you take care of creating a new baseline (and pointing #development to it) without Fuel? Cheers, Doru On Fri, Mar 15, 2013 at 4:54 PM, Vanessa Peña Araya <van.c.pena(a)gmail.com>wrote;wrote:

-- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing listMoose-dev@iam.unibe.chhttps://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

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

Tudor Girba

9:19 p.m.

Roassal loads cleanly and Fuel is not dirty anymore. Thanks, Doru On Mar 15, 2013, at 4:32 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:

...

Thanks. I did not yet take a look, but I started a Moose build. Doru On Fri, Mar 15, 2013 at 5:24 PM, Vanessa Peña Araya <van.c.pena(a)gmail.com> wrote: @Doru I just commited, can you try please? Vanessa. On 03/15/2013 11:07 AM, Tudor Girba wrote:

Yes, I would say it is better to not use anything, because you actually do not need those details. @Vanessa: could you take care of creating a new baseline (and pointing #development to it) without Fuel? Cheers, Doru On Fri, Mar 15, 2013 at 4:54 PM, Vanessa Peña Araya <van.c.pena(a)gmail.com> wrote: Hi, But as far as I understand is better not to load anything as 2.0 includes Fuel, isn't it? Ok, I'll change to FLSerializer serialize: view toFileNamed: filename Thanks, Vanessa. On 03/15/2013 05:59 AM, Martin Dias wrote:

Hi We didn't announce the new 1.9 version yet (we are very very close). But actually it's available if Roassal want to try it. If ConfigurationOfRoassal would use '1.9' or #stable or #development, then it shouldn't be dirty. Additionally, the method ROFuelExporter>>exportView:onFileNamed: can remove the workaround that was needed with Fuel 1.8, and just do: FLSerializer serialize: view toFileNamed: filename Hope to help Martin On Fri, Mar 15, 2013 at 7:28 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: Hi, Roassal still loads Fuel in Pharo 2.0, and this makes the package dirty, because it already exists in Pharo. Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her." _______________________________________________ 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

_______________________________________________ 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

-- www.tudorgirba.com "Live like you mean it."

Vanessa Peña Araya

10:38 p.m.

Nice! :) Vanessa. On 03/15/2013 04:19 PM, Tudor Girba wrote:

...

Roassal loads cleanly and Fuel is not dirty anymore. Thanks, Doru On Mar 15, 2013, at 4:32 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:

Yes, I would say it is better to not use anything, because you actually do not need those details. @Vanessa: could you take care of creating a new baseline (and pointing #development to it) without Fuel? Cheers, Doru On Fri, Mar 15, 2013 at 4:54 PM, Vanessa Peña Araya <van.c.pena(a)gmail.com> wrote: Hi, But as far as I understand is better not to load anything as 2.0 includes Fuel, isn't it? Ok, I'll change to FLSerializer serialize: view toFileNamed: filename Thanks, Vanessa. On 03/15/2013 05:59 AM, Martin Dias wrote:

Hi We didn't announce the new 1.9 version yet (we are very very close). But actually it's available if Roassal want to try it. If ConfigurationOfRoassal would use '1.9' or #stable or #development, then it shouldn't be dirty. Additionally, the method ROFuelExporter>>exportView:onFileNamed: can remove the workaround that was needed with Fuel 1.8, and just do: FLSerializer serialize: view toFileNamed: filename Hope to help Martin On Fri, Mar 15, 2013 at 7:28 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: Hi, Roassal still loads Fuel in Pharo 2.0, and this makes the package dirty, because it already exists in Pharo. Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her." _______________________________________________ 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

-- www.tudorgirba.com "Live like you mean it." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

4524

days inactive

4524

days old

moose-dev@list.inf.unibe.ch

Manage subscription

10 comments

3 participants

tags (0)

participants (3)

Martin Dias
Tudor Girba
Vanessa Peña Araya