Re: [Formsess-devel] setting formsess options

[<ka...@ka...>]

> I added (g|s)etOption time ago to set formsess options. However they
> became important only recently when some more options were added.
> (before you could only toggle the js validation).
>
> Calling setOption several times after instanciating the formsess
> class sucks so we need a way to easily set side-wide preferences.
>
> Bertrand, you wanted to add that additional configuration class, nothing
> happend with that however. ;)
>
> I suggest to make all options properties of the formsess class, they way
> it's with smarty. You could easily define your own class extending
> formsess only with different properties set.
> (just the way we do it with smarty)
>
> This is simple, powerful and (which is most important imho) familar to
> smarty users.
>
> What do you think?
I think it is OK, and it is almost what I had in mind. However, I will
write _ sooner or later _ that FormsessController class so that
application wide options might be set without having to set them everytime
you create an instance.
But how do you think these options will be set when no instance of the
class is created, e.g. when you only use <fs:form> in the template ?

Katana