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."
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@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@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@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
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@gmail.comwrote:
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@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing listMoose-dev@iam.unibe.chhttps://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
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@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@gmail.comwrote:
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@tudorgirba.comwrote:
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing listMoose-dev@iam.unibe.chhttps://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
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@gmail.com wrote:
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@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@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@tudorgirba.comwrote:
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing listMoose-dev@iam.unibe.chhttps://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
On Fri, Mar 15, 2013 at 4:32 PM, Tudor Girba tudor@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.
@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@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@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@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 https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@gmail.comwrote:
@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@gmail.comwrote:
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@tudorgirba.comwrote:
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing listMoose-dev@iam.unibe.chhttps://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 listMoose-dev@iam.unibe.chhttps://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
Roassal loads cleanly and Fuel is not dirty anymore.
Thanks, Doru
On Mar 15, 2013, at 4:32 PM, Tudor Girba tudor@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@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@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: filenameHope to help
Martin
On Fri, Mar 15, 2013 at 7:28 AM, Tudor Girba 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
"Next time you see your life passing by, say 'hi' and get to know her."
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
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Live like you mean it."
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@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@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@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: filenameHope to help
Martin
On Fri, Mar 15, 2013 at 7:28 AM, Tudor Girba 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
"Next time you see your life passing by, say 'hi' and get to know her."
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
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Martin Dias -
Tudor Girba -
Vanessa Peña Araya