skip to main content

kiesler.at

Understanding the Display Engine
updated by rck, 2004-11-15

Actually, one of the more powerful things in phpWebSite is the Display engine. A content management like phpWS does just that: It manages your content. I'll show you, how.

                     
1 | 2 | 3 | 4 | 5 | 6

Overview

Components of the phpws Display Engine
the display engine

Have a look to the graphic to the right. It's the logical structure of a phpWebSite screen. If you are looking at a phpWebSite screen, you are looking at exactly this structure.

Our content, of course, is on top. It's why you set up your site in the first place, isn't it? But please remember, I'll go through that in more detail in a later page: You content is not about font sizes, colours, boldness etc. It's about plain information, mixed with a bit of structure. The more you control on the content (and markup) level, the less effective the rest of the display engine and finally your Browser can work with it.

Theme vs. Module

phpWS supports themes. Most CMSes do. The concept is pretty simple: Seperate, how the page looks and -- to a certain extend -- behaves from the rest of the content. And make that look and feel customizeable.

Compare a theme to, say, a WinAMP skin. Or your GUIs Theme, be it KDE or Windows XP. OS X, on the other hand, looks pretty much like Aqua all the time. The theme there seems to be fixed, which isn't as bad as it sounds.

You can and actually should customize your site theme, so it can be recognized and differentiated from other sites. On the other hand, you usually probably won't change your modules, unless you are developing yourself. Modules are autark, they handle stuff by themselves. Still, they allow you to make theme specific templates. More on that later.

Where to find them

You themes are located in themes/ of your phpwebsite root directory, your modules in mod/.
                     
1 | 2 | 3 | 4 | 5 | 6



RSSComments - Make a comment
The comments are owned by the poster. We are not responsible for its content.

  • Great article!

    Posted on 2004-11-13 05:11:11 By aDarkling[2]

    Very Informative!

    Possibly too informative, though. It might be better to break this down 3 articles, like:

    Understanding the Display Engine
    Effective CSS with phpWebsite
    Writing good HTML for phpWebsite

    because there's so much to cover, like the /images directory, how templating tags work, necessary tags for theme.tpl, what theme.php is, etc..

    I'd like to see examples of what the theme.tpl looks like, like when you suggested using 2 .css files, there should be an example of how they are used.

    I like the analogy you used for Box Styles.
    "default_pop.tpl" has been obsolete since (I think) 0.9.1, but noone ever got around to deleting it.

    I haven't played around with templates in months, but as for module templates from the theme being loaded the second time they are used, you may want to try turning the cache off. I think the templates may either be stored in the cache or in session memory.

    Good job!
    I look forward to seeing where this goes!

    [Reply ]

    • Article Breakup

      Posted on 2004-11-13 12:24:13 By rck[110]

      Very Informative!

      Possibly too informative, though. It might be better to break this down 3 articles, like:

      Understanding the Display Engine
      Effective CSS with phpWebsite
      Writing good HTML for phpWebsite

      In fact, this was meant to be a overview article about all aspects of the display engine of phpWebSite. I've already tried to point out the things on writing good HTML in my Semantic Web article, which didn't have the impact I had thought.

      I too see the need for guidance of good CSS and HTML generally, as well as taylored for phpWebSite and think about articles on that all the time. As soon as I know, how I can sum that up nicely, I will do it. Suggestions are always welcome of course

      [Reply ]

    • Examples

      Posted on 2004-11-13 12:26:24 By rck[110]

      I'd like to see examples of what the theme.tpl looks like, like when you suggested using 2 .css files, there should be an example of how they are used.

      Did you check out the Autumn theme already? It's a pretty good example of what I'm writing about. When you open it's theme.tpl, you'll see three css links (standard.css, colours.css and layout_screen.css) that are exactly doing what I describe in that article. That theme could be easily extended with, say, layout_handheld.css, layout_audible.css, whatever.

      As soon as I have an idea of the outline, I will go into that in more detail in it's own article. Until then: Feel free to discuss it right here!

      [Reply ]

    • Templates load only the second time

      Posted on 2004-11-13 12:30:15 By rck[110]

      changed On 2004-11-13 17:33:23 Edited By rck (reason: luck vs. look)

      I haven't played around with templates in months, but as for module templates from the theme being loaded the second time they are used, you may want to try turning the cache off. I think the templates may either be stored in the cache or in session memory.

      I've already turned off caching in the phpWebSite config. While it helps overall performance, it doesn't change this issue, as far as I can tell. Even if I do shift-reload pages in my browser (which in fact shouldn't be neccessary with the right http-headers), I still get the templates only the second time

      It must be some kind of caching issue, but I don't know where to look. Maybe appstate or someone else can gain some insight on this topic? I've read about people that have the same issue already, so I guess it should be reproducable.

      [Reply ]

    • Re: Great article!

      Posted on 2004-11-13 12:31:44 By rck[110]

      Very Informative!

      I like the analogy you used for Box Styles.

      Good job!
      I look forward to seeing where this goes!
      Thank you! It wouldn't be possible without your Article Manager... ;)

      [Reply ]

  • A Brave Step

    Posted on 2004-11-14 02:01:17 By Anonymous

    Good article, and probably the pilot of many more specific explanations. Well done and clears up a confusing area.

    quote
    I've already tried to point out the things on writing good HTML in my Semantic Web article, which didn't have the impact I had thought.
    unquote

    My opinion? There are many places pointing out good HTML etc but after unpacking phpws we tend to be more into getting the look together... if phpwebsite display/theming/customisation tutorials follow good practise we the flock will fall into line! You have the power - convert us!

    [Reply ]

RSSAll Articles
2008, 2007, 2006, 2005, 2004

What's Related

Article Manager

Tutorials

Latest Updates

AdministrativeTexts
updated by freddiemac1993, 2013-06-14
wiki

Re: adventures
created by brittdavis10, 2012-02-23 (1 rply, 3 views)
thread

Re: how to run phpwebsite...
created by alexander, 2011-08-25 (2 rpls, 3607 views)
thread

Re: Forum tags
created by HaroldFaragher, 2011-08-22 (3 rpls, 8488 views)
thread


Zu den KO2100 Foren