September 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by Guillermo Polito

Hmmm, I don't think that Fuel has to be related with Monticello. They have different intentions :). But having binary packaging is great! :) What comes next is a way of organize the binary distributions :P. Guille On Sat, Sep 24, 2011 at 5:30 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Sat, Sep 24, 2011 at 10:22 PM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > >> On 24 September 2011 20:51, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> > >> > >> > On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <frank.shearar(a)gmail.com >> > >> > wrote: >> >> >> >> On 24 September 2011 20:40, Mariano Martinez Peck < >> marianopeck(a)gmail.com> >> >> wrote: >> >> > >> >> > >> >> > On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar < >> frank.shearar(a)gmail.com> >> >> > wrote: >> >> >> >> >> >> On 24 September 2011 20:01, Mariano Martinez Peck >> >> >> <marianopeck(a)gmail.com> >> >> >> wrote: >> >> >> > Well...Martin and I have been working a little bit this week and >> here >> >> >> > is >> >> >> > a >> >> >> > post explaining it: >> >> >> > >> >> >> > >> >> >> > >> http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… >> >> >> >> >> >> Cool! >> >> >> >> >> >> If I understand correctly, Fuel and Monticello (1; I don't know >> >> >> anything about 2 other than noone seems to use it but it's much >> >> >> better) accomplish two different things though: Fuel's a mechanism >> to >> >> >> quickly load a bunch of stuff, while Monticello's much more >> >> >> introspective: mainly, a bunch of definitions of things, with a >> >> >> history pointing to previous versions of the package. >> >> >> >> >> > >> >> > Yes. >> >> > >> >> >> >> >> >> I don't see how Fuel could replace Monticello, >> >> > >> >> > No, Fuel won't replace Monticello at all. They are different things. >> >> >> >> Ah, OK. That means I misinterpreted "As you may imagine the idea is >> >> that maybe in the future we can replace Monticelloâ mcz with Fuel >> >> packages." You meant in the sense of an mcz being something you load >> >> in your image, not somehow extending Fuel to a version control system >> >> (which would ... not make sense :) ). >> >> >> > >> > Exactly. Maybe the comment was not clear. What I mean is to change >> > Monticello in the way that instead of serializing code into a mzc that >> > contains the sources and the use the compiler, use Fuel to directly >> > store/load the code in a binary way. >> > Is that better explained? >> >> I think it's just my careless reading. The rest of the article's quite >> clear - "As you may know, Fuel is a plain object graph serializer. No >> more than that." - and so on. >> >> > :) > > >> I can't wait: a super fast package loader makes it cheap and easy to >> build up images from recipes. Nice! >> >> > Yes, me too. Problem is that neither Martin or I know very much about > Monticello. Even more, we prefer to focus in Fuel itself. We consider Fuel > Package Loader as a proof of concept for a real project. Hopefully, someone > can join and take care of it. Otherwise, we will try to make progres, but > slowly :( > > > > >> frank >> >> >> >> then, except in the >> >> >> sense of "here's a chunk of stuff you can load into your image" - >> >> >> which makes me think that one could simply replace the snapshot.bin >> >> >> with a snapshot.fuel (or simply put it in the same directory, for a >> >> >> loss in space but a gain in compatibility) and you'd have a much >> >> >> faster loading mcz, right? >> >> > >> >> > Exactly. With Monticello right now you have to compile the >> sources.st, >> >> > which >> >> > may be slow and even more you need the compiler. The idea is to >> >> > experiment a >> >> > way of using Monticello to directly store binary/already compiled >> code. >> >> > This way, it may be faster for exporting/importing the code. >> >> > So....in summary, we will try to experiment to replace only a small >> part >> >> > of >> >> > Monticello ;) >> >> >> >> Ah, excellent! I can't wait! >> >> >> >> >> frank >> >> >> >> >> >> > Cheers >> >> >> > >> >> >> > On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe >> >> >> > <sven(a)beta9.be> >> >> >> > wrote: >> >> >> >> >> >> >> >> On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote: >> >> >> >> >> >> >> >> > Cool Martin. Now I could do it as well. I have exported the >> groups >> >> >> >> > 'Core', 'Tests' and 'Zinc-Seaside'. >> >> >> >> > Then I materialize it a clean image and all tests (1567) are >> >> >> >> > green. >> >> >> >> > And >> >> >> >> > it only takes 7 seconds :) >> >> >> >> >> >> >> >> Great ! >> >> >> >> >> >> >> >> I want to try this myself soon. >> >> >> >> >> >> >> >> Sven >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> seaside mailing list >> >> >> >> seaside(a)lists.squeakfoundation.org >> >> >> >> >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> >> > >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > Mariano >> >> >> > http://marianopeck.wordpress.com >> >> >> > >> >> >> > >> >> >> >> >> > >> >> > >> >> > >> >> > -- >> >> > Mariano >> >> > http://marianopeck.wordpress.com >> >> > >> >> > >> >> >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> > >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

Sept. 24, 2011

Re: [Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by StÃ©phane Ducasse

> > > I can't wait: a super fast package loader makes it cheap and easy to > build up images from recipes. Nice! this was always the vision I got since I proposed this topics to tristan :) > > > Yes, me too. Problem is that neither Martin or I know very much about Monticello. Even more, we prefer to focus in Fuel itself. We consider Fuel Package Loader as a proof of concept for a real project. Hopefully, someone can join and take care of it. Otherwise, we will try to make progres, but slowly :( Yes but this is the best way. Making fuel robust fast and covering all the difficult aspects will make sure that we can use it in MC or other places. Keep your excellent work. Stef

Sept. 24, 2011

Re: [Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by Mariano Martinez Peck

On Sat, Sep 24, 2011 at 10:22 PM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > On 24 September 2011 20:51, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > > > On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <frank.shearar(a)gmail.com> > > wrote: > >> > >> On 24 September 2011 20:40, Mariano Martinez Peck < > marianopeck(a)gmail.com> > >> wrote: > >> > > >> > > >> > On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar < > frank.shearar(a)gmail.com> > >> > wrote: > >> >> > >> >> On 24 September 2011 20:01, Mariano Martinez Peck > >> >> <marianopeck(a)gmail.com> > >> >> wrote: > >> >> > Well...Martin and I have been working a little bit this week and > here > >> >> > is > >> >> > a > >> >> > post explaining it: > >> >> > > >> >> > > >> >> > > http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… > >> >> > >> >> Cool! > >> >> > >> >> If I understand correctly, Fuel and Monticello (1; I don't know > >> >> anything about 2 other than noone seems to use it but it's much > >> >> better) accomplish two different things though: Fuel's a mechanism to > >> >> quickly load a bunch of stuff, while Monticello's much more > >> >> introspective: mainly, a bunch of definitions of things, with a > >> >> history pointing to previous versions of the package. > >> >> > >> > > >> > Yes. > >> > > >> >> > >> >> I don't see how Fuel could replace Monticello, > >> > > >> > No, Fuel won't replace Monticello at all. They are different things. > >> > >> Ah, OK. That means I misinterpreted "As you may imagine the idea is > >> that maybe in the future we can replace Monticelloâ mcz with Fuel > >> packages." You meant in the sense of an mcz being something you load > >> in your image, not somehow extending Fuel to a version control system > >> (which would ... not make sense :) ). > >> > > > > Exactly. Maybe the comment was not clear. What I mean is to change > > Monticello in the way that instead of serializing code into a mzc that > > contains the sources and the use the compiler, use Fuel to directly > > store/load the code in a binary way. > > Is that better explained? > > I think it's just my careless reading. The rest of the article's quite > clear - "As you may know, Fuel is a plain object graph serializer. No > more than that." - and so on. > > :) > I can't wait: a super fast package loader makes it cheap and easy to > build up images from recipes. Nice! > > Yes, me too. Problem is that neither Martin or I know very much about Monticello. Even more, we prefer to focus in Fuel itself. We consider Fuel Package Loader as a proof of concept for a real project. Hopefully, someone can join and take care of it. Otherwise, we will try to make progres, but slowly :( > frank > > >> >> then, except in the > >> >> sense of "here's a chunk of stuff you can load into your image" - > >> >> which makes me think that one could simply replace the snapshot.bin > >> >> with a snapshot.fuel (or simply put it in the same directory, for a > >> >> loss in space but a gain in compatibility) and you'd have a much > >> >> faster loading mcz, right? > >> > > >> > Exactly. With Monticello right now you have to compile the sources.st > , > >> > which > >> > may be slow and even more you need the compiler. The idea is to > >> > experiment a > >> > way of using Monticello to directly store binary/already compiled > code. > >> > This way, it may be faster for exporting/importing the code. > >> > So....in summary, we will try to experiment to replace only a small > part > >> > of > >> > Monticello ;) > >> > >> Ah, excellent! I can't wait! > >> > >> >> frank > >> >> > >> >> > Cheers > >> >> > > >> >> > On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe > >> >> > <sven(a)beta9.be> > >> >> > wrote: > >> >> >> > >> >> >> On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote: > >> >> >> > >> >> >> > Cool Martin. Now I could do it as well. I have exported the > groups > >> >> >> > 'Core', 'Tests' and 'Zinc-Seaside'. > >> >> >> > Then I materialize it a clean image and all tests (1567) are > >> >> >> > green. > >> >> >> > And > >> >> >> > it only takes 7 seconds :) > >> >> >> > >> >> >> Great ! > >> >> >> > >> >> >> I want to try this myself soon. > >> >> >> > >> >> >> Sven > >> >> >> > >> >> >> _______________________________________________ > >> >> >> seaside mailing list > >> >> >> seaside(a)lists.squeakfoundation.org > >> >> >> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >> >> > > >> >> > > >> >> > > >> >> > -- > >> >> > Mariano > >> >> > http://marianopeck.wordpress.com > >> >> > > >> >> > > >> >> > >> > > >> > > >> > > >> > -- > >> > Mariano > >> > http://marianopeck.wordpress.com > >> > > >> > > >> > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- Mariano http://marianopeck.wordpress.com

Sept. 24, 2011

Re: [Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by Frank Shearar

On 24 September 2011 20:51, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <frank.shearar(a)gmail.com> > wrote: >> >> On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> > >> > >> > On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar(a)gmail.com> >> > wrote: >> >> >> >> On 24 September 2011 20:01, Mariano Martinez Peck >> >> <marianopeck(a)gmail.com> >> >> wrote: >> >> > Well...Martin and I have been working a little bit this week and here >> >> > is >> >> > a >> >> > post explaining it: >> >> > >> >> > >> >> > http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… >> >> >> >> Cool! >> >> >> >> If I understand correctly, Fuel and Monticello (1; I don't know >> >> anything about 2 other than noone seems to use it but it's much >> >> better) accomplish two different things though: Fuel's a mechanism to >> >> quickly load a bunch of stuff, while Monticello's much more >> >> introspective: mainly, a bunch of definitions of things, with a >> >> history pointing to previous versions of the package. >> >> >> > >> > Yes. >> > >> >> >> >> I don't see how Fuel could replace Monticello, >> > >> > No, Fuel won't replace Monticello at all. They are different things. >> >> Ah, OK. That means I misinterpreted "As you may imagine the idea is >> that maybe in the future we can replace Monticelloâ mcz with Fuel >> packages." You meant in the sense of an mcz being something you load >> in your image, not somehow extending Fuel to a version control system >> (which would ... not make sense :) ). >> > > Exactly. Maybe the comment was not clear. What I mean is to change > Monticello in the way that instead of serializing code into a mzc that > contains the sources and the use the compiler, use Fuel to directly > store/load the code in a binary way. > Is that better explained? I think it's just my careless reading. The rest of the article's quite clear - "As you may know, Fuel is a plain object graph serializer. No more than that." - and so on. I can't wait: a super fast package loader makes it cheap and easy to build up images from recipes. Nice! frank >> >> then, except in the >> >> sense of "here's a chunk of stuff you can load into your image" - >> >> which makes me think that one could simply replace the snapshot.bin >> >> with a snapshot.fuel (or simply put it in the same directory, for a >> >> loss in space but a gain in compatibility) and you'd have a much >> >> faster loading mcz, right? >> > >> > Exactly. With Monticello right now you have to compile the sources.st, >> > which >> > may be slow and even more you need the compiler. The idea is to >> > experiment a >> > way of using Monticello to directly store binary/already compiled code. >> > This way, it may be faster for exporting/importing the code. >> > So....in summary, we will try to experiment to replace only a small part >> > of >> > Monticello ;) >> >> Ah, excellent! I can't wait! >> >> >> frank >> >> >> >> > Cheers >> >> > >> >> > On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe >> >> > <sven(a)beta9.be> >> >> > wrote: >> >> >> >> >> >> On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote: >> >> >> >> >> >> > Cool Martin. Now I could do it as well. I have exported the groups >> >> >> > 'Core', 'Tests' and 'Zinc-Seaside'. >> >> >> > Then I materialize it a clean image and all tests (1567) are >> >> >> > green. >> >> >> > And >> >> >> > it only takes 7 seconds :) >> >> >> >> >> >> Great ! >> >> >> >> >> >> I want to try this myself soon. >> >> >> >> >> >> Sven >> >> >> >> >> >> _______________________________________________ >> >> >> seaside mailing list >> >> >> seaside(a)lists.squeakfoundation.org >> >> >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> > >> >> > >> >> > >> >> > -- >> >> > Mariano >> >> > http://marianopeck.wordpress.com >> >> > >> >> > >> >> >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> > >> > > > > -- > Mariano > http://marianopeck.wordpress.com > >

Sept. 24, 2011

Re: [Pharo-project] Class creation notification

by Luc Fabresse

2011/9/23 Mariano Martinez Peck <marianopeck(a)gmail.com> > grrr shorcuts.. then I found AutomaticMethodCategorizerApplier which I > don't care. > And I don't care if I need to close and open again the TestRunner. > > So....what I mean is that class creation notification increases Fuel > classes materialization like 50%. Do you think this is un-important enough > to provide a way to NOT notify? I mean, should I provide a way to avoid that > and avoid the 50% ? or it will be totally unsafe? > I have no idea how notification works. I imagine that every class creation is notified. Perhaps it could be faster to notify only time that multiple classes have created. of course it requires a way to create classes without notifying. just an idea, Luc > > Thanks! > > > > > > On Fri, Sep 23, 2011 at 7:52 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Hi guys. I was checking who needs to be notified when a class is created. >> If I follow correctly senders of #notify:ofSystemChangesOfItem:change:using: >> and friends, I don't really find too many listeners. I found TestRunner >> >> initialize and MCPackageManager >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

Sept. 24, 2011

Re: [Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by Mariano Martinez Peck

On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > > > On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar(a)gmail.com> > > wrote: > >> > >> On 24 September 2011 20:01, Mariano Martinez Peck < > marianopeck(a)gmail.com> > >> wrote: > >> > Well...Martin and I have been working a little bit this week and here > is > >> > a > >> > post explaining it: > >> > > >> > > http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… > >> > >> Cool! > >> > >> If I understand correctly, Fuel and Monticello (1; I don't know > >> anything about 2 other than noone seems to use it but it's much > >> better) accomplish two different things though: Fuel's a mechanism to > >> quickly load a bunch of stuff, while Monticello's much more > >> introspective: mainly, a bunch of definitions of things, with a > >> history pointing to previous versions of the package. > >> > > > > Yes. > > > >> > >> I don't see how Fuel could replace Monticello, > > > > No, Fuel won't replace Monticello at all. They are different things. > > Ah, OK. That means I misinterpreted "As you may imagine the idea is > that maybe in the future we can replace Monticelloâ mcz with Fuel > packages." You meant in the sense of an mcz being something you load > in your image, not somehow extending Fuel to a version control system > (which would ... not make sense :) ). > > Exactly. Maybe the comment was not clear. What I mean is to change Monticello in the way that instead of serializing code into a mzc that contains the sources and the use the compiler, use Fuel to directly store/load the code in a binary way. Is that better explained? > >> then, except in the > >> sense of "here's a chunk of stuff you can load into your image" - > >> which makes me think that one could simply replace the snapshot.bin > >> with a snapshot.fuel (or simply put it in the same directory, for a > >> loss in space but a gain in compatibility) and you'd have a much > >> faster loading mcz, right? > > > > Exactly. With Monticello right now you have to compile the sources.st, > which > > may be slow and even more you need the compiler. The idea is to > experiment a > > way of using Monticello to directly store binary/already compiled code. > > This way, it may be faster for exporting/importing the code. > > So....in summary, we will try to experiment to replace only a small part > of > > Monticello ;) > > Ah, excellent! I can't wait! > > >> frank > >> > >> > Cheers > >> > > >> > On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe < > sven(a)beta9.be> > >> > wrote: > >> >> > >> >> On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote: > >> >> > >> >> > Cool Martin. Now I could do it as well. I have exported the groups > >> >> > 'Core', 'Tests' and 'Zinc-Seaside'. > >> >> > Then I materialize it a clean image and all tests (1567) are green. > >> >> > And > >> >> > it only takes 7 seconds :) > >> >> > >> >> Great ! > >> >> > >> >> I want to try this myself soon. > >> >> > >> >> Sven > >> >> > >> >> _______________________________________________ > >> >> seaside mailing list > >> >> seaside(a)lists.squeakfoundation.org > >> >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >> > > >> > > >> > > >> > -- > >> > Mariano > >> > http://marianopeck.wordpress.com > >> > > >> > > >> > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- Mariano http://marianopeck.wordpress.com

Sept. 24, 2011

Re: [Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by Frank Shearar

On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar(a)gmail.com> > wrote: >> >> On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> > Well...Martin and I have been working a little bit this week and here is >> > a >> > post explaining it: >> > >> > http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… >> >> Cool! >> >> If I understand correctly, Fuel and Monticello (1; I don't know >> anything about 2 other than noone seems to use it but it's much >> better) accomplish two different things though: Fuel's a mechanism to >> quickly load a bunch of stuff, while Monticello's much more >> introspective: mainly, a bunch of definitions of things, with a >> history pointing to previous versions of the package. >> > > Yes. > >> >> I don't see how Fuel could replace Monticello, > > No, Fuel won't replace Monticello at all. They are different things. Ah, OK. That means I misinterpreted "As you may imagine the idea is that maybe in the future we can replace Monticelloâ mcz with Fuel packages." You meant in the sense of an mcz being something you load in your image, not somehow extending Fuel to a version control system (which would ... not make sense :) ). >> then, except in the >> sense of "here's a chunk of stuff you can load into your image" - >> which makes me think that one could simply replace the snapshot.bin >> with a snapshot.fuel (or simply put it in the same directory, for a >> loss in space but a gain in compatibility) and you'd have a much >> faster loading mcz, right? > > Exactly. With Monticello right now you have to compile the sources.st, which > may be slow and even more you need the compiler. The idea is to experiment a > way of using Monticello to directly store binary/already compiled code. > This way, it may be faster for exporting/importing the code. > So....in summary, we will try to experiment to replace only a small part of > Monticello ;) Ah, excellent! I can't wait! >> frank >> >> > Cheers >> > >> > On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven(a)beta9.be> >> > wrote: >> >> >> >> On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote: >> >> >> >> > Cool Martin. Now I could do it as well. I have exported the groups >> >> > 'Core', 'Tests' and 'Zinc-Seaside'. >> >> > Then I materialize it a clean image and all tests (1567) are green. >> >> > And >> >> > it only takes 7 seconds :) >> >> >> >> Great ! >> >> >> >> I want to try this myself soon. >> >> >> >> Sven >> >> >> >> _______________________________________________ >> >> seaside mailing list >> >> seaside(a)lists.squeakfoundation.org >> >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> > >> > > > > -- > Mariano > http://marianopeck.wordpress.com > >

Sept. 24, 2011

Re: [Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by Mariano Martinez Peck

On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > Well...Martin and I have been working a little bit this week and here is > a > > post explaining it: > > > http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… > > Cool! > > If I understand correctly, Fuel and Monticello (1; I don't know > anything about 2 other than noone seems to use it but it's much > better) accomplish two different things though: Fuel's a mechanism to > quickly load a bunch of stuff, while Monticello's much more > introspective: mainly, a bunch of definitions of things, with a > history pointing to previous versions of the package. > > Yes. > I don't see how Fuel could replace Monticello, No, Fuel won't replace Monticello at all. They are different things. > then, except in the > sense of "here's a chunk of stuff you can load into your image" - > which makes me think that one could simply replace the snapshot.bin > with a snapshot.fuel (or simply put it in the same directory, for a > loss in space but a gain in compatibility) and you'd have a much > faster loading mcz, right? > Exactly. With Monticello right now you have to compile the sources.st, which may be slow and even more you need the compiler. The idea is to experiment a way of using Monticello to directly store binary/already compiled code. This way, it may be faster for exporting/importing the code. So....in summary, we will try to experiment to replace only a small part of Monticello ;) > frank > > > Cheers > > > > On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven(a)beta9.be> > > wrote: > >> > >> On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote: > >> > >> > Cool Martin. Now I could do it as well. I have exported the groups > >> > 'Core', 'Tests' and 'Zinc-Seaside'. > >> > Then I materialize it a clean image and all tests (1567) are green. > And > >> > it only takes 7 seconds :) > >> > >> Great ! > >> > >> I want to try this myself soon. > >> > >> Sven > >> > >> _______________________________________________ > >> seaside mailing list > >> seaside(a)lists.squeakfoundation.org > >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- Mariano http://marianopeck.wordpress.com

Sept. 24, 2011

Re: [Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by Frank Shearar

On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Well...Martin and I have been working a little bit this week and here is a > post explaining it: > http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… Cool! If I understand correctly, Fuel and Monticello (1; I don't know anything about 2 other than noone seems to use it but it's much better) accomplish two different things though: Fuel's a mechanism to quickly load a bunch of stuff, while Monticello's much more introspective: mainly, a bunch of definitions of things, with a history pointing to previous versions of the package. I don't see how Fuel could replace Monticello, then, except in the sense of "here's a chunk of stuff you can load into your image" - which makes me think that one could simply replace the snapshot.bin with a snapshot.fuel (or simply put it in the same directory, for a loss in space but a gain in compatibility) and you'd have a much faster loading mcz, right? frank > Cheers > > On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven(a)beta9.be> > wrote: >> >> On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote: >> >> > Cool Martin. Now I could do it as well. I have exported the groups >> > 'Core', 'Tests' and 'Zinc-Seaside'. >> > Then I materialize it a clean image and all tests (1567) are green. And >> > it only takes 7 seconds :) >> >> Great ! >> >> I want to try this myself soon. >> >> Sven >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > -- > Mariano > http://marianopeck.wordpress.com > >

Sept. 24, 2011

[Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)

by Mariano Martinez Peck

Well...Martin and I have been working a little bit this week and here is a post explaining it: http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… Cheers On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 23 Sep 2011, at 11:47, Mariano Martinez Peck wrote: > > > Cool Martin. Now I could do it as well. I have exported the groups > 'Core', 'Tests' and 'Zinc-Seaside'. > > Then I materialize it a clean image and all tests (1567) are green. And > it only takes 7 seconds :) > > Great ! > > I want to try this myself soon. > > Sven > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Mariano http://marianopeck.wordpress.com

Sept. 24, 2011