In the demo they use this link format
# click here to show window
After debugging with firebug I noticed tapestry did not initialize the
windows properly and the ID's are gone. The windows are still initialized
but attached to the Windows DOM element in an array. You can change your
link to this
On Thu, Sep 1, 2011 at 8:52 AM, Nicola Buso wrote:
> Anyone encountered the same problem?
Just to say that the Chenillekit library will have a complete whirl to
support the next 5.3 release...
Cheers
--
Massimo
http://meridio.blogspot.com
--
gt; Hi,
>>
>> Is there anyone using Chenillekit 1.3.2 window component on tapestry 5.2.5 ?
>> I got 'window1 is not defined' error when following code snippet on
>> http://www.chenillekit.org/demo/tapcomp/windowdemo.
>>
>> I got those snippet working succe
Hi all,
I'm using window component from chenillekit 1.1.0, replacing
RenderSupport with JavaScriptSupport, and this problem is solved. :)
Thanks..
On Tue, Jun 28, 2011 at 9:48 AM, Yohan Yudanara
wrote:
> Hi,
>
> Is there anyone using Chenillekit 1.3.2 window component on tapest
Hi,
Is there anyone using Chenillekit 1.3.2 window component on tapestry 5.2.5 ?
I got 'window1 is not defined' error when following code snippet on
http://www.chenillekit.org/demo/tapcomp/windowdemo.
I got those snippet working successfully using chenillekit 1.1.0 and
tapestry 5.1
