[PHPiCalendar-DEV] Re: XHTML and "big" features

[Chad <ch...@ch...>]

Hi all -
I've never understood how a template system would work this since its a  
calendar. The php code draws the calendar. You can work on it if you  
like but its not going into the project until after 1.0. I don't want  
to make these kinds of big changes until the calendar parser and  
underlying code is running 100% or better, and quite frankly it is not.

Secondly, I've seen zero evidence of people wanting templates. A  
templating system is merely a solution looking for a problem. We've  
provided a means to fairly easily allow 'regular guys' to change the  
look of their calendars with headers, footers, and style sheets. Yet  
99% of the installations take use of the provided themes. Noone has  
even submitted their theme back to us!

Our way is easy, I've looked at smarty and how projects like PHPBB do  
themes and it loses me. True there can be even more separation of code  
and display, which is what we should be looking at.

XHTML: I guess I'm missing what the point is. The only reason to recode  
the entire project would have to be that there is a great benefit from  
what XHTML offers. Noone has pointed out what that was or why we should  
switch. Is ditching 4.0 Browser users worth it? Apple still ships  
Netscape 4.7 on every single Mac today.

http://phpicalendar.sourceforge.net/nuke/ 
modules.php?name=Surveys&op=results&pollID=4&mode=&order=&thold=

These are the things our users want. Multi-User support, Multi-Calendar  
Support, Optional SQL support, and editing calendars.

The parser is slow. Needs to be faster. Needs to be a program. It  
should morph into a global class.
$phpical->getdate(20021123);
$phpical->gettodos

Although the above is something Jared and I have been talking about. If  
something like that existed, templates and everything else would be  
much simpler.

Ok, so I've rambled on a bit. I've needed to point out my views on many  
of the emails floating around here. Seems like every so often a big  
swell of interest comes and thats very very good. I just would like us  
more focused on getting to 1.0 before trying to re-invent the calendar.  
I think most of you will agree. I am still interested in seeing  
examples. Of course Jared's opinion counts as much as mine does, its a  
good bit his project too.

Cheers,
C


On Saturday, November 23, 2002, at 08:49  AM, Ed Finkler wrote:

> 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
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel