On Thu, 11 Oct 2012 15:34:44 -0300, Ken in Nashua
wrote:
maybe defaultPrefix should have been called bindingPrefix or
defaultBindingPrefix?
In this case, 'prefix', in parameters, can only refer to binding prefixes,
so I think the name is clear enough.
I didn't want to burn you. If you
maybe defaultPrefix should have been called bindingPrefix or
defaultBindingPrefix?
I get sort of dyslexic... and yes the default is what took me
From: kcola...@live.com
To: users@tapestry.apache.org
Subject: RE: readonly parameter binding issue
Date: Thu, 11 Oct 2012 14:27:17 -0400
burn me beautiful Thiago...
thanks
I will give that a shot... and keep note of these special best practices
you will be the first one to see this gallery
i am working on the autopaging button handlers now
I wonder whatever happened to tacos... and jfly... andrea chiumante had some
nice stuff t
On Thu, 11 Oct 2012 11:40:00 -0300, Ken in Nashua
wrote:
Folks,
Hi!
my Gallery component operates a parameter CURSOR
Gallery.JAVA
@Property
@Parameter(required = true, cache = true, defaultPrefix = "0")
private int cursor;
You're confusing defaultPrefix with default paramet
Thanks Lance... I know it might be asking alot...
is there a small snippet code example you could post?
this thing is coming along great
kcola...@live.com
From: kcola...@live.com
To: users@tapestry.apache.org
Subject: readonly parameter binding issue
Date: Thu, 11 Oct 2012 10:40:00 -0400
For persistance between requests, your first consideration should always be
activation context (see @PageActivationContext or onActivate() /
onPassivate()). This will store values as part of the URL.
If activation context does not solve the problem, you should then consider
@Persist to either stor
