Hi,
> I wanted to try out bweb. It turned out to be a bit frustrating at first
> because of the fixed names for the CGI scripts and fixed path for the
> static resources. I don't think it's very friendly to force the user to
> use the same names for stuff (.pl ending for the scripts and hard-coded
> /bweb path for the resources) as the developer is using. Instead, IMHO,
> it should be configurable with defaults behaving just like the existing
> things do. So after a bit of poking around the source, now I've got bweb
> installation I like. Description of the patches follow. Feel free to use
> them if you like or ask any questions.
IMHO, if you want to change all .pl files to .cgi, you can simply do :
sed -i 's:\.pl:.cgi:g' cgi/* html/* lib/* tpl/*
And if /bweb or /cgi-bin/bweb isn't good for you
sed -i "s:'/bweb/:'/newpath/:g" tpl/* lib/* cgi/*
sed -i "s:/cgi-bin/bweb:/pathtocgi/bweb/foo:g' tpl/* lib/* cgi/*
It a lot more simple, isn't it ?
> By the way, I think current localization scheme doesn't scale at all
> (having copies of all the templates for all the supported languages).
> One might try to improve the situation by externalizing all the strings
> to HTML::Template variables and then translate them using Locale::PO or
> something similar so you wouldn't have to update N templates when you
> have to change the layout...
Yes, i have ideas to fix that, i think that i will use something like
_("string to adapt") in the main tpl file, then i will use a script to
generate all tpl versions.
Thanks for your feedback.
Bye
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
