From: <g7c...@sn...> - 2001-03-24 22:59:19
|
----- Original Message ----- From: "Todd Owen to...@ow... XXXXXXXXXXXXXXXXXXX" <XXXXXXXXXXXXXXXXXXXXXXXXX> >Steven, could you elaborate on your XML idea? > --Todd Sure, here is an example of what I mean (this is a sample from phpweblog, which uses XML as it's layout format): Then you could design a "Layout/Theme Admin" page that would simply use PHP's XML facilities to read/write the theme files. You would only need one php script then, which would simply read in the appropriate XML file. Does that make sense? I am not an XML nor PHP wizard, but I think that XML would really help with making Themes easily designable. ------------------------------------------ ample ------------------------------------------- <?xml version="1.0"?> <layout> <info> <author>Stephen</author> <description>Steves Office</description> <version>0.5.0</version> </info> <item> <element>BgURL</element> <value></value> </item> <item> <element>LogoURL</element> <value>/images/StevesOffice.jpg</value> </item> <item> <element>FgColor</element> <value>#000000</value> </item> <item> <element>LinkColor</element> <value>#000000</value> </item> etc.. |
From: Todd O. <to...@da...> - 2001-03-25 04:02:24
|
Steven, this idea has merit; sort of like a CSS on steroids--of course CSS entities would have to go in the XML too. What do you think about this approach Jason? I assume we could use forms to create the XML or allow certain admins to upload them directly once we decide on the keywords. Then we would only have to store the XML filename and path in the database. Is there anyone else besides Steven that would like to think on this some more? BTW, having some XML in you project usually bumps you up at least one cool factor anyway ;) --Todd |
From: Jason C. <cam...@xp...> - 2001-03-25 05:04:42
|
Just got back from the hockey game and started reading this....Anyways.... Yea I like this idea for sure. If we could maybe store even the XML code into a table that would be cool too but using just one file would be fine. I was going to check out phpweblog's theme functions after I read somewhere they used XML. I think I'll look at that some more tomorrow. I'm at a stand still anyways until we decide what to change in the system before adding anything new to it. Jason Campbell Xplozive Media Technologies > Steven, this idea has merit; sort of like a CSS on steroids--of course > CSS entities would have to go in the XML too. What do you think about > this approach Jason? > > I assume we could use forms to create the XML or allow certain admins > to upload them directly once we decide on the keywords. Then we would > only have to store the XML filename and path in the database. Is there > anyone else besides Steven that would like to think on this some more? > > BTW, having some XML in you project usually bumps you up at least one > cool factor anyway ;) > > --Todd > > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
From: Todd O. <to...@da...> - 2001-03-25 18:57:10
|
I've looked at phpweblog and that project uses HTML style templates/themes, which is better than what we're using now, but it's not XML either. --Todd |
From: Jason C. <cam...@xp...> - 2001-03-25 19:34:41
|
There are .XLAY files which I believe are XML based. At least they look that way. phpweblog looks pretty damn good too for that matter. That theme functionality is still alot better than what we have now. > I've looked at phpweblog and that project uses HTML style > templates/themes, which is better than what we're using now, but it's > not XML either. > > --Todd > > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
From: Todd O. <to...@da...> - 2001-03-25 20:27:08
|
Jason, you're right about the .xlay files. I was looking at their .tmpl files, which are html. --Todd |
From: Jason C. <cam...@xp...> - 2001-03-25 20:35:15
|
Looks to be a pretty good system to me for themes. I've seen some other nice stuff in Drupal which uses classes for alot core code of the engine. Pretty cool stuff thats for sure... > Jason, you're right about the .xlay files. I was looking at their > .tmpl files, which are html. > > --Todd > > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
From: Karsten D. <k.d...@tu...> - 2001-03-26 14:17:29
|
On Sun, Mar 25, 2001 at 03:30:41PM -0500, Todd Owen wrote: > Jason, you're right about the .xlay files. I was looking at their .tmpl > files, which are html. HTML templates seem to be the best solution right now. I wrote an email to jason Campbell (and forwarded it to Brian later), but dind't get any response until now. I will elaborate on my ideas in details later. But again: HTML templates (combined with (PEAR:)Cache) are the way to go, IMHO. The use of XML to to the basic placement of blocks might make sense. But someone is working on arbritrary block positioning right now, right? So lets see what the results are, before jumping on the XML wagon just because it is cool. Regards, Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |
From: Jason C. <cam...@xp...> - 2001-03-26 15:08:36
|
I'm working on the new block code but if we're changing the theme system, which I and others things we should, I don't want to commit stuff to CVS that will need to be recoded for the new theme system. I think we need to get on IRC and have a developers meeting soon to decide what we want to get done with the project before anything else gets added to the core code base. We as the developers need to decide what we want to do with the database first and then work from there. I've heard talk about changing the structure of the tables and what not, if thats going to happen and be in the core code I say we have a meeting SOON and decide on it and get that done first, when thats completed we can add/modify other parts of the system around the new model and maybe get a modular system started. I don't want to write or commit code that will need to be rewritten if the whole system changes. Anyone else feel this way? Jason Campbell Xplozive Media Technologies www.xplozivemedia.com phpWebSite Developer > On Sun, Mar 25, 2001 at 03:30:41PM -0500, Todd Owen wrote: > >> Jason, you're right about the .xlay files. I was looking at their >> .tmpl files, which are html. > > HTML templates seem to be the best solution right now. I wrote an email > to jason Campbell (and forwarded it to Brian later), but dind't get any > response until now. I will elaborate on my ideas in details later. But > again: HTML templates (combined with (PEAR:)Cache) are the way to go, > IMHO. > > The use of XML to to the basic placement of blocks might make sense. > But someone is working on arbritrary block positioning right now, > right? So lets see what the results are, before jumping on the XML > wagon just because it is cool. > > Regards, > Karsten > -- > Why do we have to hide from the police, daddy? > Because we use emacs, son. They use vi. > ----------------------------- > mailto:k.d...@tu... w³: http://www.k-fish.de/ > gpg: http://www.k-fish.de/mykeys.gpg |
From: Christian S. <chr...@sc...> - 2001-03-26 15:46:53
|
Karsten Dambekalns wrote: > > HTML templates seem to be the best solution right now. I wrote an email to > jason Campbell (and forwarded it to Brian later), but dind't get any > response until now. I will elaborate on my ideas in details later. But > again: HTML templates (combined with (PEAR:)Cache) are the way to go, IMHO. > > The use of XML to to the basic placement of blocks might make sense. But > someone is working on arbritrary block positioning right now, right? So lets > see what the results are, before jumping on the XML wagon just because it > is cool. I don't think XML should be used because of it's coolness but because of it's portability and universality. XML or JSP template generation is one of the main issues Forrester Research focused as an absoulute "must have" in their last study about professional content management systems. PHP plus XML would give a highly scalable system relying on internet standards instead of all that proprietary formats used in today's portal solutions. The other industry standard would be Java server pages with Tomcat or BEA Weblogic - far away from anything that phpWS is or should ever be. Chris |
From: Karsten D. <k.d...@tu...> - 2001-03-26 14:17:30
|
On Sat, Mar 24, 2001 at 11:05:57PM -0500, Todd Owen wrote: > BTW, having some XML in you project usually bumps you up at least one cool > factor anyway ;) Not too good a reason :-/ Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |
From: Karsten D. <k.d...@tu...> - 2001-03-26 14:17:28
|
On Sat, Mar 24, 2001 at 03:00:22PM -0800, g7c...@sn... wrote: > Sure, here is an example of what I mean (this is a sample from phpweblog, > which uses XML as it's layout format): > [...] > I am not an XML nor PHP wizard, but I think that XML would really help wi= th > making Themes easily designable. [...] > <item> > <element>FgColor</element> > <value>#000000</value> > </item> I think this is a "buzzword-only" use of XML. Defining colors could be done through CSS easier and with more clarity and performance I believe. XML used in conjunction with XSL might make sense, but XML in this way... I don't like the idea. Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |