kde-www module

[Jason Bainbridge]

>one more note: no hardcoding of stuff like >http://usablity.kde.org as baseref, 
>as that will break the page on all mirrors, to include >common stuff out of 
>/images or /styles just assume that it is located in >the server root, that 
>should be easy to accomplish.

That's exactly how it was in the first place when it I think it was yourself that suggested we don't do that and instead have a file where $basehref can be defined for each site. Now you want the opposite?

>One thing that is a problem is the start dir of the >menu.inc stuff, hardcode 
>there any documentroot stuff in the subpages is bad, as >breaks mirroring, 
>too. perhaps use relative dirs there, too.

The document_root is set in one place, I don't think it is much of an issue for a mirror site to update one tiny file as part of their cron job to refresh the site.

>At all, I want to get rid of any hardcoded url, dir, ...

I don't think defining variables in a single configuration file and then using those variables throughout the codebase would constitute hardcoding...

>If we design that whole stuff from scratch at least >that should be possible, 
>or does kdebase need to be located in >/usr/src/kde3.2/.... to be compiled ?

Uhm what about $KDEDIR and ./configure --prefix= ? 

Regards,
Jason