On Mon, 15 Dec 2008, Kevin Waterson wrote:
> This one time, at band camp, Alexandru Stanoi wrote:
>
> > Is it a good idea to depend on another component? (UserInput in this case).
>
> I was thinking on this, and the options seem to be to 'repurpose' UserInput
> or to re-invent it again in ezcFor
On Mon, 15 Dec 2008, Alexandru Stanoi wrote:
> How about CSS for the form? Also it should support different "renderers"
> (HTML, templates, maybe smartphone forms?).
I would agree, rending should be done through multiple renders.
regards,
Derick
--
Components mailing list
Components@lists.ez.n
On Mon, 15 Dec 2008, Kevin Waterson wrote:
> My proposal is for an ezcForm component.
> The ezcForm component would provide an interface to the creation
> of HTML form objects which may be rendered for use with templates.
>
> Each form element would be an object which whose properties would
> def
This one time, at band camp, Alexandru Stanoi wrote:
> How about CSS for the form? Also it should support different "renderers"
> (HTML, templates, maybe smartphone forms?).
These are all up for grabs, I expect there will be several possiblities
in choice of renderers.
>
> How is state being
Kevin Waterson wrote:
> My proposal is for an ezcForm component.
> The ezcForm component would provide an interface to the creation
> of HTML form objects which may be rendered for use with templates.
Does it need to depend on the Template component?
> Each form element would be an object which w
My proposal is for an ezcForm component.
The ezcForm component would provide an interface to the creation
of HTML form objects which may be rendered for use with templates.
Each form element would be an object which whose properties would
define how the form would be rendered.
eg:
setMethod('post
