On 26 juil. 06, at 03:42, Masashi UMEZAWA wrote:

> Hi,
>
> I'm now upgrading SIXX. The new version has new hooks for customizing
> serialization more easily. So I recommend using the latest version
> here:
> http://squeaksource.blueplane.jp/SIXX/
>
> Basically, SIXX writes the whole object structures in one file. It is
> simple, but causes a performance problem if the data becomes
> relatively big.

Is there a way to specify which instance variables we can save?
Do you have a kind of metadescription?
I always thought that Magritte would be a good basis for that.


>
> To avoid it, you would need to split the structures in small files. I
> recently developed FileMan library, which enables you to manage
> multiple files easily.
>
> FileMan:
> http://map1.squeakfoundation.org/package/f9917683-25da-4a6c-a013- 
> b36527a100c1
>
> Actually. I'm developing a Wiki that stores pages in SIXX with
> FileMan. If it is released, it would be a good example of using SIXX
> in application.
>
> Cheers,
>
> 2006/7/25, florent trolat <trolat.florent at laposte.net>:
>> Hi,
>>
>> 1/
>> I'm playing with SIXX and I call upon your memory about troubles  
>> with it.
>> I've already seen some troubles in mailing list archives...
>>
>> 2/
>> Have you big (critic) applications using sixx?
>>
>>
>> 3/
>> The SiXX description says:
>> > Advanced users can implement custom serialization/deserialization
>> > format by overriding only a few hook methods
>> Maybe someone have tried to do something like this?
>>
>> Thanks
>>
>> FLO
>>
> -- 
> [:masashi | ^umezawa]
>