On 28 Jun 2020, at 18:22, Russ Whaley <[hidden email]> wrote:

Stephane,

Thanks for the info on chrysal.  I'm going to like going through the code to see how you solved some things.  I created my own Configuration class that operates with a dictionary of keys the applications expect to use, and configuration values (paths, numerics, dates, strings...) but not blocks!... and save to and read from a STON file when a 'configs' instvar is referenced in the application.  So far the only limitation I've come into is saving blocks, but admittedly I'm building it out as I need it.

Looking forward to reviewing chrysal!

Thanks,

Russ

On Sun, Jun 28, 2020 at 6:25 AM Stéphane Ducasse <[hidden email]> wrote:

Hi russ,

I do not if you know but based on Ston I built chrysal

to manage applications configuration:

https://github.com/ducasse/chrysal

The basic idea is that you describe the possible fields of your configuration (i.e. how user can edit JSON files) and 

it generates a converter from STON to your pharo objects.

You ship just the converter and its textual description so that you understand what you did. 

But this is probably not what you need but more a textual serializer.  

S. 

On 27 Jun 2020, at 16:07, Russ Whaley <[hidden email]> wrote:

Good morning all from stormy Ohio/USA.  Hope everyone is well and sheltering effectively from COVID, etc.

I have a STON question.  FIrst off, I LOVE STON.  It has been the answer to my (minimal) persistence needs.  I'm writing two different applications, both of which I hope to distribute someday, and I struggled with what would work to save configurations, templates, status, etc.  STON was the answer for me - it's very easy to install and simple to use.

But as I add the next feature/function in my code - sort blocks - as soon as I tried to save them (a collection of them in an instvar)... I get an error on the writeToSTON, and the target file is now corrupt - at the point where it tried to write the blocks.  I have looked in the documentation and it plainly states the version I'm using does not yet address blocks - but I was hoping someone out there has developed a workaround, or perhaps has STON been updated to handle blocks?

I could make the jump to a more sophisticated storage mechanism (i.e. Fuel?), but I'd rather spend my time working on features and figuring out the Spec2 GUI. :)

Any advice is welcome and appreciated.

Thanks!

Russ 

--

Russ Whaley
[hidden email]

--------------------------------------------

Stéphane Ducasse

http://stephane.ducasse.free.fr / http://www.pharo.org 

03 59 35 87 52

Assistant: Aurore Dalle 

FAX 03 59 57 78 50

TEL 03 59 35 86 16

S. Ducasse - Inria

40, avenue Halley, 

Parc Scientifique de la Haute Borne, Bât.A, Park Plaza

Villeneuve d'Ascq 59650

France

--

Russ Whaley
[hidden email]