[snip]
In src/*.php we'll have such calls :
foo.php : <?php include 'themes/' . $skin . '/foo.php';
before_head(); // some code head();
...
?>
that might not be flexible enough in practice (but is still better than what we have currently!).
I'm thinking of a situation where someone might want to render the header at the bottom, or on the right hand side of the main content, or do something else a bit strange.
thas one could use the CSS power :)
Performance wise, it might be better for the template to request only the parts it needs:
// returns node names and captions for sibling nodes // (based on toc structure) for the named node // $node = "function.fopen" as used by the search stuff. $contents = livedocs_get_siblings($node);
// returns navigation information in the form of // node names and captions for Next, Prev, and Up // links, based on the named node $nav = livedocs_get_navigation($node);
erm, I forgot this part when replying to Gabor :/
I now think we better go on forgetting the templating part.. from the new eye seight, we can manage to get this customized with some plugins..
Other functions could do such things as fetching the raw XML, fetching the HTML rendition of the XML using the default (very clean) CSS attributed XML->HTML converter; most templates shouldn't need to do anything to that if all they need is HTML.
agreed !
Using these things as building blocks, we can leave template authors to do pretty much anything they want.
s/template/plugin sounds just good :)
didou
