Tim's original question is something that I ask myself from time to time. Having some "obvious" options for simple prototyping of ideas on Pharo would be a good tool for infiltrating Pharo in our workplaces and starting the slow adoption process. The Django web framework is a good example. The framework as a whole is quite complete, mature and professional, but it's adoption usually started with the auto-generated "admin" interface, an ill-suited tool for anything more serious.

On Fri, Oct 9, 2020 at 12:53 PM Offray Vladimir Luna C��rdenas <offray.luna@mutabit.com> wrote:

Tim,

As I showed in my example Grafoscopio notebook in this thread, STON is a
pretty well suited format for complex documents or simple objects and
DVCS (Fossil / Git) friendly. Besides, the pretty print option make it
really readable, even outside Pharo (see the referred notebook for
example). Using Fossil repositories + STON as a future proof format for
reproducible, agile data storytelling is one of those combinations that,
could no be exactly what you're looking for, but maybe useful to have on
the radar and put in your preliminary explorations. I'm pretty happy
with it.

Cheers,

Offray

On 9/10/20 6:07 a.��m., Sven Van Caekenberghe wrote:
>
>> On 9 Oct 2020, at 12:13, Sean P. DeNigris <sean@clipperadams.com> wrote:
>>
>> Tim Mackinnon wrote
>>> Thanks, I had completely forgotten about STON, thats a good point too
>>> (possibly this is what SimplePersistence uses as well - I'm not sure).
>> It currently uses Fuel, but the serializer/materializer is abstracted, so
>> STON could probably be plugged in easily
> As a textual format, STON has the advantage that you can read/edit the file (especially if you pretty print it).
>
> Wrapping a ZnBuffered[Read|Write]Stream around your text/character stream before handing it to STON improves speed.
>
>> -----
>> Cheers,
>> Sean
>> --
>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html