[Pharo-project] Importing and exporting packages with Fuel [WAS] Re: [Seaside] Seaside not loading css styles (but our fault)
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-packages... Cheers On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven@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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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@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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar@gmail.com>wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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@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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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@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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <frank.shearar@gmail.com>wrote:
On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <
marianopeck@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-packages...
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@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@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
On 24 September 2011 20:51, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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@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@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
On Sat, Sep 24, 2011 at 10:22 PM, Frank Shearar <frank.shearar@gmail.com>wrote:
On 24 September 2011 20:51, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:40, Mariano Martinez Peck <
marianopeck@gmail.com>
wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <
frank.shearar@gmail.com>
wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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@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@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
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
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@gmail.com> wrote:
On Sat, Sep 24, 2011 at 10:22 PM, Frank Shearar <frank.shearar@gmail.com>wrote:
On 24 September 2011 20:51, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <frank.shearar@gmail.com
wrote:
On 24 September 2011 20:40, Mariano Martinez Peck <
marianopeck@gmail.com>
wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <
frank.shearar@gmail.com>
wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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@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@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
On Sat, Sep 24, 2011 at 10:53 PM, Guillermo Polito < guillermopolito@gmail.com> wrote:
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.
Well, in fact that was one of the ideas behind Fuel Package Loader. For those who knows Java, the idea is to provide a kind of Jar, that is, the code already compiled. With of course, the possibility to attach sources as well. Then for example you have your applicatio XXX that uses Seaside, then you can just build an image with seaside.fuel and that's all. No need of sources, no need of version history, etc... So...I think that for deploying purposes, it is also an interesting idea :)
Guille
On Sat, Sep 24, 2011 at 5:30 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 10:22 PM, Frank Shearar <frank.shearar@gmail.com>wrote:
On 24 September 2011 20:51, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:47 PM, Frank Shearar <
frank.shearar@gmail.com>
wrote:
On 24 September 2011 20:40, Mariano Martinez Peck <
marianopeck@gmail.com>
wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <
frank.shearar@gmail.com>
wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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@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@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
-- Mariano http://marianopeck.wordpress.com
On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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 ;)
I just did a bit of digging. It looks like source.st is there purely as a convenience. It looks like Monticello (i.e., MCPackageLoader) will look for snapshot.bin (or, failing that, the files snapshot/*). This file (or files) contains the list of definitions in the package. MCPackageLoader then walks over the definitions. frank
frank
Cheers
On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven@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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
On 25 September 2011 01:13, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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 ;)
I just did a bit of digging. It looks like source.st is there purely as a convenience. It looks like Monticello (i.e., MCPackageLoader) will look for snapshot.bin (or, failing that, the files snapshot/*). This file (or files) contains the list of definitions in the package. MCPackageLoader then walks over the definitions.
... and then compiles them :) Fuel can load stuff directly, without compilation.
frank
frank
Cheers
On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven@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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
-- Best regards, Igor Stasenko.
On 25 September 2011 03:50, Igor Stasenko <siguctua@gmail.com> wrote:
On 25 September 2011 01:13, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:40, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sat, Sep 24, 2011 at 9:34 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 24 September 2011 20:01, Mariano Martinez Peck <marianopeck@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-packages...
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 ;)
I just did a bit of digging. It looks like source.st is there purely as a convenience. It looks like Monticello (i.e., MCPackageLoader) will look for snapshot.bin (or, failing that, the files snapshot/*). This file (or files) contains the list of definitions in the package. MCPackageLoader then walks over the definitions.
... and then compiles them :) Fuel can load stuff directly, without compilation.
Yes, I know Fuel can. Monticello does too, as it happens: it only compiles new methods. Take a look at MCPackageLoader >> #basicLoad, which invokes MethodAddition >> #installMethod. My comment was merely to say that Monticello doesn't actually use source.st in its loading process (from what I can see). Fuel looks to do more, faster! frank
frank
frank
Cheers
On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven@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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
-- Best regards, Igor Stasenko.
I just did a bit of digging. It looks like source.st is there purely as a convenience. It looks like Monticello (i.e., MCPackageLoader) will look for snapshot.bin (or, failing that, the files snapshot/*). This file (or files) contains the list of definitions in the package. MCPackageLoader then walks over the definitions.
yes and this is important that the bin does not get desync else you publish packages and 3 months later they are broken. This happens to us when we started to fix MethodReference and friends. So soon we will migrate MC model to Ring to reduce the over head because a MC meta model uses pseudo class (I guess) and MethodReference a real "mille-feuilles". Stef
On Sat, Sep 24, 2011 at 9:01 PM, Mariano Martinez Peck < marianopeck@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-packages...
Well...I have just tried with Fuel 1.8 (will be released soon) but with a nice experiment: we also store source code in CompiledMethods :) So...the files increased like 50% (because of the source code), but the good news is that now we can load and have the sources as well. The load process took me now 14 seconds rather than 7. This is because of the source code but also because in this last version we also do system notifications of class creations, etc... Cheers
Cheers
On Fri, Sep 23, 2011 at 12:09 PM, Sven Van Caekenberghe <sven@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@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
participants (5)
-
Frank Shearar -
Guillermo Polito -
Igor Stasenko -
Mariano Martinez Peck -
Stéphane Ducasse