RE: [PEAR-CVS] cvs: pearweb /public_html package-search.php /public_html/gifs calendar.gif tri-back.gif tri.gif /public_html/javascript/calendar
calendar.css calendar.js /public_html/javascript/xbApi xbApi.common.js xbApi.dom.js xbApi.ie.js xbApi.loade
| From: | Richard Heyes | Date: | Mon, 27 May 2002 09:22:50 +0000 |
| Subject: | RE: [PEAR-CVS] cvs: pearweb /public_html package-search.php /public_html/gifs calendar.gif tri-back.gif tri.gif /public_html/javascript/calendar calendar.css calendar.js /public_html/javascript/xbApi xbApi.common.js xbApi.dom.js xbApi.ie.js xbApi.loade |
||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-6461@lists.php.net to get a copy of this message | ||
> Wouldn't it be better to move package-search.html back into
> package-search.php? From my point of view it doesn't make much sense
> to split this up.
Templates are the way to go imho. It certainly makes the code easier to
read and maintain.
> Apart from that we should really consider to not use <?foreach($foo as
> $bar):?>
> and friends, since pear.php.net is our showcase and it should show people
> how to write clean code.
Pearweb is far from showcase code, and to be honest I think the use of templates
is a step towards this. I don't think there's anything wrong with short tags
and alternative syntax, as it makes the "template" much easier to read. Neither
are on the way out, so it's not "bad" coding as such, though when mirror sites
start appearing they will probably need to be made aware they need short tags
enabled (though it does default to on...).
> BTW: The calendar thingie is simply cool :-).
Thanks. :) Wrt Opera, I've no idea. I've not used it extensively so I'm not sure
as to what it supports. I'll have a browse on the Opera site and see.
--
Richard Heyes
Need webmail? http://www.v-webmail.co.uk