RE: [PHP] WYSIWIG CMS Part1

I really really like the idea of using XML/XSLT for creating future CMS Apps. XML is simply a good way to manage and share content between different companies, etc. Those that are not too familiar with XML, should try and read a little bit on the advantages of it. It is the next generation markup language that many major players support. It's more flexable than HTML/XHTML and less difficult than SGML. > -----Original Message----- > From: Kevin Waterson [mailto:kevin@oceania.net] > Sent: Monday, February 10, 2003 6:27 PM > To: php-general@lists.php.net > Subject: Re: [PHP] WYSIWIG CMS Part1 > > > This one time, at band camp, > Hardik Doshi <php_hardik@yahoo.com> wrote: > > > > THe stuff which you are doing with XSLT and XML is > > pretty same like Smarty template engine? What is the > > advantage of using XML, XSLT than Smarty template > > engine? > > Well basically, Smarty is gay. > Smarty supposedly will seperate code from content. > but you have still need to markup to able to handle loops, > conditions etc which puts code right back into the content. > But it is Smarty code and not PHP code, where is the value in that? > The pre-supposition is of course that html designers are idiots when > what is really needed is to teach them some basics about PHP rather > than introducing an entire new (Smarty) concept. > Of course when you build an application with Smarty you get to > use buzzwords like multi-tiered, but this slows you down. > > The extensive use of regex within the application cannot be a > good thing. The use of tags such as {foobar} could easily be replaced > by <?=$foobar;?> or <?php echo $foobar; ?> and most every thing else > is easily handled with file_get_contents() include() or eval() > I am not saying Smarty is a worthless piece of dog shit, quite, I just > feel it create unneccessary overhead without delivering true seperation > of code and content. > > The XML way I am implementing also does not achieve this, and > does not make any claim to > it mearly makes the information available to many applications which > can format or do with whatever the programmer wants. Example... > If I have a news > script with the output > <root> > <news> > <nid>24</nid> > <news_headline>Smarty is dead</news_headline> > <news_story>People finally wake up</news_story> > </news> > </root> > > Now other applications can snarf this information readily. So you > can do something > like a news headlines block on the side of your page ala > freshmeat. just take the > <root><news><news_headline> in a xsl:foreach and you have it. > This can be done > application using xml. > > So anyhow, just my $0.02 > Try Smarty, try other template solutions, roll your own, or find > the solution that > best fits your needs. There is no ultimate Template Engine or > application. It really > is horses for courses. > > enjoy > Kevin > > -- > ______ > (_____ \ > _____) ) ____ ____ ____ ____ > | ____/ / _ ) / _ | / ___) / _ ) > | | ( (/ / ( ( | |( (___ ( (/ / > |_| \____) \_||_| \____) \____) > Kevin Waterson > Port Macquarie, Australia > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >