tacos:PartialFor question

2007-02-20 Thread Chris Perfect
Hello,
In the documentation for the PartialFor component it states 
 
"This component will not render the contents of a particular loop during
an ajax request if the key value of the element/component doesn't exist
as an updateComponent to the original request. The values will still be
iterated over, just not rendered." (see
http://tacos.sourceforge.net/components/PartialFor.html)
 
Can someone tell me what is meant by "the key value of the
element/component"? I assume this refers to the component immediately
inside the PartialFor, but is this the (tapestry) component name, the id
attribute or something else? 
 
 
Thanks
Chris

NOTICE
This e-mail and any attachments are confidential and may contain copyright 
material of Macquarie Bank or third parties. If you are not the intended 
recipient of this email you should not read, print, re-transmit, store or act 
in reliance on this e-mail or any attachments, and should destroy all copies of 
them. Macquarie Bank does not guarantee the integrity of any emails or any 
attached files. The views or opinions expressed are the author's own and may 
not reflect the views or opinions of Macquarie Bank.


Submit form and bypass validation

2007-01-15 Thread Chris Perfect
Is it possible to have a submit button on a form that can call a
listener bypassing any validation set for the form (without having to
explicitly code around validation in the listener)? This is useful when
buttons modify the structure of the form: e.g add or remove form
components.
 

Chris Perfect 
Macquarie Bank ISD (Real Estate) 
Ph.   N/A 
Mob. +61 423 041 240 

 

NOTICE
This e-mail and any attachments are confidential and may contain copyright 
material of Macquarie Bank or third parties. If you are not the intended 
recipient of this email you should not read, print, re-transmit, store or act 
in reliance on this e-mail or any attachments, and should destroy all copies of 
them. Macquarie Bank does not guarantee the integrity of any emails or any 
attached files. The views or opinions expressed are the author's own and may 
not reflect the views or opinions of Macquarie Bank.


RE: Problem when using morwe than one intance of an Autocompleter

2006-12-20 Thread Chris Perfect
I have confirmed that the 4.1.2-SNAPSHOT fixes the issue.
Thanks!
Chris 

-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] 
Sent: Thursday, 21 December 2006 8:54 AM
To: Tapestry users
Subject: Re: Problem when using morwe than one intance of an
Autocompleter

Ouch . ...Ok I think you've run into a bug I had in the javascript
template for this component. (I wasn't properly using the  key to
make my javascript variable names unique)

It's fixed and deploying now, but you'll have to make sure you are using
the 4.1.2-SNAPSHOT version of Tapestry, not 4.1.1.

Sorry for the goof. I'll probably go back and re-check everything now to
be sure there aren't any other hidden goofs. (i don't think there will
be but...maybe)

On 12/18/06, Chris Perfect <[EMAIL PROTECTED]> wrote:
> Hello,
> I am having an issue with 4.1.1 (latest snapshot): I have created a 
> component with various form elements that includes an Autocompleter: 
> the component is an address create/edit component and  the autompleter

> is used for the Country field. I have a use case where I need to be 
> able have more than one address in the form and would like to re-use 
> the component however the component works perfectly fine if used in a 
> form once but if I have more than one instance of the component the 
> autocompleter only works in the first instance in the page: any 
> attempt to use the second or subsequent intances doesn't autocomplete 
> and produces the java script message "DEBUG: [SyntaxError: syntax 
> error,
> file: ?service=asset&path=%2Fdojo%2Fdojo.js, line:
> 15]". Has anyone else had this problem and know a solution?
>
> Thanks
> Chris
>
>
>
> NOTICE
> This e-mail and any attachments are confidential and may contain
copyright material of Macquarie Bank or third parties. If you are not
the intended recipient of this email you should not read, print,
re-transmit, store or act in reliance on this e-mail or any attachments,
and should destroy all copies of them. Macquarie Bank does not guarantee
the integrity of any emails or any attached files. The views or opinions
expressed are the author's own and may not reflect the views or opinions
of Macquarie Bank.
>
>


--
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

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


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



Problem when using morwe than one intance of an Autocompleter

2006-12-18 Thread Chris Perfect
Hello,
I am having an issue with 4.1.1 (latest snapshot): I have created a
component with various form elements that includes an Autocompleter: the
component is an address create/edit component and  the autompleter is
used for the Country field. I have a use case where I need to be able
have more than one address in the form and would like to re-use the
component however the component works perfectly fine if used in a form
once but if I have more than one instance of the component the
autocompleter only works in the first instance in the page: any attempt
to use the second or subsequent intances doesn't autocomplete and
produces the java script message "DEBUG: [SyntaxError: syntax error,
file: ?service=asset&path=%2Fdojo%2Fdojo.js, line:
15]". Has anyone else had this problem and know a solution?
 
Thanks
Chris
 
 

NOTICE
This e-mail and any attachments are confidential and may contain copyright 
material of Macquarie Bank or third parties. If you are not the intended 
recipient of this email you should not read, print, re-transmit, store or act 
in reliance on this e-mail or any attachments, and should destroy all copies of 
them. Macquarie Bank does not guarantee the integrity of any emails or any 
attached files. The views or opinions expressed are the author's own and may 
not reflect the views or opinions of Macquarie Bank.