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-tabpanelfocusedCommentId=12561377#action_12561377Best
 regards Ken in nashua


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: bidirectional dom interfaceDate: 
Wed, 16 Jan 2008 08:15:02 -0500


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 to 
my dom javascript node from here? Is there a way to reference the form and set 
a value of a dom node that models a tapestry widget ? Why do I need this? Well 
My tapestry widget is modeled to a dom node A. But I actually used the @Block 
declaration to model another dom B node to the same widget...  When I change A, 
B stays the same. I need to update the other dom node when one changes. Thanks 
for any tips.Best regards Ken in nashua

Get the power of Windows + Web with the new Windows Live. Get it now! 
_
Helping your favorite cause is as easy as instant messaging. You IM, we give.
http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join

Re: bidirectional dom interface

2008-01-18 Thread DR_GLoPeL_BouCa



Thiago H de Paula Figueiredo-2 wrote:
 
 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 display any change, but in the fireBug bar, inspect de response and
 is
 in there, what's wrong..
 
 
 Try updateComponents=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 work.
-- 
View this message in context: 
http://www.nabble.com/bidirectional-dom-interface-tp14881716p14948083.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-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've form with submit async=true and
 updateComponents=ognl:customerTable, when the ajax response come browser
 don't display any change, but in the fireBug bar, inspect de response and is
 in there, what's wrong..
 Sorry mi english, Thaws. 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: bidirectional dom interface

2008-01-18 Thread DR_GLoPeL_BouCa

this part of my code

form
   input type=submit jwcid=@Submit class=boton value=Aceptar
tag=AgregarProveedor   selected=ognl:comando async=true
updateComponents=customerTable/
 div jwcid=[EMAIL PROTECTED]  
  table
 tr jwcid=@For source=ognl:customers value=ognl:customer
element=tr
td
 
/td
 /tr
  /table
 /div
/form 

thanks for your time


nirvdrum wrote:
 
 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've form with submit async=true and
 updateComponents=ognl:customerTable, when the ajax response come
 browser
 don't display any change, but in the fireBug bar, inspect de response and
 is
 in there, what's wrong..
 Sorry mi english, Thaws. 
 
 
 
 -
 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
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-17 Thread DR_GLoPeL_BouCa

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 display any change, but in the fireBug bar, 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.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



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 display any change, but in the fireBug bar, inspect de response and
 is
 in there, what's wrong..


Try updateComponents=customerTable, without the ognl: prefix.

Thiago


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...
div id=headerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div id=galleryContent
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div id=footerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
 
and this does not cut it.
 
I am looking at cometd sample in tacos and it looks like I need to establish a 
scripting interface?
 
Can anyone confirm? Is there an easier quicker way to update a dom referring to 
a widget from the server side?
Thanks in advance...
Best regards Ken in nashua


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: bidirectional dom interfaceDate: 
Wed, 16 Jan 2008 08:15:02 -0500


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 to 
my dom javascript node from here? Is there a way to reference the form and set 
a value of a dom node that models a tapestry widget ? Why do I need this? Well 
My tapestry widget is modeled to a dom node A. But I actually used the @Block 
declaration to model another dom B node to the same widget...  When I change A, 
B stays the same. I need to update the other dom node when one changes. Thanks 
for any tips.Best regards Ken 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.mspx?ocid=TXT_TAGLM_CPC_VideoChat_distantfamily_012008

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().updateComponent(headerSelect);
 getResponseBuilder().updateComponent(footerSelect);
 }

 Since these are my dom references...
 div id=headerSelect
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div
 div id=galleryContent
 div jwcid=@RenderBlock block=ognl:components.collectionContent /
 /div
 div id=footerSelect
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div

 and this does not cut it.

 I am looking at cometd sample in tacos and it looks like I need to
 establish a scripting interface?

 Can anyone confirm? Is there an easier quicker way to update a dom
 referring to a widget from the server side?
 Thanks in advance...
 Best regards Ken in nashua


 From: [EMAIL PROTECTED]: [EMAIL PROTECTED]:
 bidirectional dom interfaceDate: Wed, 16 Jan 2008 08:15:02 -0500


 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 to my dom javascript node from here? Is there a way to reference the
 form and set a value of a dom node that models a tapestry widget ? Why do I
 need this? Well My tapestry widget is modeled to a dom node A. But I
 actually used the @Block declaration to model another dom B node to the same
 widget...  When I change A, B stays the same. I need to update the other dom
 node when one changes. Thanks for any tips.Best regards Ken 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(R) + Windows Live™.

 http://www.microsoft.com/windows/digitallife/keepintouch.mspx?ocid=TXT_TAGLM_CPC_VideoChat_distantfamily_012008




-- 
Best regards,

Igor Drobiazko


RE: bidirectional dom interface

2008-01-16 Thread Pai911

Hi!
Maybe you should make the division you want to update Tapestry components?
 
div id=[EMAIL PROTECTED] 
div jwcid=@RenderBlock block=ognl:components.autoPagingContent / 
/div 
div id=[EMAIL PROTECTED] 
div jwcid=@RenderBlock block=ognl:components.collectionContent / 
/div 
div id=[EMAIL PROTECTED] 
div jwcid=@RenderBlock block=ognl:components.autoPagingContent / 
/div 


nhhockeyplayer wrote:
 
 
 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...
 div id=headerSelect
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div
 div id=galleryContent
 div jwcid=@RenderBlock block=ognl:components.collectionContent /
 /div
 div id=footerSelect
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div
  
 and this does not cut it.
  
 I am looking at cometd sample in tacos and it looks like I need to
 establish a scripting interface?
  
 Can anyone confirm? Is there an easier quicker way to update a dom
 referring to a widget from the server side?
 Thanks in advance...
 Best regards Ken in nashua
 
 
 From: [EMAIL PROTECTED]: [EMAIL PROTECTED]:
 bidirectional dom interfaceDate: Wed, 16 Jan 2008 08:15:02 -0500
 
 
 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 to my dom javascript node from here? Is there a way to reference the
 form and set a value of a dom node that models a tapestry widget ? Why do
 I need this? Well My tapestry widget is modeled to a dom node A. But I
 actually used the @Block declaration to model another dom B node to the
 same widget...  When I change A, B stays the same. I need to update the
 other dom node when one changes. Thanks for any tips.Best regards Ken 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.mspx?ocid=TXT_TAGLM_CPC_VideoChat_distantfamily_012008
 
 -
 Best regards
 Ken in nashua
 

-- 
View this message in context: 
http://www.nabble.com/bidirectional-dom-interface-tp14881716p14886847.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

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.createTextNode(Loading...)); var contentDom = 
  document.forms[0].document.getElementById(galleryContent); 
contentDom.appendChild(divBlock);
 
contentDom is always NULL now.
 
?
 
Do you kow whats going on?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 the component... 
public void refresh()
{
getResponseBuilder().updateComponent(headerSelect); 
getResponseBuilder().updateComponent(footerSelect); }  Since these are my dom 
references...
div id=headerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div id=galleryContent
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div id=footerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div 
and this does not cut it. I am looking at cometd sample in tacos and it looks 
like I need to establish a scripting interface? Can anyone confirm? Is there an 
easier quicker way to update a dom referring to a widget from the server 
side?Thanks in advance...Best regards Ken in nashua


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: bidirectional dom interfaceDate: 
Wed, 16 Jan 2008 08:15:02 -0500

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 to 
my dom javascript node from here? Is there a way to reference the form and set 
a value of a dom node that models a tapestry widget ? Why do I need this? Well 
My tapestry widget is modeled to a dom node A. But I actually used the @Block 
declaration to model another dom B node to the same widget...  When I change A, 
B stays the same. I need to update the other dom node when one changes. Thanks 
for any tips.Best regards Ken 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™. Start 
now! 
_
Get the power of Windows + Web with the new Windows Live.
http://www.windowslive.com?ocid=TXT_TAGHM_Wave2_powerofwindows_012008

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?
  
 div id=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div 
 div id=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.collectionContent /
 /div 
 div id=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div 
 
 
 nhhockeyplayer wrote:
 
 
 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...
 div id=headerSelect
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div
 div id=galleryContent
 div jwcid=@RenderBlock block=ognl:components.collectionContent /
 /div
 div id=footerSelect
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div
  
 and this does not cut it.
  
 I am looking at cometd sample in tacos and it looks like I need to
 establish a scripting interface?
  
 Can anyone confirm? Is there an easier quicker way to update a dom
 referring to a widget from the server side?
 Thanks in advance...
 Best regards Ken in nashua
 
 
 From: [EMAIL PROTECTED]: [EMAIL PROTECTED]:
 bidirectional dom interfaceDate: Wed, 16 Jan 2008 08:15:02 -0500
 
 
 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 to my dom javascript node from here? Is there a way to reference the
 form and set a value of a dom node that models a tapestry widget ? Why do
 I need this? Well My tapestry widget is modeled to a dom node A. But I
 actually used the @Block declaration to model another dom B node to the
 same widget...  When I change A, B stays the same. I need to update the
 other dom node when one changes. Thanks for any tips.Best regards Ken 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.mspx?ocid=TXT_TAGLM_
 CPC_VideoChat_distantfamily_012008
 
 -
 Best regards
 Ken in nashua
 



-
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 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 the component... 
public void refresh()
{
getResponseBuilder().updateComponent(headerSelect); 
getResponseBuilder().updateComponent(footerSelect); }  Since these are my dom 
references...
div id=headerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div id=galleryContent
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div id=footerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div 
and this does not cut it. I am looking at cometd sample in tacos and it looks 
like I need to establish a scripting interface? Can anyone confirm? Is there an 
easier quicker way to update a dom referring to a widget from the server 
side?Thanks in advance...Best regards Ken in nashua


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: bidirectional dom interfaceDate: 
Wed, 16 Jan 2008 08:15:02 -0500

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 to 
my dom javascript node from here? Is there a way to reference the form and set 
a value of a dom node that models a tapestry widget ? Why do I need this? Well 
My tapestry widget is modeled to a dom node A. But I actually used the @Block 
declaration to model another dom B node to the same widget...  When I change A, 
B stays the same. I need to update the other dom node when one changes. Thanks 
for any tips.Best regards Ken 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™. Start 
now! 
_
Get the power of Windows + Web with the new Windows Live.
http://www.windowslive.com?ocid=TXT_TAGHM_Wave2_powerofwindows_012008

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...
select name=tableSizeSelect id=tableSizeSelect
...
select name=tableSizeSelect_0 id=tableSizeSelect_0
 
Now will HTML crap out if there exist multiple nodes of same ID.
 
My problem is right above. Each select has been modeled with @Block
 
 
here is it.. the declaration
 
span jwcid=[EMAIL PROTECTED]
table width=100% border=1
tr
td width=25% align=left NOWRAP
span jwcid=@Insert value=Table Size/
select jwcid=[EMAIL PROTECTED]
model=ognl:tableSizeModel
value=ognl:tableSize
/
span jwcid=@Insert value=Paging Span/
select jwcid=[EMAIL PROTECTED]
model=ognl:pagingSpanModel
value=ognl:pagingSpan
/
/td
 ...more cut out omitted code
/span
 
  
 
here is it.. the definition...
 
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
 
   -
Now referring back to top... the ID was taken on the first instance but 
animated by tapestry on the second instance.
 
markup...
select name=tableSizeSelect id=tableSizeSelect
...
select name=tableSizeSelect_0 id=tableSizeSelect_0
 
?
 
So now I guess EVERYTHING on the second definition ([EMAIL PROTECTED]) will get 
all of it's ID's appended with an autoincrement.
 
?
 
Here is the million dollar question...
 
Given the following block of code...
 
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
 
How do I get headerSelect and footerSelect be updated against the same widget 
instance (which happens to be the ognl:components.autoPagingContent) ? I 
thought the above snippet was sufficient. It is obviously an ID issue. 
 
Clarification appreciated.
 
Thanks in advance.
 Best regards Ken in nashua


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: bidirectional dom 
interfaceDate: Wed, 16 Jan 2008 14:49:17 -0500


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 the component... 
public void refresh()
{
getResponseBuilder().updateComponent(headerSelect); 
getResponseBuilder().updateComponent(footerSelect); }  Since these are my dom 
references...
div id=headerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div id=galleryContent
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div id=footerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div 
and this does not cut it. I am looking at cometd sample in tacos and it looks 
like I need to establish a scripting interface? Can anyone confirm? Is there an 
easier quicker way to update a dom referring to a widget from the server 
side?Thanks in advance...Best regards Ken in nashua


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: bidirectional dom interfaceDate: 
Wed, 16 Jan 2008 08:15:02 -0500

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 to 
my dom javascript node from here? Is there a way to reference the form and set 
a value of a dom node that models a tapestry widget ? Why do I need this? Well 
My tapestry widget is modeled to a dom node A. But I actually used the @Block 
declaration to model another dom B node to the same widget...  When I change A, 
B stays the same. I need to update the other dom node when one changes. Thanks 
for any tips.Best regards Ken 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™. Start 
now! 

Get the power of Windows + Web with the new Windows Live. Get it now! 
_
Share life as it happens with the new Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008

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: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: bidirectional dom 
interfaceDate: Wed, 16 Jan 2008 15:16:20 -0500


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...select name=tableSizeSelect 
id=tableSizeSelect...select name=tableSizeSelect_0 
id=tableSizeSelect_0 Now will HTML crap out if there exist multiple nodes of 
same ID. My problem is right above. Each select has been modeled with @Block  
here is it.. the declaration 
span jwcid=[EMAIL PROTECTED]
table width=100% border=1
tr
td width=25% align=left NOWRAP
span jwcid=@Insert value=Table Size/
select jwcid=[EMAIL PROTECTED]
model=ognl:tableSizeModel
value=ognl:tableSize
/
span jwcid=@Insert value=Paging Span/
select jwcid=[EMAIL PROTECTED]
model=ognl:pagingSpanModel
value=ognl:pagingSpan
/
/td ...more cut out omitted code/span    here is it.. the 
definition... 
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div
-Now referring back to top... the ID was taken on the first instance but 
animated by tapestry on the second instance. markup...select 
name=tableSizeSelect id=tableSizeSelect...select name=tableSizeSelect_0 
id=tableSizeSelect_0 ? So now I guess EVERYTHING on the second definition 
([EMAIL PROTECTED]) will get all of it's ID's appended with an autoincrement. ? 
Here is the million dollar question... Given the following block of code... 
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div jwcid=[EMAIL PROTECTED]
div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div 
How do I get headerSelect and footerSelect be updated against the same widget 
instance (which happens to be the ognl:components.autoPagingContent) ? I 
thought the above snippet was sufficient. It is obviously an ID issue.  
Clarification appreciated. Thanks in advance. Best regards Ken in nashua


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: bidirectional dom 
interfaceDate: Wed, 16 Jan 2008 14:49:17 -0500

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 the component... 
public void refresh()
{
getResponseBuilder().updateComponent(headerSelect); 
getResponseBuilder().updateComponent(footerSelect); }  Since these are my dom 
references...
div id=headerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
/div
div id=galleryContent
div jwcid=@RenderBlock block=ognl:components.collectionContent /
/div
div id=footerSelect
div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div 
and this does not cut it. I am looking at cometd sample in tacos and it looks 
like I need to establish a scripting interface? Can anyone confirm? Is there an 
easier quicker way to update a dom referring to a widget from the server 
side?Thanks in advance...Best regards Ken in nashua


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: bidirectional dom interfaceDate: 
Wed, 16 Jan 2008 08:15:02 -0500

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 to 
my dom javascript node from here? Is there a way to reference the form and set 
a value of a dom node that models a tapestry widget ? Why do I need this? Well 
My tapestry widget is modeled to a dom node A. But I actually used the @Block 
declaration to model another dom B node to the same widget...  When I change A, 
B stays the same. I need to update the other dom node when one changes. Thanks 
for any tips.Best regards Ken 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™. Start 
now! 

Get the power of Windows + Web with the new Windows Live. Get it now! 

Share life as it happens with the new Windows Live. Start sharing! 

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 whole thing with an @Any div and updateComponent on that.  It will
descend into each child component.  I had to do this to work around a bug in
IE6 (subsequently filed in JIRA).

-- 
Kevin


On 1/16/08 3:26 PM, in article [EMAIL PROTECTED],
Ken in nashua [EMAIL PROTECTED] wrote:

 
 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: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE:
 bidirectional dom interfaceDate: Wed, 16 Jan 2008 15:16:20 -0500
 
 
 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...select name=tableSizeSelect
 id=tableSizeSelect...select name=tableSizeSelect_0
 id=tableSizeSelect_0 Now will HTML crap out if there exist multiple nodes
 of same ID. My problem is right above. Each select has been modeled with
 @Block  here is it.. the declaration
 span jwcid=[EMAIL PROTECTED]
 table width=100% border=1
 tr
 td width=25% align=left NOWRAP
 span jwcid=@Insert value=Table Size/
 select jwcid=[EMAIL PROTECTED]
 model=ognl:tableSizeModel
 value=ognl:tableSize
 /
 span jwcid=@Insert value=Paging Span/
 select jwcid=[EMAIL PROTECTED]
 model=ognl:pagingSpanModel
 value=ognl:pagingSpan
 /
 /td ...more cut out omitted code/span    here is it.. the
 definition... 
 div jwcid=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div
 div jwcid=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.collectionContent /
 /div
 div jwcid=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div
 -Now referring back to top... the ID was taken on the first instance but
 animated by tapestry on the second instance. markup...select
 name=tableSizeSelect id=tableSizeSelect...select
 name=tableSizeSelect_0 id=tableSizeSelect_0 ? So now I guess EVERYTHING
 on the second definition ([EMAIL PROTECTED]) will get all of it's ID's 
 appended
 with an autoincrement. ? Here is the million dollar question... Given the
 following block of code...
 div jwcid=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div
 div jwcid=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.collectionContent /
 /div
 div jwcid=[EMAIL PROTECTED]
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div
 How do I get headerSelect and footerSelect be updated against the same widget
 instance (which happens to be the ognl:components.autoPagingContent) ? I
 thought the above snippet was sufficient. It is obviously an ID issue.
 Clarification appreciated. Thanks in advance. Best regards Ken in nashua
 
 
 From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE:
 bidirectional dom interfaceDate: Wed, 16 Jan 2008 14:49:17 -0500
 
 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 the component...
 public void refresh()
 {
 getResponseBuilder().updateComponent(headerSelect);
 getResponseBuilder().updateComponent(footerSelect); }  Since these are my
 dom references...
 div id=headerSelect
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent /
 /div
 div id=galleryContent
 div jwcid=@RenderBlock block=ognl:components.collectionContent /
 /div
 div id=footerSelect
 div jwcid=@RenderBlock block=ognl:components.autoPagingContent //div
 and this does not cut it. I am looking at cometd sample in tacos and it looks
 like I need to establish a scripting interface? Can anyone confirm? Is there
 an easier quicker way to update a dom referring to a widget from the server
 side?Thanks in advance...Best regards Ken in nashua
 
 
 From: [EMAIL PROTECTED]: [EMAIL PROTECTED]:
 bidirectional dom interfaceDate: Wed, 16 Jan 2008 08:15:02 -0500
 
 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
 to my dom javascript node from here? Is there a way to reference the form and
 set a value of a dom node that models a