If you look at the source for the tapx-project (https://github.com/hlship/tapx):
This is the patch file that jochenberger and I have been developing:
https://github.com/hlship/tapx/blob/master/tapx-prototype/src/main/resources/com/howardlewisship/tapx/prototype/tapestry-js-fixes.js
The other fil
This worked! Huzzah! Thanks!
On Thu, Apr 21, 2011 at 02:37:23PM +0200, Joakim Olsson wrote:
> You can use a PartialMarkupRendererFilter to get access to
> RenderSupport (I used it to get access to JavaScriptSupport in Tap
> 5.2.4 at least).
>
> See this thread for how I used it:
> http://tapestr
Okay, now I am pretty sure this is a bug related to usage of
in 5.2.5. If I put (which I didn't have
before), the state required error shows up as expected. If I use
attached to state field, the error does not show.
It's like looking for a needle in a haystack.. lol. still could
appreciate
Quick update:
By debugging Select component I see that validation tracker correctly
records the error when I submit the blank option for state. The blank
option is submitted throug the following use case:
1. Select country and state (both have blank options therefore are
required), but leave othe
I'm sorry, I am on Tapestry 5.2.5 :-)
On Thu, Apr 21, 2011 at 10:19 AM, Adam Zimowski wrote:
> @Josh - When I debug Select in 5.2.4 (break on processSubmission(),
> line 166), selectedValue is blank which is expected. So select
> correctly submits without a value, it's just it seems that the
> va
@Josh - When I debug Select in 5.2.4 (break on processSubmission(),
line 166), selectedValue is blank which is expected. So select
correctly submits without a value, it's just it seems that the
validator does not recognize that select state was repopulated via
zone and consequently no value was sub
On Thu, Apr 21, 2011 at 06:22:02AM +0530, Taha Hafeez wrote:
> Hi
>
> What Tapestry version are you using ?
T5.1.0.6
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tap
On Wed, Apr 20, 2011 at 4:07 PM, Howard Lewis Ship wrote:
> That's my intention. Live class reloading would be disabled in
> production, and enable in development.
>
>
I think that is reasonable, but I think it should be treated similar to
tapestry.secure-enabled. By default it is off in develo
You can use a PartialMarkupRendererFilter to get access to
RenderSupport (I used it to get access to JavaScriptSupport in Tap
5.2.4 at least).
See this thread for how I used it:
http://tapestry.1045711.n5.nabble.com/Focus-on-first-field-in-added-row-in-AjaxFormLoop-td3401558.html
/Joakim
On Wed
my $0.02. If it was enabled till today then we should leave it that way.
In documentation there should be note that it is possible to speed up
significantly application by doing something and with cost of no live class
reloads in production.
Regards,
Michal
--
View this message in context:
htt
Hi
I am currently working on drop downs in Tapestry. I have country
drop down . on selecting any value from country the city drop down needs to
be populated asynchronously. PFB the Home.html given below
Home.html
11 matches
Mail list logo