Good points, Lance. Yes I will consider adding those features to JumpStart, and
at the very least I will add a link to Observe. Thanks.
On 27 Apr 2015, at 7:37 pm, Lance Java wrote:
> Hi Geoff, as stated on the demo, the observe mixin was inspired by zone
> updater but with a few very handy dif
Hi Geoff, as stated on the demo, the observe mixin was inspired by zone
updater but with a few very handy differences:
1. Developers don't need to deal with request parameters. These are
converted to more user friendly event arguments.
2. You can pass multiple clientside field values. In the jump
I realise this question doesn't relate to T5.4 but, for anyone who's searching
the mailing list, here's a way to handle the same thing in T5.4.
void onChangeOfPersonName(@RequestParameter(value = "input", allowBlank = true)
String personName) {
// find the person and return an Ajax res
Is your autocomplete a select component? If so you can set the 'zone'
attribute and handle the 'onChanged' event to update the zone.
There's also the observe mixin from tapestry-stitch (
http://t5stitch-lazan.rhcloud.com/observedemo). Note: This will require a
javascript tweak to work with jquery
I have managed to resolve it. Wrapping event setup
inside Tapestry.onDOMLoaded() fixed the issue.
Mixin code is here: https://gist.github.com/xfyre/7369149
On Mon, Nov 11, 2013 at 3:15 AM, François Facon wrote:
> without code and without more information on the versions used, it is
> difficult
without code and without more information on the versions used, it is
difficult to dig.
2013/11/10 Ilya Obshadko
> Thanks, that makes sense. Any ideas on hashchange event handling
> compatibility?
>
>
> On Sun, Nov 10, 2013 at 3:29 AM, François Facon >wrote:
>
> > Oups! My bad.
> > if you set
Thanks, that makes sense. Any ideas on hashchange event handling
compatibility?
On Sun, Nov 10, 2013 at 3:29 AM, François Facon wrote:
> Oups! My bad.
> if you set JQuerySymbolConstants.
> SUPPRESS_PROTOTYPE at *false*, the tapestry core components will use a
> prototype implementations.
> see h
Oups! My bad.
if you set JQuerySymbolConstants.
SUPPRESS_PROTOTYPE at *false*, the tapestry core components will use a
prototype implementations.
see https://github.com/got5/tapestry5-jquery/wiki/FAQ
and the first commit about SUPPRESS_PROTOTYPE
https://github.com/got5/tapestry5-jquery/commit/0fcf7
Well, looks like listening to the history events conflicts with
jquery/autocomplete mixin somehow.
jquery-hashchange plugin has same issue: when hashchange event is handled,
autocomplete no longer works.
On Sun, Nov 10, 2013 at 12:31 AM, Ilya Obshadko wrote:
> I don't completely understand, do
I don't completely understand, do you really mean setting
SUPPRESS_PROTOTYPE to *false* allows tapestry to use Prototype
implementations? I'm expecting that SUPPRESS_PROTOTYPE, literally,
suppresses usage of Prototype and allows to switch to jQuery completely. Is
this right?
Seems like I have foun
if you set JQuerySymbolConstants.SUPPRESS_PROTOTYPE at true, the tapestry
core components will use a prototype implementations. In this case,
communication between core components and jQuery plugin is much more
difficult. this option is fine when you are using a lots of prototype code
on the clien
Hi,
I have found problems with jquery such as submit buttons not working when
inside zones that get refreshed, and likewise for ajax dialog links. I have had
to remove quite a bit of the jquery use from my current project, I'm even
considering pulling it entirely from the product.
It appears t
May be another javascript function redefined the hover event handler.
what version do you use?
any javascript console error?
to diagnose this type of problem, you can disable other components one by
one.
could you share your .tml?
2013/11/9 Ilya Obshadko
> This is weird, and I can't find what
13 matches
Mail list logo
