Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of mwessendorf@gmail.com
 designates 74.125.82.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=YO4ApOEqk2LTXRYF/oQYlAmjKGVi6joKEIx8nfiWKDsjvstQkSXIdFty1IMeN125BP
         eQXfXyAHHythq6octwPM56zV0T+r1cAz1y6bc2EzekNyz8lKXEd20VRmApOtqA1eyJVL
         NQGWDBGCpahPHq/7QSy4VUP3VCnCI0Q1vntjk=
MIME-Version: 1.0
Sender: mwessendorf@gmail.com
In-Reply-To: <g2q8f985b961005060843u4024bc01u4375af87fb3e9e77@mail.gmail.com>
References: <h2sd8ad8d051005051101q81077b12ia41d1122a59ef655@mail.gmail.com>
	 <hrtu2l$5ts$1@dough.gmane.org>
	 <n2oc5b496b1005060725n77bce60v6236481d599c1059@mail.gmail.com>
	 <hrukbs$sba$1@dough.gmane.org>
	 <g2q8f985b961005060843u4024bc01u4375af87fb3e9e77@mail.gmail.com>
Date: Mon, 10 May 2010 10:47:36 +0200
Message-ID: <AANLkTinb-glmTMwdH4TO7JuCIgvdvui9h_-2Mebo_dle@mail.gmail.com>
Subject: Re: [GSOC] New Form Elements
From: Matthias Wessendorf <matzew@apache.org>
To: MyFaces Development <dev@myfaces.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1

On Thu, May 6, 2010 at 5:43 PM, Mike Kienenberger <mkienenb@gmail.com> wrot=
e:
> Sounds a lot like the tomahawk sandbox subform and tomahawk UICommand
> components. =A0You 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 <werner.punz@gmail.com> wrot=
e:
>> Yes they will definitely need that attribute especially if they are outs=
ide
>> of a form. Also the components have to throw an error if the attribute i=
s
>> 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 Punz <werner.punz@gmail.com
>>> <mailto:werner.punz@gmail.com>> wrote:
>>>
>>> =A0 =A02 Possibilities:
>>> =A0 =A0First, via custom lifecycle, extend the standard elements in a w=
ay
>>> =A0 =A0that they refer to a form element and a first step collect those
>>> =A0 =A0elements and a second step at, form processing, processes those
>>> =A0 =A0external elements within the bounds of a form.
>>> =A0 =A0This applies to the apply request values and validation phases, =
or
>>> =A0 =A0probably.
>>>
>>> =A0 =A0Second possibility:
>>>
>>> =A0 =A0But also you might get it easier (second option),
>>> =A0 =A0maybe you wont even need a second lifecycle if you can tackle th=
e
>>> =A0 =A0problem via JSF2 system events on the controls themselves.
>>> =A0 =A0(you can set direct event listeners for various phases on the co=
ntrols
>>> =A0 =A0so that they will be processed), this would be even faster since=
 the
>>> =A0 =A0event handling mechanisms would do the bookkeeping for you which=
 you
>>> =A0 =A0in the other case would have to do yourself.
>>>
>>>
>>> Using component system events should work fine -- it's how
>>> <h:outputScript> and <h:outputStylesheet> can retarget themselves to th=
e
>>> <h:head> component. I think the components may need a new "forForm"
>>> attribute, though, for cases when there's more than one form on the pag=
e.
>>>
>>>
>>> =A0 =A0This is probably the biggest problem with JSF and HTML5 (I did n=
ot
>>> =A0 =A0know this was possible, since I only follow the html 5 developme=
nt
>>> =A0 =A0via blogs and articles), I would recommend also to raise a spec
>>> =A0 =A0issue there regarding this, so that we might, special handling f=
or
>>> =A0 =A0the official spec so that no impl has to cook its own mechnanism=
 in
>>> =A0 =A0the long run.
>>>
>>> =A0 =A0https://javaserverfaces-spec-public.dev.java.net/servlets/Projec=
tIssues
>>>
>>>
>>> =A0 =A0Werner
>>>
>>>
>>>
>>> =A0 =A0Am 05.05.10 20:01, schrieb Ali Ok:
>>>
>>> =A0 =A0 =A0 =A0Hi all,
>>> =A0 =A0 =A0 =A0I've been working on my GSOC project (prototyping curren=
tly). I
>>> =A0 =A0 =A0 =A0want to
>>> =A0 =A0 =A0 =A0ask you something.
>>>
>>> =A0 =A0 =A0 =A0With HTML5, form elements does not have to be children o=
f a form.
>>> Of
>>> =A0 =A0 =A0 =A0course, that is the preferred way, but you can set the "=
form"
>>> =A0 =A0 =A0 =A0attribute
>>> =A0 =A0 =A0 =A0of the <input> and that <input> will be posted when the =
owner
>>> =A0 =A0 =A0 =A0form is
>>> =A0 =A0 =A0 =A0submitted.[0]
>>> =A0 =A0 =A0 =A0This also applies to submit buttons, in a similar way. Y=
ou can
>>> =A0 =A0 =A0 =A0define
>>> =A0 =A0 =A0 =A0"form" attribute of the submit button, and it will submi=
t the
>>> =A0 =A0 =A0 =A0defined
>>> =A0 =A0 =A0 =A0form -not necessarily its parent- when it is clicked.[1]
>>>
>>> =A0 =A0 =A0 =A0So, I wonder if this can be applied in JSF side. AFAIK c=
urrently, a
>>> =A0 =A0 =A0 =A0commandButton needs to be under a <h:form>.
>>> =A0 =A0 =A0 =A0This is also about serverside component tree, and maybe =
state
>>> =A0 =A0 =A0 =A0saving.
>>>
>>> =A0 =A0 =A0 =A0I couldn't set up much in my head.
>>>
>>> =A0 =A0 =A0 =A0What do you think? How can we use this new features? How=
 to
>>> =A0 =A0 =A0 =A0model them?
>>>
>>> =A0 =A0 =A0 =A0Thanks,
>>> =A0 =A0 =A0 =A0Ali
>>>
>>> =A0 =A0 =A0 =A0[0]
>>>
>>> =A0http://www.whatwg.org/specs/web-apps/current-work/multipage/associat=
ion-of-controls-and-forms.html#attr-fae-form
>>> =A0 =A0 =A0 =A0[1]
>>>
>>> =A0http://www.whatwg.org/specs/web-apps/current-work/multipage/number-s=
tate.html#submit-button-state
>>>
>>> =A0<http://www.whatwg.org/specs/web-apps/current-work/multipage/number-=
state.html#submit-button-state>
>>>
>>> =A0 =A0 =A0 =A0--
>>> =A0 =A0 =A0 =A0My Blog: http://blog.aliok.com.tr
>>> =A0 =A0 =A0 =A0Twitter: http://twitter.com/aliok_tr
>>>
>>>
>>>
>>>
>>
>>
>>
>


--=20
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf