On Wed, 03 Mar 2010 11:35:00 -0300, DavidWei wrote:
Thanks for your suggestion. I will try to do what you suggested and to
see if it is working.
I can assure you it works, even being easier than using a script block.
Generating JavaScript in templates, regardless of which engine, is worse
Thanks for your suggestion. I will try to do what you suggested and to see if
it is working.
By the way, I like to point out that exact same codes work fine with old
version Tapestry 5.0.0.18, but do not work with T5.1.0.5 when I am upgrading
Tapestry. So there must be some changes on renderings
On Tue, 02 Mar 2010 18:54:40 -0300, DavidWei wrote:
When you mentioned "Static", I do not know what you mean? in my case, the
parameters passed in have to be loaded dynamically because we are using a
single text editor to edit many text areas so that each area(called
content block) will have
Hi Howard,
Thanks for your response.
In the web app I am working on. I did have a Javascript in a .js file and
reference it. In the code example, I just want to simplify the codes by
using inline javascript codes.
The problem now is not that it can not reference the method, but it popups
javas
Don't do that. Put static JavaScript in a .js file and just reference
it. Use (in 5.2) JavaScript.importJavaScriptLibrary().
On Tue, Mar 2, 2010 at 1:16 PM, DavidWei wrote:
>
> Hi,
>
> when I am trying to upgrade our web app to Tapestry 5.1.0.5, I have got a
> javascript syntax error when a jav
