I think that it would be better to have an external js library included with
tapestry. Your validation example was very good: why have a custom one in
the tapestry core if DOJO has a good and continously developed one?
Maybe this would free some tapestry developer resources as well.
DOJO seems to be a very good choice nowdays, it not only has some AJAX
components but a very good base infrastructure!
Based on the DOJO dev list a big amount of development is going on to
dissolve the performace and "unnecessary including of packages" problems in
DOJO.
So including DOJO does not mean that it will be loaded in each page. But
components should have a choice during rendering to include the required
DOJO packages. And a smarter Shell component would take care of the
optimizations (maybe not including any DOJO files at all if not needed).
About AJAX. As I see most web frameworks will (or do) support it out of the
box, so tapestry should do it, too. For example it's not good to have two
separate Form or DirectLink components (1 for normal and 1 for ajax). This
means that some (minimal?) integration of AJAX to the core is necessary.
Regards,
Norbi
----- Original Message -----
From: "Jesse Kuhnert" <[EMAIL PROTECTED]>
To: "Tapestry development" <[email protected]>
Sent: Thursday, February 02, 2006 5:49 AM
Subject: Re: Tapestry 4.1 AJAX support (& other things)
Ok, sounds good...
On a side note, I'm not dead set against not including dojo in tapestrys
core, I just want to be sure it's for a very good reason as it will sort of
take some of the fun out of what I'm doing. It's not a ~must have~. The ajax
support will still work either way..
On 2/1/06, Ron Piterman <[EMAIL PROTECTED]> wrote:
as mentioned in my previous postings, its quite a time difference, so I
will set some test tommorow...
Cheers,
Ron
Jesse Kuhnert wrote:
> There is a delay whenever using a dojo page - I see it more at home than
>
>
>>on my dev box, and that concerns me:
>>I don't know what dojo does that makes the browser think twice before it
>>shows a page but it does somthing, and this 0.5 seconds (in the good
>>case) where my browser window is white - this 0.5 seconds will lead my
>>customers to click to the competitor's web site, so I just can not
>>afford it.
>>
>>this "white delay" exists also to some extent in prototype but dojo
>>breaks the records there...
>>As said, in (current) tapestry pages (also with forms) this does not
>>happen, and as for me, it also shouldn't.
>
>
>
> I'd be very interested in knowing if you experienced this delay if you
> configured dojo using "parseWdigets: false" in your djConfig variable.
> That's the exact reason why you experienced delays a long time ago, and
was
> addressed in my previous email I believe.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.25/247 - Release Date: 2006. 01.
31.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
