RE: [SMARTY] Dreamweaver MX & Smarty!
| From: | Peter Bowyer | Date: | Mon, 03 Jun 2002 15:19:28 +0000 |
| Subject: | RE: [SMARTY] Dreamweaver MX & Smarty! | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-4531@lists.php.net to get a copy of this message | ||
At 15:26 03/06/02 +0200, LIMBOURG Arnaud wrote:
If you use XML for templates you're better off with XSLT.Have you tried writing XSLT using a WYSIWYNG editor such as Dreamweaver? It's impossible, and we've got a greater chance of making Dreamweaver MX write Smarty code than we have making it write XSLT. Unfortunate but true :-( Besides, until the new XML/XSLT extension for PHP is written (the one based on libxml) I'd prefer not to use these technologies - especially as my host still hasn't added XSLT support ;-)
I can't see any advantages in having that functionality. If it makes it please keep as plugin or something not loaded every time, smarty is already big enough.I agree. Smarty accounts for 25%+ of the load/compilation time for my web site, longer even than PEAR-DB. When I implement caching I want to see about pulling out the cache management features from the main Smarty class and this should mean that I can check that the page is cached, and if it isn't then I load the main Smarty classes and if it is then I just display the page. That of course is still theoretical, and won't happen until I get the bugs out of the site :-) Peter -- Maple Design - quality web design and programming http://www.mapledesign.co.uk