Re: [Formsess-devel] setting formsess options

[David <da...@df...>]

> 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.

Would that be compatible to the smarty approach I suggest?
It's just that to 'learn formsess' itself is not an easy task, and since
the users already know smarty.. 

> 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 ?

I'm not sure. What about providing accepting the classname as an
optional parameter to enableFormsess()? (which would set a constant
internally)