Re: [Pharo-project] Monticello enhancing
Thanks tobias This is cool to have that! With your experiment are loading MC definitions using fuel? Stef On Dec 2, 2011, at 4:54 PM, Tobias Pape wrote: > Dear all, > > afte Fuel being available for both Squeak and Pharo, > I experimented a little bit. > > So, I put a new snapshot.fuel beside the snapshot.bin in > the mcz zips (same for patch.* in mcd). > > But to make it easier in the future to experiment with things, > I included a small facility to extend serializers/materializers > or similar things more easily. How is it done? > > Example: new serializer in MCZ files: > After my patch, include > > MCMczWriter class>>serializerMine > > ^ [:writer :snapshot | writer writeSnapshotAsMyFormat: snapshot] > > and > > MCMczWriter>>writeSnapshotAsMyFormat: snapshot > > self addString: (self doSomeConversion: aSnapshot) at: > 'snapshot.myformat'. > > as Extension methods in MCMczWriter, and execute > > MCMczWriter populateSerializers. > > Now, a new file member is added to every new mcz file. > > As an example, I have done such thing for Fuel. > Don't worry, it just uses the default behavior if > Fuel is not present in either the image or the mcz-file. > > Best, > -Tobias > > PS: for Squeak, see Inbox Monticello-topa.491, >And I also have an MCD attached that should help using the code elsewhere. > > > >
Re: [Pharo-project] Monticello enhancing
On Sat, Dec 3, 2011 at 12:23 AM, Stéphane Ducasse wrote: > Thanks tobias > This is cool to have that! > With your experiment are loading MC definitions using fuel? > yes, loading and writing. Basically, for writing, for example, it is to change #writeSnapshot: or #serializeInBinary: to use Fuel instead of DataStream. For loading, #loadDefinitions Cheers > > Stef > > On Dec 2, 2011, at 4:54 PM, Tobias Pape wrote: > > > Dear all, > > > > afte Fuel being available for both Squeak and Pharo, > > I experimented a little bit. > > > > So, I put a new snapshot.fuel beside the snapshot.bin in > > the mcz zips (same for patch.* in mcd). > > > > But to make it easier in the future to experiment with things, > > I included a small facility to extend serializers/materializers > > or similar things more easily. How is it done? > > > > Example: new serializer in MCZ files: > > After my patch, include > > > > MCMczWriter class>>serializerMine > > > > ^ [:writer :snapshot | writer writeSnapshotAsMyFormat: snapshot] > > > > and > > > > MCMczWriter>>writeSnapshotAsMyFormat: snapshot > > > > self addString: (self doSomeConversion: aSnapshot) at: > 'snapshot.myformat'. > > > > as Extension methods in MCMczWriter, and execute > > > > MCMczWriter populateSerializers. > > > > Now, a new file member is added to every new mcz file. > > > > As an example, I have done such thing for Fuel. > > Don't worry, it just uses the default behavior if > > Fuel is not present in either the image or the mcz-file. > > > > Best, > > -Tobias > > > > PS: for Squeak, see Inbox Monticello-topa.491, > >And I also have an MCD attached that should help using the code > elsewhere. > > > > > > > > > > > > -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-project] Monticello enhancing
Am 2011-12-03 um 14:34 schrieb Mariano Martinez Peck:
>
>
>> On Sat, Dec 3, 2011 at 12:23 AM, Stéphane Ducasse
>> wrote:
>> Thanks tobias
>> This is cool to have that!
>> With your experiment are loading MC definitions using fuel?
>>
> yes, loading and writing. Basically, for writing, for example, it is to
> change #writeSnapshot: or #serializeInBinary: to use Fuel instead of
> DataStream.
> For loading, #loadDefinitions
No. that is the point.
you add a loderFuel to the class side of MCMc{d,z}Reader that
returns an association of priority -> oneargblock.
My proposal is about experimenting with the MC stuff _without_ changing
the present logic, but augmenting them.
See the FuelMonticello-topa.1.mcz for an example.
(note that this mcz already contains a snapshot.fuel ;) )
best
-Tobias
Re: [Pharo-project] Monticello enhancing
On Sat, Dec 3, 2011 at 3:46 PM, Tobias Pape wrote:
>
> Am 2011-12-03 um 14:34 schrieb Mariano Martinez Peck:
>
> >
> >
> >> On Sat, Dec 3, 2011 at 12:23 AM, Stéphane Ducasse <
> stephane.duca...@inria.fr> wrote:
> >> Thanks tobias
> >> This is cool to have that!
> >> With your experiment are loading MC definitions using fuel?
> >>
> > yes, loading and writing. Basically, for writing, for example, it is to
> change #writeSnapshot: or #serializeInBinary: to use Fuel instead of
> DataStream.
> > For loading, #loadDefinitions
>
> No. that is the point.
> you add a loderFuel to the class side of MCMc{d,z}Reader that
> returns an association of priority -> oneargblock.
>
> My proposal is about experimenting with the MC stuff _without_ changing
> the present logic, but augmenting them.
>
> See the FuelMonticello-topa.1.mcz for an example.
> (note that this mcz already contains a snapshot.fuel ;) )
>
>
Yes, yes, yes, I saw that :)
I just wanted to point to Stef where MC was doing such magic. I know you
didn't modify that directly with instead add different loaders. I saw your
code :)
> best
> -Tobias
>
>
>
>
--
Mariano
http://marianopeck.wordpress.com
Re: [Pharo-project] Monticello enhancing
Am 2011-12-03 um 15:52 schrieb Mariano Martinez Peck:
>
>
> On Sat, Dec 3, 2011 at 3:46 PM, Tobias Pape wrote:
>
> Am 2011-12-03 um 14:34 schrieb Mariano Martinez Peck:
>
> >
> >
> >> On Sat, Dec 3, 2011 at 12:23 AM, Stéphane Ducasse
> >> wrote:
> >> Thanks tobias
> >> This is cool to have that!
> >> With your experiment are loading MC definitions using fuel?
> >>
> > yes, loading and writing. Basically, for writing, for example, it is to
> > change #writeSnapshot: or #serializeInBinary: to use Fuel instead of
> > DataStream.
> > For loading, #loadDefinitions
>
> No. that is the point.
> you add a loderFuel to the class side of MCMc{d,z}Reader that
> returns an association of priority -> oneargblock.
>
> My proposal is about experimenting with the MC stuff _without_ changing
> the present logic, but augmenting them.
>
> See the FuelMonticello-topa.1.mcz for an example.
> (note that this mcz already contains a snapshot.fuel ;) )
>
>
> Yes, yes, yes, I saw that :)
> I just wanted to point to Stef where MC was doing such magic. I know you
> didn't modify that directly with instead add different loaders. I saw your
> code :)
Ah, ok. nevermind.
Best
-Tobias
