...and developers can substitute their own protocol compatible classes and extend the settings being managed and/or customize the behavior upon certain triggers ... with the added benefit of being editable outside of an image ... .... been doing this for awhile in tODE:) Dale On 10/15/15 7:26 AM, Juraj Kubelka wrote:
And there are more values that has to be treated differently, e.g. fonts, file paths, theme.
Cheers, Juraj
On Oct 15, 2015, at 08:32, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
First of all you can add additional data like a version of the project for which the setting should work.
Secondly it depends how much do we want to stress the developers. Because you cannot serialize classes in STON. So either we store âStoredSettingâ and âStoredClassSettingâ where the second one knows that is has to convert a value to a class, or we force developers to do that. I late the second one moreâ¦
Uko
On 15 Oct 2015, at 13:09, Damien Cassou <damien.cassou@inria.fr> wrote:
Yuriy Tymchuk <yuriy.tymchuk@me.com> writes:
It is like that:
[ StoredSetting { #settingNodeIdentifier : '#shoreLine#autoSubmit', #realValue : true }, StoredSetting { #settingNodeIdentifier : '#reIgnore', #realValue : Set [ ] } ] why not:
{ '#shoreLine#autoSubmit' : true, '#reIgnore' : Set [ ] }
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill