Hi,
I've created gentle wrapper components around basic form components like
TextField. (I have apply some custom styling, particularly table cells)
For the most part this is easy enough using the nice publishParameters
feature:
public class CTextField extends AxAbstractTextInput {
On 2/28/2011 5:06 AM, Thiago H. de Paula Figueiredo wrote:
On Mon, 28 Feb 2011 05:35:14 -0300, wkm wrote:
I've created gentle wrapper components around basic form components
like TextField. (I have apply some custom styling, particularly table
cells)
Suggestion: implement it as a
Hi,
I've been very much enjoying using tapestry-security.
I can't seem to figure out how to redirect to the original page, after
log-in, however.
I've played around with various settings for SecuritySymbols.ON_SUCCESS,
but that configures the landing page and seems to be independent of the
ynamo/trunk/tapestry-security/src/main/java/org/tynamo/security/components/LoginForm.java?r=HEAD#l112
Cheers.
Alejandro.
On Tue, Apr 5, 2011 at 4:42 AM, wkm wrote:
Hi,
I've been very much enjoying using tapestry-security.
I can't seem to figure out how to redirect to the original pag
Hi,
I'm trying to create a mixin that pulls together a textfield, its label,
and error message with the appropriate styling. Previously I used a
component with parameters, but that interfered with validation.
Is it possible for a mixin to render a component?
I find myself continually writing
On 5/25/2011 2:08 PM, Josh Canfield wrote:
Previously I used a component
with parameters, but that interfered with validation
I'd go with a component. Your trouble with validation was possibly
that you were trying to validate based on the id of the textfield from
within your AxFormField compone
On 5/25/2011 1:39 PM, Thiago H. de Paula Figueiredo wrote:
On Wed, 25 May 2011 16:36:39 -0300, wkm wrote:
Hi,
Hi!
Is it possible for a mixin to render a component?
Short answer: no.
Long answer: no. :) This violates the Tapestry architecture: templates
have static structure.
Ah
On 5/25/2011 7:08 PM, wkm wrote:
public void setupRender() {
clientId = jsSupport.allocateClientId(componentResources);
}
Uh, well, using this instead:
public void setupRender() {
clientId = componentResources.getId();
}
Otherwise AJAX field validation
