Some more infos about my change

[Jason Bainbridge]

This sounds quite good to me, I will have to have a look at it over the weekend and see how it all fits together.

It's good communicating details like this as it gives us all an understanding about what each of us are doing and  helps everyone see the bigger picture.

I think we are again getting to the stage of having some momentum behind our efforts and I want to see it continue so I will be doing what I can to accomodate this. I had taken a step back over the last day or so to freshen myself and again be able to approach this project in the right frame of mind.

Now that we have the kde-www module I'd like to see that we co-ordinate things better and that means through this mailing list, so if there are any interested parties that anyone knows about that aren't subscribed to kde-www can you please let them know? The IRC chats are useful but no decisions should be made during them as not all interested parties can attend, IRC should be more about discussing the various options available and then they can be decided upon through the mailing list.

So before anyone commits any major kind of changes to CVS to do with the common files please post to this list so your changes can be discussed beforehand.

What does everyone think?

Regards,
Jason

-----Original Message-----
From: Christoph Cullmann <cullmann at babylon2k.de>
To: kde-www at mail.kde.org
Date: Thu, 17 Oct 2002 16:08:28 +0200 
Subject: Some more infos about my change

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
perhaps some more infos about my changes will make things more clear.
(Have made some more stuff to fullfill the multiple server location stuff even 
better)

1.) All menus of a app/area page are relative to it's root, which means you 
can
 a) put any of the apps/areas on a seperate server, will work
 b) put all the stuff on one server for mirroring/testing, will work

2.) Links between areas/apps pages (like the links in family.inc) should use 
the new (and not finished) kde_links ($site, $page) function. This function 
wants to get something like kde_links ("/areas/usability", "/index.php") and 
will look in the array (defined in config.inc which is THE ONLY file a mirror 
must change) where the real page is located (for testing I have entered 
"/areas/usability" which looks like a no-brainer, but you can say that it 
points to usability.kde.org there with one line.

Again some stuff we win:
 a) if for example usability.kde.org goes down, change one line in config.inc 
and you can set it up on what know I for example "http://www.lalala.org" and 
all links in whole cvs will match

b) you can even costumize where on your server is the /styles and /images dir 
located via changing the stuff in config.inc (which will be a good thing for 
pages hosted only on a virtual server, there is no need to copy the stuff 
around, simply point that urls to the real server styles/, images/) 

c) the whole cvs module will be able to run on one server without setting up 
subdomains at all just fine

Is that more fine with everybody ?
The relative menu stuff is quiet hacky and the kde_links functions far from 
completion (it should be more clever to look if somebody forgot the / 
somewhere), but in the end, it works at least here fine. It's not that I want 
to break something, but to have only one central config.inc to modifiy and 
one php include dir to set is in my eyes just nicer to get the page up 
running somewhere. Could somebody look at my stuff and point out problems 
which may still arise with it ?

cu
Christoph

- -- 
Christoph Cullmann
Kate/KDE developer
cullmann at kde.org
http://kate.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE9rsRgyPjDGePm9UIRAlhkAKCBpRYPWAEqW/1HV9UU5In9esjUWQCgxt+A
G1kJ71eFZwyQMN/vm2bYtIs=
=YD7b
-----END PGP SIGNATURE-----

_______________________________________________
kde-www mailing list
kde-www at mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-www