Mh, I don't really know, but I think smarty is even better, because XSL Stylesheets have to be translatet by an extra Server Engine, so everything can be translatet into HTML, so far as I know. So it is not possible to just work with an standard Apache unless you install an extra XML Module or special Apache Version on the Server.
Smarty can be used without installing some extra things, I think. But really don't know either, because I never used smarty before, just read a little about it ;)). XML should maybe be used to store Configurationfiles and Database Content into static files for exchanging the Content with other Applikations like Quark Xpress or Indesign or maybe to share it with with Cellphones (Which there is no need to, because PHP is able to write XHTML). I don't know if there is an XML/XSL Browser Around or how the Data could be shown, if I would know I would start to write all my Websites in XML, if this is possible. Maybe someone knows a litte more and want to tell some about. Have a nice day! Sascha ----- Original Message ----- From: "Hardik Doshi" <[EMAIL PROTECTED]> To: "Sascha Braun" <[EMAIL PROTECTED]>; "PHP General list" <[EMAIL PROTECTED]>; "Aaron" <[EMAIL PROTECTED]> Sent: Monday, February 10, 2003 3:55 PM Subject: Re: [PHP] WYSIWIG CMS Part1 > I have a same question in my mind about XML. > > I have another question in my mind too. > > If we are using smarty template engine in our > development then what is need of XML and XSLT for > presentation layer? I think XML and XSLT work is > automatically done in smarty template engine. Am i > right? Please correct me if i am wrong. Let me know > which one is good to use smarty engine or XML,XSLT for > seperating interface and php code? > > thanks > > Hardik > > --- Sascha Braun <[EMAIL PROTECTED]> wrote: > > I know how XML works and how a wellformed document > > may look > > like, but I must say, I really dont know why I > > should use XML as long > > I store everything in a Database. > > > > I've read about all good CMS Systems use XML as a > > musthave, but I > > don't understand why. > > > > Would be nice, if you would explain me which data I > > should store in > > XML and why. > > Maybe its usefull together with big Customer > > Management Systems, > > or do you have other Ideas? > > > > Please discuss a little about it with me, I would > > find it very interesting > > :)) > > > > CYA > > > > Sascha > > > > ----- Original Message ----- > > From: "Aaron" <[EMAIL PROTECTED]> > > To: "Sascha Braun" <[EMAIL PROTECTED]> > > Sent: Sunday, February 09, 2003 11:43 PM > > Subject: Re: [PHP] WYSIWIG CMS Part1 > > > > > > > look into using XML if you havent already. > > > > > > > > > Sascha Braun wrote: > > > > > > >Ok, > > > > > > > >overspoken. I'm going to write my basic CMS > > Concept here, and let us see > > > >what happens then. My Multilanguage Frontend > > Engine has even finished, > > > >but still needs a nice Admin Frontend to do the > > translation of the > > Frontend. > > > > > > > >Ok, lets start. Later I will tell some about the > > things which I could not > > really > > > >understand yet, maybe somebody is able to help. > > > > > > > >Tasks of the CMS (I called it freecon, dont know > > if there is something > > similar): > > > > > > > >1. Template Engine > > > >2. Design Management > > > >3. Article Management > > > >4. Content Management > > > >5. User Management > > > >6. Customer Management > > > >7. Message Management > > > > > > > >1. The "Template Engine" should help developers > > to easy build Websites > > based > > > >on the CMS. The only Thing the Developer has to > > do, is to develop an > > static > > > >HTML Webpage Design and replace all the Visitor > > viewable and Admin > > viewable > > > >textparts with special "CMS Based Tags". As there > > is possibility to write > > parts > > > >of the CMS as Modules, it would be very nice if > > fx. the customer login > > could > > > >consist of a small code sniped and a border > > (Table and Images fx.) so the > > > >developer can easely change the design of the > > page, probably with the > > "Design > > > >Management". > > > > > > > >2. The Design Management is part of the > > Administration Kit for the CMS. > > With > > > >this tool you should be able to change the Design > > of the Templates and if > > you > > > >used the "CMS Based Tags" you should be able to > > upload new parts of the > > > >homepage design and change the hole page look, > > with a few mouseclicks. > > > >So there has be an Design Table in the Database > > or an configuration file, > > > >where all the Imageparts are stored and together > > build the page look and > > > >feel. The CSS Stylesheet should the be changeable > > to a lot of forms, seen > > > >in phpbb or other nice templated website tools. > > > > > > > >3. The Article Management should be part of the > > Admin Interface where you > > > >can deside, of which parts an article should be > > consist. Fx. an Article > > could > > > >possibly consist of an Headline, Introduction, > > Shortdescription, > > Description, > > > >1 Image, 2 Images and much more. So it would be > > nice, if the Admin could > > > >give some orders on which parts a text may > > consist of and which design > > you > > > >should be able to chose from. When you want to > > write a new Newstext and > > > >the Admin decided that newstexts should consist > > of an headline and a > > short > > > >description toghether with the maximum of 1 > > Picture, you will chose when > > > >you want to create the text in which language you > > want to create it and > > you > > > >will enter an custom frontend for the article, > > where only the form fields > > are > > > >visible you may use to write the article, when > > you wanted you create the > > article > > > >in more than one language, you will able to > > choose if you want to see all > > forms. > > > >(I mean for the different translations on one > > page or you will be able to > > enter the > > > >translate mode, where you will see fx, headline > > in english and an empty > > headline > > > >form below for Italian language, But Later Ill > > explain more about the > > article mana- > > > >gement). I choosed to do it in this way, because > > it will reduce the space > > needed > > > >by the database enormously, because there is an > > table which only holds > > the head- > > > >lines, in all languages, and another one only > > holds the introductions, in > > all langua- > > > >ges, and so on. > > > > > > > >4. The Content Management, I started to explain > > in 3. a little about how > > it should > > > >work. Now I will get a little deeper into it. > > > > > > > >When your Chief decides that you should write an > > article, he starts > > entering a new > > > >title or headline for the task and sets the > > priority and chooses in which > > language > > > >the article should be translated in. After he did > > this, he chooses > > between his em- > > > >ployes who should write this article, if he > > doesnt direktly choose one, > > he can > > > >choose the knowledge which the employe needs to > > have (At this point fits > > the > > > >usermanagement I'll explain later). After he has > > did all this, one or a > > couple of > > > >of employes will receive an email, that there is > > a new task to do. When > > the Chief > > > >only choosed one special employe only one will > > get the message on the > > other hand > > > >of he choosed somebody who knows a lot about PHP > > and there are ten people > > in > > > >the company who know a lot of php all these ten > > people will receive the > > message unless > > > >one of the does not speak or is able to write > > text in one of the needed > > languages. > > > > > > > >When of of the employes enters the page, the > > first thing he will look at > > is is task pool. > > > >In the Task are stored all undone articles who > > need to be written. After > > the employe(from > > > === message truncated === > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
