RE: bidirectional dom interface

2008-01-22 Thread Ken in nashua
This was the issue with refresh. https://issues.apache.org/jira/browse/TAPESTRY-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561377#action_12561377Best regards Ken in nashua From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: bidirectional dom interfac

Re: bidirectional dom interface

2008-01-18 Thread DR_GLoPeL_BouCa
- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/bidirectional-dom-interface-tp14881716p14955237.html Se

Re: bidirectional dom interface

2008-01-18 Thread Kevin Menard
Is customerTable a Tapestry component or is it an ID you just attached to some element? -- Kevin On 1/17/08 10:12 AM, in article [EMAIL PROTECTED], "DR_GLoPeL_BouCa" <[EMAIL PROTECTED]> wrote: > > Hello people, I've the similar problem, the browser not display the response > of ajax submit, I

Re: bidirectional dom interface

2008-01-18 Thread DR_GLoPeL_BouCa
Components="customerTable", without the ognl: prefix. > > Thiago > > ok, try but don't work, try updateComponents="ognl:customerTable" or updateComponents="customerTable" or updateComponents="ognl:{'customerTable'} and nothing

Re: bidirectional dom interface

2008-01-17 Thread Thiago HP
On Jan 17, 2008 12:12 PM, DR_GLoPeL_BouCa <[EMAIL PROTECTED]> wrote: > > Hello people, I've the similar problem, the browser not display the > response > of ajax submit, I've form with submit async="true" and > updateComponents="ognl:customerTable", when the ajax response come browser > don't disp

RE: bidirectional dom interface

2008-01-17 Thread DR_GLoPeL_BouCa
inspect de response and is in there, what's wrong.. Sorry mi english, Thaws. -- View this message in context: http://www.nabble.com/bidirectional-dom-interface-tp14881716p14921167.html Sent from the Tapestry - User mailing list archive at Nabble.com.

RE: bidirectional dom interface

2008-01-16 Thread Pai911
ight. > > ?Best regards Ken in nashua > -- View this message in context: http://www.nabble.com/bidirectional-dom-interface-tp14881716p14912382.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: bidirectional dom interface

2008-01-16 Thread Ken in nashua
Well the fact that one definition refers to the same ognl instance being "ognl:components.autoPagingContent" commonsense tells me I shouldn't even should be mucking with this... it should update automatically. The fact that this component's PropertySelect doesn't even survive a page

Re: bidirectional dom interface

2008-01-16 Thread Kevin Menard
I could be mistaken, but I think if you have the component in a loop, then updateComponent("baseIdName") will apply to all of those components in the loop . . . I.e., you don't have to specify each individual instance. If you're running into issues with grouping though, you could surround the the

RE: bidirectional dom interface

2008-01-16 Thread Ken in nashua
more feedback... I tried this explicitly getResponseBuilder().updateComponent("tableSizeSelect_0"); and it did not update the select dom with the expected value that lives in the other select dom getResponseBuilder().updateComponent("tableSizeSelect"); Best regards Ken in nashua From: [E

RE: bidirectional dom interface

2008-01-16 Thread Ken in nashua
Ok, I fixed the ID issue... But... it don't work. What don't Work? more than one DOM referencing one instance of a tapestry component/widget... namely a PropertySelect. Here is the proof. I did view-source fro the browser to look at the markup. markup... ... Now will HTML crap out if

RE: bidirectional dom interface

2008-01-16 Thread Ken in nashua
Well it's probably because the ID has changed now to id="[EMAIL PROTECTED]" OK, so I should use jwcid.Best regards Ken in nashua From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: bidirectional dom interfaceDate: Wed, 16 Jan 2008 10:44:32 -0500 Well I tried this in the page that contains t

Re: bidirectional dom interface

2008-01-16 Thread Kevin Menard
Pai is correct. UpdateComponent() must be passed a component ID. An arbitrary ID does not work. -- Kevin On 1/16/08 12:40 PM, in article [EMAIL PROTECTED], "Pai911" <[EMAIL PROTECTED]> wrote: > > Hi! > Maybe you should make the division you want to update Tapestry components? > > > >

RE: bidirectional dom interface

2008-01-16 Thread Ken in nashua
PAI, I tried your suggestion on the ANY component. My Gallery.script is being impacted now. I cannot do the following: // just paste a Loading text at bottom of table // this worked previously to your suggestion var divBlock = document.createElement("div"); divBlock.appendChild(document.

RE: bidirectional dom interface

2008-01-16 Thread Pai911
in > nashua > > Get the power of Windows + Web with the new Windows Live. Get it now! > _ > Make distant family not so distant with Windows Vista® + Windows Live™. > http://www.microsoft.com/windows/digitallife/keepintouch.

Re: bidirectional dom interface

2008-01-16 Thread Igor Drobiazko
getResponseBuilder().updateComponent is the way to update parts of your view. Check if your html is correct. On Jan 16, 2008 4:44 PM, Ken in nashua <[EMAIL PROTECTED]> wrote: > > Well I tried this in the page that contains the component... > > public void refresh() > { > getResponseBuilder().upda

RE: bidirectional dom interface

2008-01-16 Thread Ken in nashua
Well I tried this in the page that contains the component... public void refresh() { getResponseBuilder().updateComponent("headerSelect"); getResponseBuilder().updateComponent("footerSelect"); } Since these are my dom references... and this does not cut it. I am looking at come

bidirectional dom interface

2008-01-16 Thread Ken in nashua
Hi Folks, I am impressed with this interface. @EventListener(events = { "onchange" }, targets = { "pagingSpanSelect" }, submitForm = "myForm", async = true) public void pagingSpanListener(IRequestCycle cycle) { } It provides a nice interface from DOM into server side. But How do I talk t