<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, From my understanding and experience with Pharo: - FileTree : one file per method (abandoned? Two many files, problem for limited system as Windows) - Tonel: one file per class. But I am not paying attention since two years. Hilaire <div class="moz-cite-prefix">Le 01/05/2022 à 01:16, ken.dickey--- via Cuis-dev a écrit : </div> <blockquote type="cite" cite="mid:794d62c6ee60e306294edc377e667bbf@whidbey.com">Gak! Er, no. Pharo splits files not at class-per-file, but Method-per-file, and uses separate files for class comment, and package manifests, and ... and ... Also, Cuis does not have Traits, so no STON support for Traits. However, I am happy if you take what I did as a starting point and add the busy bits to deal with the superfluous explosion of files which Pharo uses. I am basically interested in code in <a class="moz-txt-link-freetext" href="https://github.com/powerlang/bee-dmr" moz-do-not-send="true">https://github.com/powerlang/bee-dmr</a> which is class-per-file Compare the Pharo Tonel files <a class="moz-txt-link-freetext" href="https://github.com/pharo-vcs/tonel" moz-do-not-send="true">https://github.com/pharo-vcs/tonel</a> with the much smaller file set in <a class="moz-txt-link-freetext" href="https://github.com/aucerna/bee-dmr/tree/master/Tonel" moz-do-not-send="true">https://github.com/aucerna/bee-dmr/tree/master/Tonel</a> which is where I started from. It is good that Smalltalk supplies a number of iterators, because Pharo source really tests the fine granularity of a file system. IMHO, </blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a class="moz-txt-link-freetext" href="http://blog.drgeo.eu">http://blog.drgeo.eu</a></pre> </body> </html>