[Pharo-project] Fuel and Pharo Kernel
Hi, I tried the Fuel with Pharo Kernel and... it works well. It needs only very few modifications (removing of some dependencies). But the really great thing is that the FLPackageLoader seems to work quite well too. I do strongly recommend to add Fuel very early in the development of 1.5 into the basic kernel packages. I can not wait to see a Pharo image without the Compiler ;-) -- Pavel
On Tue, Apr 3, 2012 at 6:39 PM, Pavel Krivanek <pavel.krivanek@gmail.com>wrote:
Hi,
I tried the Fuel with Pharo Kernel and... it works well.
I am really happy to hear that.
It needs only very few modifications (removing of some dependencies).
Right now I am extremelly busy, but in 2 ways I can spend some time in Fuel. If you think that some of these dependencies removal could be applied directly to Fuel core, please let us know.
But the really great thing is that the FLPackageLoader seems to work quite well too.
Awesome.
I do strongly recommend to add Fuel very early in the development of 1.5 into the basic kernel packages.
Indeed. That was the idea for 1.4 but we didn't have time.
I can not wait to see a Pharo image without the Compiler ;-)
In fact that was one of the things Stef had in mind when he decided to support and push Fuel. Because RMOD is working in boostrap and related works where you would like to boostrap and grow without a compiler ;)
-- Pavel
-- Mariano http://marianopeck.wordpress.com
On Tue, Apr 3, 2012 at 7:36 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Tue, Apr 3, 2012 at 6:39 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I tried the Fuel with Pharo Kernel and... it works well.
I am really happy to hear that.
It needs only very few modifications (removing of some dependencies).
Right now I am extremelly busy, but in 2 ways I can spend some time in Fuel. If you think that some of these dependencies removal could be applied directly to Fuel core, please let us know.
Hm, I used packages from the Fuel CI image. As I see some things were changed. For the start, Fuel extensions of classes CharacterBlock and MetacelloGoferLoad should not be in the basic package.
But the really great thing is that the FLPackageLoader seems to work quite well too.
Awesome.
I do strongly recommend to add Fuel very early in the development of 1.5 into the basic kernel packages.
Indeed. That was the idea for 1.4 but we didn't have time.
I can not wait to see a Pharo image without the Compiler ;-)
In fact that was one of the things Stef had in mind when he decided to support and push Fuel. Because RMOD is working in boostrap and related works where you would like to boostrap and grow without a compiler ;)
I know, but I expected that package loading in Fuel has much wider dependencies and that it will require a lot of next work. -- Pavel
-- Pavel
-- Mariano http://marianopeck.wordpress.com
Nice :) FuelPackageLoader is a functional prototype but needs many improvements. I am elaborating a proposal for GSoC, with features like: basic: - emulate ClassBuilder (implies replacing it for something less monolithic): - validating the class definition - modifying an existent class - recompiling methods (superclass change tolerance) - mutating existing instances to the new format - registering the class as a global - send notifications - more - handle dependencies - good migration support - visual tool: integrate with Gofer or Monticello? extra: - run pre and post scripts (to avoid compilation the scripts should be fully serialized, not just the source code) - new extension operations: add trait, add variable. - clean uninstall: if an extension method overwrote an existing one, then it should be restored when package uninstalled (I think in VW is like this). - ? Some items require community discussion, especially the extra ones. Also, I'm not sure what should be in the scope of GSoC. Cheers, MartÃn On Tue, Apr 3, 2012 at 5:19 PM, Pavel Krivanek <pavel.krivanek@gmail.com>wrote:
On Tue, Apr 3, 2012 at 7:36 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Tue, Apr 3, 2012 at 6:39 PM, Pavel Krivanek <pavel.krivanek@gmail.com
wrote:
Hi,
I tried the Fuel with Pharo Kernel and... it works well.
I am really happy to hear that.
It needs only very few modifications (removing of some dependencies).
Right now I am extremelly busy, but in 2 ways I can spend some time in
Fuel.
If you think that some of these dependencies removal could be applied directly to Fuel core, please let us know.
Hm, I used packages from the Fuel CI image. As I see some things were changed. For the start, Fuel extensions of classes CharacterBlock and MetacelloGoferLoad should not be in the basic package.
But the really great thing is that the FLPackageLoader seems to work quite well too.
Awesome.
I do strongly recommend to add Fuel very early in the development of 1.5 into the basic kernel packages.
Indeed. That was the idea for 1.4 but we didn't have time.
I can not wait to see a Pharo image without the Compiler ;-)
In fact that was one of the things Stef had in mind when he decided to support and push Fuel. Because RMOD is working in boostrap and related
works
where you would like to boostrap and grow without a compiler ;)
I know, but I expected that package loading in Fuel has much wider dependencies and that it will require a lot of next work.
-- Pavel
-- Pavel
-- Mariano http://marianopeck.wordpress.com
On Apr 3, 2012, at 10:42 PM, Martin Dias wrote:
Nice :)
FuelPackageLoader is a functional prototype but needs many improvements. I am elaborating a proposal for GSoC, with features like:
basic: - emulate ClassBuilder (implies replacing it for something less monolithic): - validating the class definition - modifying an existent class - recompiling methods (superclass change tolerance) - mutating existing instances to the new format - registering the class as a global - send notifications - more - handle dependencies - good migration support - visual tool: integrate with Gofer or Monticello?
martin writing a new class builder is indeed a really nice and great ideas.
extra: - run pre and post scripts (to avoid compilation the scripts should be fully serialized, not just the source code) - new extension operations: add trait, add variable. - clean uninstall: if an extension method overwrote an existing one, then it should be restored when package uninstalled (I think in VW is like this). - ?
Some items require community discussion, especially the extra ones. Also, I'm not sure what should be in the scope of GSoC.
Cheers, MartÃn
On Tue, Apr 3, 2012 at 5:19 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote: On Tue, Apr 3, 2012 at 7:36 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Tue, Apr 3, 2012 at 6:39 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I tried the Fuel with Pharo Kernel and... it works well.
I am really happy to hear that.
It needs only very few modifications (removing of some dependencies).
Right now I am extremelly busy, but in 2 ways I can spend some time in Fuel. If you think that some of these dependencies removal could be applied directly to Fuel core, please let us know.
Hm, I used packages from the Fuel CI image. As I see some things were changed. For the start, Fuel extensions of classes CharacterBlock and MetacelloGoferLoad should not be in the basic package.
But the really great thing is that the FLPackageLoader seems to work quite well too.
Awesome.
I do strongly recommend to add Fuel very early in the development of 1.5 into the basic kernel packages.
Indeed. That was the idea for 1.4 but we didn't have time.
I can not wait to see a Pharo image without the Compiler ;-)
In fact that was one of the things Stef had in mind when he decided to support and push Fuel. Because RMOD is working in boostrap and related works where you would like to boostrap and grow without a compiler ;)
I know, but I expected that package loading in Fuel has much wider dependencies and that it will require a lot of next work.
-- Pavel
-- Pavel
-- Mariano http://marianopeck.wordpress.com
I do strongly recommend to add Fuel very early in the development of 1.5 into the basic kernel packages.
:) Marcus added in the todo (BTW he should invite to the todo board we are just opening) to handle the old reference streamâ¦. :)
Indeed. That was the idea for 1.4 but we didn't have time.
I can not wait to see a Pharo image without the Compiler ;-)
the dream will come true :) Since 1998 I want that, it is cool to see the vision getting reality because after we can do a lot more :)
In fact that was one of the things Stef had in mind when he decided to support and push Fuel. Because RMOD is working in boostrap and related works where you would like to boostrap and grow without a compiler ;)
Mariano, Pavel knows it too because we talk about that years ago. Stef
Hi--
I can not wait to see a Pharo image without the Compiler ;-)
the dream will come true :) Since 1998 I want that, it is cool to see the vision getting reality because after we can do a lot more :)
Just FYI, Spoon[1] has been like that for years. thanks, -C [1] http://thiscontext.wordpress.com -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468 + 1 250 607 7393
participants (5)
-
Craig Latta -
Mariano Martinez Peck -
Martin Dias -
Pavel Krivanek -
Stéphane Ducasse