On Thu, May 6, 2010 at 5:43 PM, Mike Kienenberger mkien...@gmail.com
wrote:
Sounds a lot like the tomahawk sandbox subform and tomahawk UICommand
components. You can specify an actionFor attribute on the UICommand
components to point at a specific subform.
I wonder if some of the design
Hi,
Thanks for the replies.
But also you might get it easier (second option),
maybe you wont even need a second lifecycle if you can tackle the
problem via JSF2 system events on the controls themselves.
Sounds good :)
I would recommend also to raise a spec issue there
2 Possibilities:
First, via custom lifecycle, extend the standard elements in a way that
they refer to a form element and a first step collect those elements and
a second step at, form processing, processes those external elements
within the bounds of a form.
This applies to the apply request
On Thu, May 6, 2010 at 4:19 AM, Werner Punz werner.p...@gmail.com wrote:
2 Possibilities:
First, via custom lifecycle, extend the standard elements in a way that
they refer to a form element and a first step collect those elements and a
second step at, form processing, processes those
Yes they will definitely need that attribute especially if they are
outside of a form. Also the components have to throw an error if the
attribute is not set and if they are not hosted inside of a form.
Werner
Am 06.05.10 16:25, schrieb Kito Mann:
On Thu, May 6, 2010 at 4:19 AM, Werner
Sounds a lot like the tomahawk sandbox subform and tomahawk UICommand
components. You can specify an actionFor attribute on the UICommand
components to point at a specific subform.
I wonder if some of the design from subform can be reused.
On Thu, May 6, 2010 at 10:39 AM, Werner Punz
Hi all,
I've been working on my GSOC project (prototyping currently). I want to ask
you something.
With HTML5, form elements does not have to be children of a form. Of course,
that is the preferred way, but you can set the form attribute of the
input and that input will be posted when the owner
