Due to its source code management (ENVY) each application has its own configuration section in a simple ascii based *.ini file. Therefore each
application has a text section like
[name of application] key = value ...The developer just write 3 methods on the class side of its application class, which more or less do something:
one method defines all possible entries expected in the text files and what type it has
one method defines current AND default values for each setting one method defines how to transfer the values to your application.That's pretty simple - but also limited - and you copy the implementation of these three methods from another application, change them according to your needs and that's it.
The documentation describing the Pharo settings framework is 20 pages long and offers many more features - I actually do not need. And I do not need a GUI to edit my setting values - but for others this might be useful. The documentation is not straight forward - three or four pages with introductions. And even now I do not know how the settings are stored outside the system.
But as I said before - I have not done much work with Squeak/Pharo yet - and this only reflects my early impressions when working with this system. And I even do not know, if Settings is part of Pharo 1.4 or Pharo 2.0. Just to give you an overview of my ideas here.
and another point I want to say about using the system:Working with VASmalltalk/ENVY the methods called after starting, resuming, loading, unloading (and various other events) to each class/application are well documented. I do not find documents/informations about this in Pharo/Squeak and this is a very important information when initializing an application.
Marten Feldtmann Am 06.09.2012 17:30, schrieb Sean P. DeNigris:
* Settings – I find this one *really* interesting. Will you highlight the key differences to VA? Maybe we can improve the framework in Pharo, or at minimum create a UI that makes things simpler and more straightforward for you
<<attachment: marten.vcf>>
