Yes, it was a mistake to leave that parameter in there at all. It was during a fanciful/fleeting moment where I thought it would be a good/practical idea to globally turn "ajax" on/off like a water spicket.
Rational thought soon returned when actually implementing these features. You should find that no XmlHttpObject's will be created against your will unless you specifically set a parameter or call a method that is designed to do it. (whether directly or as a side effect). The framework does continue to include javascript in your pages, as it has always done. This page outlines more behind this thought, http://tapestry.apache.org/tapestry4.1/javascript/packaging.html. The summary between that documented page, and another email written on this list - is that your thoughts are valid/common, but until someone presents me with a real "problem" that I can measure and test against I'm not going to invest the time/effort it would require to write the API around unknown object environments. I would certainly be all for reducing the total compressed size of the initial dojo bootstrap file though. No argument here for that :) Some of it would involve simply including less packages in the default build, some of it involving other things I've been mulling over in my head for a while. So, it's not set in stone yet, just convenient so far. I'm willing to work with someone(s) when/if anyone gets a bug up their proverbial butt about it enough to work with me on it :) On 8/4/06, hv @ Fashion Content <[EMAIL PROTECTED]> wrote:
I think the intention is that ajax functionality is disabled by default. "Bernard" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] > Beat Hoermann wrote: >> I surrounded the form component with a shell component. After all, my >> tiny web- >> app, just displaying a simple text field and a submit button, not using >> ajax nor any dojo things, was forced to load the 173 KByte heavy >> "dojo.js". The integration of dojo into Tapestry seems quite invasive to >> me. > > Take look at this (Shell component): > < http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-framework/src/java/org/apache/tapestry/html/Shell.jwc?view=markup > > > it is my guess, that you need to set "ajaxEnabled" parameter to false > (true is default). > > Jesse, I wouldn't be so eager to enable Ajax on default. Ajax is cool but > I'd rather have working version of plain html app first, than fiddling > with JS code which may not work on all browsers. After all, good UI design > principle says that you should provide alternative with non-JS UI when the > JS is disabled. Will 4.1 components do that? > > I would rather to work like that: if I include Ajax enabled component it > would include required JS scripts (with unique). No ajax enabled > components used - no redundant js included. > > Beat, your example is of "pet-shop" kind but I agree that is a little bit > of overkill. The good side is that browser caches JS so it would be > downloaded once :) > > Best regards, > Bernard > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
