Re: Ajax Response adding extra space

Thank you! I am really relieved that it is so straight forward with setting it to false. On the plus side though, the template did get a work over in the process... Thanks again, Rachel @If, @Else and @for have a renderTag parameter - it's true by default Either rethink your template, or set

Ajax Response adding extra space

I have this page that has (amongst other things) a DirectLink and a div on it. Now, if the page is a normal non-ajax page, the div loads up fine with the right layout and that's great. Then I changed the page to use ajax to speed up the initial load of the page. So now, the div is not rendered a

[T4.1.3] Component and Form generated id's and form refresh

Hi I have a component which has a form on it. This component is included in a @For and is rendered on the page a number of times. What I am finding is that the component's generated id's are component component_1 component_2 etc... while the form's generated id is (i'm using jwcid="[EMAIL PROTE

Re: [poll] how do people feel about me changing that validation dialog in 4.1.1 ?

There are so many possibilities! I just love it :) andyhot wrote: > > exactly - and if you're able to control the display (or not) of the dialog > you can easily go for calling the validation methods every 2-3 secs > and displaying little green or red markers here and ther

Re: [poll] how do people feel about me changing that validation dialog in 4.1.1 ?

ap calls to > tapestry.form.validation.processResults e.t.c. > > Take a look at > https://svn.apache.org/repos/asf/tapestry/tapestry4/trunk/tapestry-framework/src/js/tapestry/form.js > to get more ideas. > > > > > RachelS wrote: >> Can a

Re: [poll] how do people feel about me changing that validation dialog in 4.1.1 ?

Can anyone shed some light as to what happened with this idea of having a configurable validation 'theme'? Thanks, Rachel Jessek wrote: > > .. > Not sure which release this belongs in but I've got all kinds of > usability/humane/etc plans for validation that I'm going to want to > try app

Re: Mixing AjaxForm and Form

Hi Marcus That sounds like it will be very nice to use! My eyes must have jumped over that in the documentation. I'm going to go up to 4.1 and see how it goes. Thanks again, Rachel Marcus Schulte wrote: > > > In Tap 4.1, you can do all the things you could do with Tacos' Ajax* > components

Re: Mixing AjaxForm and Form

Hi Marcus I read the Tap4.1 documentation and ultimately we'll move up to that release. The project I am on now is simply to see how viable Tacos is to use. Even after reading the documentation, I still could not see (whether on 4.0 or 4.1) how to get the more detailed validation of Tacos forms

Mixing AjaxForm and Form

Hi there (I'm using Tapestry 4.0.2 and Tacos 4.0.1) I have a situation where I have a Form and a separate AjaxForm on a page. What I find is that the Form works perfectly when the AjaxForm is not also on the page. As soon as the AjaxForm is added, most of the Form's validation fails with errors

Re: Tacos this.form.event has no properties

Thank you for your reply. So if I understand correctly, tapestry has a form.js and tacos has a form.js and when you have both a normal form and an ajax form on the page, the tacos form.js is the one that gets used? I tried adding the tacos.refreshForm instead, but now when I click on that proper

Tacos this.form.event has no properties

I am using Tapestry 4.0.2 and Tacos 4.0.1 On a page, I have 2 forms * the first is on a component and is not ajaxy in any way * the second is on the page and is an ajax form In the component (which is not an ajax form) there is a property selection which causes the form to refresh using the onch