On Thu, 31 Mar 2005 09:52:29 -0500, qbxk <[EMAIL PROTECTED]> wrote: > Tony is my friend. he knows. > > >> I still think client side templating is a daft idea.. Server-side > >> templating systems such as TT2 have grown with the assumption that > >> including another file is a relatively cheap and reliable process, and > >> using seperate template files is basically how they provide > >> modularity.. but the situation is very different client side, fetching > >> a new template is a slow complicated procedure that may or may not > >> work, > >> > > > > > > Google seem to have got it working pretty well. > > > > > damn right. > > _______________________________________________ > templates mailing list > [email protected] > http://lists.template-toolkit.org/mailman/listinfo/templates >
I've been doing quite a bit with XmlHTTPRequest (Apple docs are a great resource to brush up on http://developer.apple.com/internet/webcontent/xmlhttpreq.html) -- You already have a "template" Engine, it's called the DOM :) It's just a heirarchical display device... JavaScript already supports callbacks. I have a system in place (not in any state to release, but I can writeup a doc on it) that accepts callbacks loaded from an XmlHTTPRequest datagram and processes it. This way you just hack in a display handler in JavaScript and away it goes. This, in conjunction with TT has proven to be quite the useful tool. -- J. Shirley >> [EMAIL PROTECTED] Kill Two Stones with One Bird http://www.toeat.com | http://www.new-wheel.com _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
