Hi Bob,

On Thu, 27 Mar 2003, Bob Woodside wrote:

>       Actually, your server's order wouldn't be a
> problem. I'd call the home page index.php.

Should be done by this mail has been sent.

>       I just grabbed your latest tarball, and will take a
> look at it shortly. The first security issue, as I've
> mentioned before, is that we need to modify the code to
> work with PHP 4 with register_globals set to off (which
> I'm sure is what Jason installed). But we want to modify
> it so it'll be backward compatible with your PHP 3
> system. 

I think we should develop for the target system not for my
system at home. I figured out that at the university's
server php 4 is running. 

http://www-user.tu-chemnitz.de/~uwp/fvwm-web/php_info.php

I will switch to php 4 at home as well.

> I'll hack up a test page and send it to you a little
> later; try it out and let me know whether it works OK on
> your system.

So you need not to do that.

>       As for merging the new files with the existing
> fvwm-web, we want to be sure there aren't any
> subdirectory clashes.

Yes, you are right.

> For example, there is a "screenshots" directory in both
> your new set and in the old fvwm-web, and they're
> different things. In the tarball I pulled down, there is
> only your new stuff. Is it your intent that I should be
> able to merge this with my existing (copy of) fvwm-web?

Yes the screenshot subdirectory was an accident :-) We might
switch to screen_shot.

>       Ah, that reminds me...what are the implications for
> running navgen in a merged directory? (That one also
> appears to have some PHP 3/4 incompatibilities that I
> haven't had time to research thoroughly yet.)

nagven.php looks recursively for files having a .php
extension and includes them. It extracts the variable
settings in the header of the php-files, does some
consistency checks and stores the contents of the variables
in the file navgen_write/navigation.inc. On my server at
home the apacher server has the permission to write into
this directory. I would suggest to do not allow this on
fvwm.org since a writeable directoy is potentially a
security issue.

> > How about the actual colors and window decoration? Bob
> > meant the colors should be changed a little bit. Any other
> > suggestions?
> 
>       Mainly for the pager background. I think something
> a bit lighter than that grey would give some needed
> contrast - possibly a light cream color.

You can try different colors on your own by specifying them
in the url like:

http://localhost/uwe/fvwm_web_site/?pager_bg=%23ffff66

Please note that this variable is not passed through links
to other pages. Other possible changes to the actual layout
and their default value are:

if(!isset($decoration_path))  
$decoration_path=$rel_path."/decorations/window_deco_simple_blue";
if(!isset($window_border_bg)) $window_border_bg="#c5cecd";
if(!isset($window_border_fg)) $window_border_fg="#ffffff";
if(!isset($window_bg))        $window_bg="#000000";
if(!isset($window_fg))        $window_fg="#ffffff";
if(!isset($body_bg))          $body_bg="#000000";
if(!isset($body_fg))          $body_fg="#ffffff";
if(!isset($body_bg_image))    
$body_bg_image=$rel_path."/pictures/Totally-New-Product-1.jpg";
if(!isset($menu_bg))          $menu_bg="#c5cecd";
if(!isset($menu_fg))          $menu_fg="#000000";
if(!isset($windowlist_bg))    $windowlist_bg="#c5cecd";
if(!isset($windowlist_fg))    $windowlist_fg="#000000";
if(!isset($pager_bg))         $pager_bg="#b5bebd";
if(!isset($pager_fg))         $pager_fg="#000000";
if(!isset($hilight_bg))       $hilight_bg="#1a6e99";
if(!isset($hilight_fg))       $hilight_fg="#ffffff";

For example to change the background image using a file on
the local machine one could use:

http://localhost/uwe/fvwm_web_site/?body_bg_image=file:/home/uwe/pictures/azure.jpg

Uwe
-- 
+----------------------------------------------
| Uwe Pross
|    mailto:[EMAIL PROTECTED]
|    http://www.tu-chemnitz.de/~uwp
+----------------------------------------------
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to