> Yep, left myself quite open there...should have been more specific. > I will not write a templating library myself because there are sooooo many > out there, > it would be a learning experience of course but other than that I think it > would be > rarely needed. > I meant bundling it along with the rest of the scripts, (which would add > around 500kb to the > size) and then giving instructions on how to do a basic configuration for > smarty. I've never done it personally, but if this is for one specific client, isn't 500k pretty much insignificant? If it's a problem though, perhaps you could use a smaller template system, that maybe required less configuration. Having that said, I've never used Smarty so I don't know what configuration is involved. Perhaps an auto-config script could be made? > > > > > > Searching google I found this very nice place discussing PHP templating > > (you > > > might also want to read up on how many there are!) > > > http://www.sitepoint.com/forums/showthread.php?t=123769&page=1&pp=25 > > > but no discussion of including any of these with commercial software for > > the > > > client to setup and their results. > > > > Smarty is licensed under the LGPL. > > I've never read the LGPL, but > > TTBOMK that means you can use it in commercial/propriatory software, > > which I'm > > assuming is what you're refering to. > > Nope, sorry, I should have been more specific here too. > I meant what I said above...nobody has discussed what experience they have > had if they > bundled smarty along with their scripts and then told the client how to > configure smarty > or if the clients had any problem configuring smarty etc. > > Cheers, > Ryan > > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.322 / Virus Database: 266.11.14 - Release Date: 5/20/2005 > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
