<div dir="ltr"><div>That's a generous offer and hopefully someone will be attending to take you up on it.[1] In the meantime, a quick search returns what appears to be at least a partial summary of FileTree vs Tonel: <a href="https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/ExportFormats.md">https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/ExportFormats.md</a></div><div><br></div><div>[1] While it would help ensure a better understanding of how things developed, I'm not sure it would actually change anything. There has been difference of opinion between the Cuis and Squeak/Pharo communities pretty much since day 1 on the subject of package formats, among other things. My take is that the lack of convergence on a common solution is due to fundamental philosophical, rather than technical, differences.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 31, 2019 at 2:50 PM Dale Henrichs via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>I've been following this particular issue and would prefer not to
get into an email-based discussion of why tonel/filetree came to
be and their relative disadvantages and advantages ...</p>
<p>However, I will be at ESUG in Cologne and would love to have a
discussion (at a whiteboard) with one or more members of the Cuis
community to talk things over and see if there is any common
ground to be found ...</p>
<p>Dale<br>
</p>
<div class="gmail-m_1026786084093384829moz-cite-prefix">On 7/31/19 10:18 AM, Phil B via
Cuis-dev wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">On Wed, Jul 31, 2019 at 9:54 AM Juan Vuletich via
Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st" target="_blank">cuis-dev@lists.cuis.st</a>> wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">pufff.<br>
<br>
I don't want to even think of how github package diff would
look like.<br>
<br>
At least they could use <a href="http://xxx.filetree.st" rel="noreferrer" target="_blank">xxx.filetree.st</a>
and <a href="http://xxx.tonel.st" rel="noreferrer" target="_blank">xxx.tonel.st</a>
(like we use <br>
<a href="http://xxx.pck.st" rel="noreferrer" target="_blank">xxx.pck.st</a> and <a href="http://xxx.cs.st" rel="noreferrer" target="_blank">xxx.cs.st</a>). Now it is
impossible for tools to tell <br>
whether they are dealing wiht filetree, tonel, or some other
smalltalk <br>
format...<br>
<br>
</blockquote>
<div><br>
</div>
<div>They use .properties files to convey that information.
Actually I think the entire point of these 'exploded'
package formats was to make raw method-level diffs pretty...
at the cost of making the overall package format quite
ugly/cumbersome. Every time I've had to look at a repo
using those formats, I'm happy you went the direction you
did with package files. You prioritized the people using
the package files, they continue to prioritize the tools
that manipulate them.</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
</blockquote>
</div>
</div>
<br>
<fieldset class="gmail-m_1026786084093384829mimeAttachmentHeader"></fieldset>
</blockquote>
</div>
-- <br>
Cuis-dev mailing list<br>
<a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a><br>
<a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br>
</blockquote></div>