[Cuis-dev] Converting Tonel packages
juan at jvuletich.org
Wed Jul 31 06:30:49 PDT 2019
On 7/29/2019 3:16 PM, Philip Bernhart wrote:
> Hi Juan,
> Juan Vuletich<juan at jvuletich.org> writes:
>> Aren't those also based on the old Smalltalk-80 chunk format, like .cs
>> files? Cuis already handles changeset files. So, it could be a matter of
>> writing a Smalltalk script to load them, right?
> well as far as I can tell: no, they aren't.
> 1. Filetree splits up an export into package directories,
> then class directories, then subdirs of them with the instance
> and class sides and then creates for each method a .st file.
> Also it stores a bunch of properties for classes, packages, methods
> in STON (Smalltalk Object Notation) format.
> 2. Tonel is like filetree but less deeply nested. It stores classes
> per file. Each file in turn is not chunk based anymore, but has
> the tonel format. Which are methods serialized and have additionally
> a STON prefix infront of them.
> For comparison:
> 1. https://github.com/pharo-vcs/test-project-source-properties-filetree
> 2. https://github.com/pharo-vcs/test-project-source-properties-tonel
> So for reading them in, you would need to be able to parse them.
> I don't see the improvement over good old chunk files.
> Thanks for your time,
I don't want to even think of how github package diff would look like.
At least they could use xxx.filetree.st and xxx.tonel.st (like we use
xxx.pck.st and xxx.cs.st). Now it is impossible for tools to tell
whether they are dealing wiht filetree, tonel, or some other smalltalk
More information about the Cuis-dev