Uh, if we're going in this direction, should we at least maybe think about XSL
rather than Smarty? JP
--- j hermanns <j@...> wrote:
> zem wrote:
> > Smarty's no panacea, but the benefits of a cleaner code base are
> > considerable. Done right you can remove all traces of HTML from your
> > code. And it buys you a bunch of display-related functionality for
> > free. At the cost of rewriting code, of course.
> The pain of rewriting existing code shouldn't be too bad, as s9y was
> initially designed (should I say "ment") as some kind of API. This API
> is currently used by the "templates" or "themes" (layout.php). Some
> functions of the s9y API (serendipity_functions.inc.php) are able to
> print HTML, but their use is optional. So, moving to smarty as template
> system should be fairly easy.
> Of course, there finally needs to be some documentation on which
> variables are availible on which page (a list of entries on one page, a
> list of comments on the other, a list of archives, whatever....). These
> variables need to be defined, and a fixed number of "templates" must be
> defined as well. That would be the switch in layout.php handlying the
> action-get-variable. I think.
> > (One of my bplog sites was slashdotted earlier this year. Smarty didn't
> > miss a beat, serving something like half a million hits in a day or so)
> Does anyone have experience with smarty and high load? If it performs,
> smarty would be my choice over the current system. How's smarty
> licensed. Can we bundle it with s9y without any licensing-issues? Does
> it have any special requirements on the server side?
> > The main issue I can see is dealing with URLs for existing s9y blog
> > entries, since a Smarty cached page still uses a thin PHP layer to
> > serve up the static HTML. Could be dealt with by Apache redirection,
> > internal trickery, or simply breaking old links.
> I can't follow you. Where's the problem? Please explain.
> > I'm no Smarty expert, though I've used it in enough projects to have a
> > good idea how to proceed. But I've only had a cursory glance at the
> > s9y code sofar. Maybe there are other complications.
> Same for me (except for the cursory glance at the s9y code ;), so, any
> real smarty experts around?