Re: XHTML and "big" features was Re: [PHPiCalendar-DEV] $_GET variables

[Ed F. <co...@fu...>]

Greg Westin wrote:
> The problem, as I see it, is to make sure that we're not JUST writing
> perfect XHTML.  In other words, if we're really concerned about
> compatibility, we should be checking sites with something like Bobby to
> figure out potential problems.

Not a bad idea.  In the very least, people should be using the w3c 
validators more.

> The only problem I've ever had with XHTML is that Mozilla/5 (Netscape 6?)
> has a bug in it.  When it encounters a DOCTYPE declaration, positioning on
> the page can get messed up.  Luckily, this doesn't happen with earlier
> browsers, later versions of Netscape, or any other browsers I've found, so
> you can simply check for the browser and only deliver the DOCTYPE
> declaration if it doesn't have Mozilla/5 as it's user agent. (Or Gecko, I
> think).

Interesting... I've never run into this, and I run Mozilla (or its 
variants) pretty exclusively.

To bring this back to PHPiCalendar:

Personally, as I've said before, I think we should implement a 
templating system that removes markup entirely from the PHP code.  I 
didn't get much response from my early request for recommendations on 
which template class to use, so I'll do the following:

1) get the current CVS
2) pick a templating system
3) integrate the templating system into one page as a "proof of concept"
4) Let everybody take a look at it

If no one raises an objection, I'll try to work on that tonight or tomorrow.

-- 
"it's like an addiction to idiocy" -j
-Ed