Re: [Phpgroupware-developers] re: CSS support

[Andrea Iacoponi]

At 07.59 24/05/02 -0700, Dan wrote:
> Pim Snel wrote:
> >
> > What's wrong with linking to a separated css-file? Maybe create a
> > default directory called style. The path to the css-file can be set in
> > de theme-array so that the api can decide to put the Link-tag, or not
> > place it in case the user doesn't wan't to use css.
>
> Same thing is accomplished the way Im doing it now. However by having
> this array we can override css defs further down the chain as nessesary.
> Also, some browsers have problems mixing various css files + inline css.
>
> Its also very easy to do browser detection and preference check, then if
> one or the other decides css is a not welcome, then we can have the
> value in the templates class turn empty.
>
> Dan


I agree with Pim.
I also use separated CSS files and it works quite fine (at least on IE, 
Netscape, Mozilla and Konquerror)
Some problems may arise in overriding inline css.
At the moment I output dynamically the CSS linking instruction with the 
rest of the HTML page.
I think there should be no problems in using the same approach with the 
PHPGW API; it would greatly benefit readability of the code, keeping the 
same functionality  (i.e. loading a browser-safe CSS file if the browser is 
not fully compatible with CSS specs. )



       Andrea Iacoponi