[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-user
Subject:    Re: jquery jgrowl params not working
From:       "D.R." <d.rehle () googlemail ! com>
Date:       2013-06-27 19:27:58
Message-ID: 51CC923E.7000906 () gmail ! com
[Download RAW message or body]

Ciao Thiago,

yes, happy on the one hand as i was able to figure out where the problem
is and how to fix it.
But sad on the other hand that my app now depends on custom changes of a
lib.

I did a post on the googlegroup of the tapestry-jquery guys. Manu wants
me to make a fork and a pull request.
Seems now is the time to start fighting with git.

Thanx again, Thiago!


Kind regards
David


Am 26.06.2013 23:39, schrieb Thiago H de Paula Figueiredo:
> On Wed, 26 Jun 2013 17:17:46 -0300, D.R. <d.r@googlemail.com> wrote:
>
>> Then i just rebooted my server and it works with
>> retour.put("beforeClose", new JSONLiteral("function(e,m) {alert('About
>> to close this notification!');}"));
>
> That's a correct way of doing that.
>
>> but not with:
>> retour.put("beforeClose", "function(e,m) {alert('About to close this
>> notification!');}");
>
> That's a wrong way of doing that, so it's expected to not work.
>
>> so JSONLiteral seems the way to go, also my custom function is called
>> when i do a: retour.put("beforeClose", new
>> JSONLiteral("mybeforeclose"));
>
> That's a corret way of doing that. I'd say it's the correct one. I
> guess, in this case, you don't need JSONLiteral, as you're not
> including a function.
>
>> But what shall i do now?
>
> Be happy because it's working? :)
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]