Re: form and select component

2012-10-26 Thread Geoff Callender
g statement out of it > > oh well...onward > > I am historically an DECWindows XWindows buff... babied by the MIT boys back > in the day... but this is endless challenging fun > > From: nhhockeypla...@hotmail.com > To: users@tapestry.apache.org > Subject: RE: form

RE: form and select component

2012-10-26 Thread nhhockeyplayer nashua
t oh well...onward I am historically an DECWindows XWindows buff... babied by the MIT boys back in the day... but this is endless challenging fun From: nhhockeypla...@hotmail.com To: users@tapestry.apache.org Subject: RE: form and select component Date: Fri, 26 Oct 2012 09:04:19 -0400 Ok, I a

Re: form and select component

2012-10-26 Thread Thiago H de Paula Figueiredo
On Fri, 26 Oct 2012 11:04:19 -0200, nhhockeyplayer nashua wrote: Ok, I am stubborn.. because it worked fine in T4 without the form. T5 is not T4. T5 is a complete rewrite, not sharing any code with T4, so don't expect stuff to work in the same way. But it is housed within a form... from

RE: form and select component

2012-10-26 Thread nhhockeyplayer nashua
ok I will get out the firebug and see what gives inside the dom Best regards and thanks... KEN From: nhhockeypla...@hotmail.com To: users@tapestry.apache.org Subject: RE: form and select component Date: Fri, 26 Oct 2012 00:37:24 -0400 this one doesnt invoke the handler either but I change

Re: form and select component

2012-10-26 Thread Thiago H de Paula Figueiredo
Why isnt this sufficient? It refuses to invoker the event handler. I've already told you that it won't work and why, in this same thread why, so I don't think I need to repeat it here. -- Thiago H. de Paula Figueiredo - To

Re: form and select component

2012-10-26 Thread Peter Wendorff
Am 26.10.2012 02:32, schrieb nhhockeyplayer nashua: Folks, Do I really NEED to have a form with my components ? I know its unorthadox... but I would like to skip the form if possible to keep this lightweight and just use onchange="this.form.submit()" when it gets selected. For that concrete

RE: form and select component

2012-10-25 Thread nhhockeyplayer nashua
this one doesnt invoke the handler either but I changed handkler to the following @Component(id="itemsPerPageSelect", parameters = { "value=itemsPerPage", "clientId=itemsPerPageSelect" }) private Select itemsPerPageSelect; @OnEvent(value = EventConstants.VALUE_CHANGED, compon

RE: form and select component

2012-10-25 Thread nhhockeyplayer nashua
as you can tell I like to keep things petite and simple onchange="Event.fire(this,'change');" ? From: nhhockeypla...@hotmail.com To: users@tapestry.apache.org Subject: RE: form and select component Date: Thu, 25 Oct 2012 23:49:20 -0400 @Component(id

RE: form and select component

2012-10-25 Thread nhhockeyplayer nashua
@Component(id="itemsPerPageSelect", parameters = { "value=itemsPerPage", "clientId=itemsPerPageSelect" }) private Select itemsPerPageSelect; @OnEvent(value = EventConstants.VALUE_CHANGED, component = "itemsPerPageSelect") public Object onValueChangedItemsPerPageSelect(

Re: form and select component

2012-10-25 Thread Thiago H de Paula Figueiredo
On Thu, 25 Oct 2012 22:32:42 -0200, nhhockeyplayer nashua wrote: Folks, Hi! Do I really NEED to have a form with my components ? Short answer: yes. Long answer: ys. :P The Form component is the one who actually invokes the form field components logic that hand