RE: [SMARTY] XML+XSLT or Smarty?

If you are going to provide multiple presentations for your objects (Example: HTML, WML, TXT, PDF, ETC ETC) Then you can benefit from managing them in XML and use an XSLT stylesheet to convert them. If not you can just use Smarty with a set of templates for each presentation. -----Original Message----- From: Hardik Doshi [mailto:php_hardik@yahoo.com] Sent: Thursday, March 27, 2003 12:49 PM To: luis; 'Smarty General'; 'Smarty Dev' Subject: RE: [SMARTY] XML+XSLT or Smarty? Thanks for your quick feedback. >From your reply, i got the following layout in my mind. 1. First of all PHP script calls proper table of MySQL (or any) database and retrieve information in XML format. 2. Now PHP calls XSLT processor to take care of recently generated XML document. 3. XSLT renders XML document and get proper printable contents. 4. XSLT gives printable contents to Smarty template engine to print result set in proper layout. Is this correct? Thats what you mean? Correct me if i am wrong anywhere. Now from your explanation i have one question for you. Why do you want to make one extra call for XML+XSLT processing? Is it necessary? From my understanding, it makes the application slower because of addition of extra processing. Please explain me clearly. If you have any examples or tutorial explaining your idea than it would be nice. Again thanks for your help. Hardik Doshi --- luis <luis@fuegolabs.com> wrote: > You can use both. > For example you can have an XML representation for > some objects and use > XSLT to render the object in different > presentations. > You can also have a set off different Smarty > templates for presentations > and use the proper XML transformation depending on > the presentation > being used. > A possible idea is to use Smarty for all the layout > and pages in your > site and XML+XSLT for displaying objects in your > pages. For example you > can have an XML document representing an "article" > and use XSLT to > transform the article to HTML, WML or say PDF. > There're many options. > What I wouldn't do is to use XML+XSLT to generate > HTML pages for your > site or application that's usually hard to maintain, > a Smarty template > is much simple and easy to maintain than an XSLT > transformation. > > -----Original Message----- > From: Hardik Doshi [mailto:php_hardik@yahoo.com] > Sent: Thursday, March 27, 2003 12:13 PM > To: Smarty General; Smarty Dev > Subject: [SMARTY] XML+XSLT or Smarty? > > Hello Everyone, > > I am writing a PHP based student management portal > and > library management software for one graduate > college. > I am looking the possibility of using template > engine > in my web based applications. After initial research > i > come with two ideas namely Smarty template engine > and > XML+XSLT technology. Now i need feedback from Smarty > template community about advantages of smarty over > XML+XSLT or in either way. > > Please guide me in proper direction based on your > experience with above two different template > engines. > > Thanks in advance. > > Hardik Doshi > > __________________________________________________ > Do you Yahoo!? > Yahoo! Platinum - Watch CBS' NCAA March Madness, > live on your desktop! > http://platinum.yahoo.com > > -- > Smarty General Mailing List (http://smarty.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > > -- > Smarty General Mailing List (http://smarty.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com