Just a note that may be of interest.<div><br></div><div>I moved off Git and into Fossil. Check it out, it may actually be easier for us to work with since everything lives in a single Sqlite database. No more files everywhere. The author of Fossil is the author of Sqlite.</div>

<div><br></div><div>The whole Tcl/Tk source moved into that as well.</div><div><br></div><div>For me it looks like coherent with the Smalltalk idea of an image and metadata access that is easy. Not really easy to do with a bunch of files.</div>

<div><br></div><div>And the commands are pretty much compatible.</div><div><br></div><div>As an added benefit, you get a free issue tracker and wiki built in to document all of the package.</div><div><br></div><div>Phil<br>

<br><div class="gmail_quote">2012/10/1 Dale Henrichs <span dir="ltr">&lt;<a href="mailto:dhenrich@vmware.com" target="_blank">dhenrich@vmware.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Stef,<br>
<br>
I forgot to share with you that at this last ESUG we (Jan Vrany, Martin Kobetic and myself) agreed that the next version of Filetree will use .ston files instead of .json files. I am planning on writing a blog post on this...eventually.<br>


<br>
The Smalltalk/X implementation (Jan Vrany) is using .ston files and version 2.0 of FileTree will using .ston files and I will be working on version 2.0 soon. �Jan is planning on using Metacello with Smaltalk/X so I&#39;ll need to implement version 2.0 of FileTree to share code with him...<br>


<br>
.json files are on the way out!<br>
<br>
Dale<br>
----- Original Message -----<br>
| From: &quot;St�phane Ducasse&quot; &lt;<a href="mailto:stephane.ducasse@inria.fr">stephane.ducasse@inria.fr</a>&gt;<br>
| To: &quot;<a href="mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@lists.gforge.inria.fr</a> Development&quot; &lt;<a href="mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@lists.gforge.inria.fr</a>&gt;<br>


| Sent: Monday, October 1, 2012 10:00:47 AM<br>
| Subject: [Pharo-project] [Another sad day] a nice example of the mess with � �json in FileTree<br>
|<br>
| Hi guys<br>
|<br>
| I was browsing (at least trying) to have a look at mist<br>
| � � � <a href="https://github.com/martinmcclure/mist/commit/b3103bd30be11dd8063aa9ce212a368c66f73e9a" target="_blank">https://github.com/martinmcclure/mist/commit/b3103bd30be11dd8063aa9ce212a368c66f73e9a</a><br>
|<br>
| and this is so nice to see json code in the middle of Smalltalk<br>
| methods. Look for class definitions there are<br>
| great. Yes it will help newcomers to jump into Smalltalk. So great.<br>
| We avoided the XML crap as in VW but apparently we will not avoid the<br>
| shit of JSON.<br>
|<br>
| May be this is the clear indication that we should all stop to code<br>
| in Smalltalk (a dead language anyway) and all switch to Javascript<br>
| in a plain happiness. Have a look this is great to read class<br>
| definitions and method categories like that. I love FileTree. I love<br>
| JSON.<br>
|<br>
| What is terribly fun is that JSON could be good if we would not have<br>
| a declarative syntax for exactly the same but<br>
| new is always better. So long life to FileTree and JSON.<br>
|<br>
| Stef<br>
| PS: Of course you can all piss on me, do it if this helps you.<br>
| Now tell me that I do not have to use GitHub to browse code and all<br>
| kind of nice arguments�<br>
| while at the same time, people are telling me the inverse.<br>
|<br>
| Yes I can stick with my old crappy browser and we will explain to our<br>
| students that we were not able to use<br>
| the syntax of our language to express nicely the same.<br>
|<br>
| PSPS: so do not ask me any help and support for such idea.<br>
|<br>
<br>
</blockquote></div><br></div>