How to use custom onSubmit handler in form tag?

The form tag automagically renders a javascript handler for the onSubmit event [1, line 388]. It uses the same snippet that's declared for onclick handler in MarkupConstants.WAIT_FOR_PAGE [2] described in [3]. H

[ANN] First version of tapestry-mfautocomplete is released

Hi, I just released the first version of a new mixin which I call tapestry-mfautocomplete. It's an autocomplete mixin which can populate multiple fields. I use it to populate item description, price and VAT-percentage in an invoicing application for example. The project is at https://github.com/

Re: [ANN] First version of tapestry-mfautocomplete is released

Sounds Great! On Jan 29, 2012, at 10:48 AM, Joakim Olsson wrote: > Hi, > > I just released the first version of a new mixin which I call > tapestry-mfautocomplete. > > It's an autocomplete mixin which can populate multiple fields. I use > it to populate item description, price and VAT-percentage

Re: Referencing the context path from within Javascript?

On Sat, 28 Jan 2012 20:12:06 -0200, Julien Martin wrote: Hello Thiago, Hi! It is on a page template. The advice you provide does work. However, I am realizing I need to concatenate the protocol+host+etc. which is a bit cumbersome. Page templates don't handle anything. Pages, components

Re: Referencing the context path from within Javascript?

On Sun, 29 Jan 2012 19:22:31 -0200, Julien Martin wrote: Thiago, Hi! Yes it is indeed a Tapestry page. Here is the java code for it (there is no template for this page): So the correct way of generating an URL for a page is to @Inject PageRenderLinkSource and use one of its methods. Th

contributeSymbolSource doesn't always work for me?

Hi all, I've seen in a few examples and posts that the way to configure tapestry from a properties file is to use contributeSymbolSource. I would like to configure tapestry firstly from a properties file and secondly hard-set a couple of values from AppModule. I am doing the following:

Re: contributeSymbolSource doesn't always work for me?

Hi! Have you tried ordering (adding "before:*" or "after:*" in your contributions? It's an OrderedConfiguration, so order matters. Without specifying order constraints, there's no guaranteed contribution order. On Sun, 29 Jan 2012 23:45:11 -0200, Paul Stanton wrote: Hi all, I've seen

Re: contributeSymbolSource doesn't always work for me?

Hi Thiago, I assume you mean on my SymbolSource contribution for 'tapestry.properties' .. Which should it be? "before:*" so that it gets loaded first (to initialise correctly), or "after:*" so it gets loaded last (to override other settings) Since I'm getting kind of inconsistent behaviour, I

Re: contributeSymbolSource doesn't always work for me?

Thiago, I've tested with "after:*" and it fails every time, and with "before:*" it succeeds every time. I guess I should have read http://wiki.apache.org/tapestry/Tapestry5HowToReadSymbolsFromPropertiesFile#Tying_it_together since the recommended "after:SystemProperties", "before:Applicati