Hi,
would it be possible to use PNG for logo in HTML manual pages
instead of GIF? That only means to convert the logo
and modify Html.make.
Qt is not compiled with GIF support by default because of
patent problems.
Thanks
Radim
On Fri, Sep 22, 2006 at 02:25:42PM +0200, Radim Blazek wrote:
Hi,
would it be possible to use PNG for logo in HTML manual pages
instead of GIF? That only means to convert the logo
and modify Html.make.
Many more files were affected, but done.
Qt is not compiled with GIF support by default because of
patent problems.
AFAIK the patent is expired. Anyway, PNG is fine
and now used.
Markus
Markus Neteler wrote:
> would it be possible to use PNG for logo in HTML manual pages
> instead of GIF? That only means to convert the logo
> and modify Html.make.Many more files were affected, but done.
> Qt is not compiled with GIF support by default because of
> patent problems.AFAIK the patent is expired. Anyway, PNG is fine
and now used.
For the record, TclTk doesn't like PNG. e.g. the NVIZ help browser won't
load PNG help graphics in the nviz man pages. I consider the fix for
this to be dropping that help browser altogether & in general dropping
tcltk...
Hamish
Hamish wrote on 09/27/2006 12:36 PM:
Markus Neteler wrote:
would it be possible to use PNG for logo in HTML manual pages
instead of GIF? That only means to convert the logo
and modify Html.make.
Many more files were affected, but done.
Qt is not compiled with GIF support by default because of
patent problems.
AFAIK the patent is expired. Anyway, PNG is fine
and now used.
For the record, TclTk doesn't like PNG. e.g. the NVIZ help browser won't
load PNG help graphics in the nviz man pages.
Cool 
We should change the NVIZ help browser to the standard HTML browser. The
limited
tcltk based browser isn't that fancy at all.
I consider the fix for
this to be dropping that help browser altogether
yes. The code could be taken from
gis.m -> Help -> GRASS help.
It also needs to be updated in the startup GUI.
& in general dropping tcltk...
This will take some more time.
Markus
On Wed, Sep 27, 2006 at 05:47:01PM +0200, Markus Neteler wrote:
Hamish wrote on 09/27/2006 12:36 PM:
> For the record, TclTk doesn't like PNG. e.g. the NVIZ help browser won't
> load PNG help graphics in the nviz man pages.Cool
We should change the NVIZ help browser to the standard HTML browser. The
limited tcltk based browser isn't that fancy at all.> I consider the fix for
> this to be dropping that help browser altogetheryes. The code could be taken from
gis.m -> Help -> GRASS help.It also needs to be updated in the startup GUI.
Done (startup GUI) & done (nviz). Also for 6.2-release branch.
Any other places?
Please test...
Markus
> > For the record, TclTk doesn't like PNG. e.g. the NVIZ help browser
> > won't load PNG help graphics in the nviz man pages.
>
> Cool
> We should change the NVIZ help browser to the standard HTML browser.
> The limited tcltk based browser isn't that fancy at all.
..
Done (startup GUI) & done (nviz). Also for 6.2-release branch.
Any other places?
$ grep -rI help.tcl * | grep -v locale/po | cut -f1 -d: | uniq
No, only those two used it.
If we remove GRASS's visualization/nviz/html/help.tcl web browser,
that's 120k less source to distribute!
Please test...
with this set in ~/.grass.bashrc:
export GRASS_HTML_BROWSER=dillo
it works fine from NVIZ, but the startup GUI defaults to using klunky
old mozilla as .grass.bashrc hasn't been sourced yet(?). Also is there
any way to get rid of or minimize the residual xterm window?
Hamish
On Mon, Oct 02, 2006 at 03:26:50PM +1300, Hamish wrote:
> > > For the record, TclTk doesn't like PNG. e.g. the NVIZ help browser
> > > won't load PNG help graphics in the nviz man pages.
> >
> > Cool
> > We should change the NVIZ help browser to the standard HTML browser.
> > The limited tcltk based browser isn't that fancy at all.
..
> Done (startup GUI) & done (nviz). Also for 6.2-release branch.
> Any other places?$ grep -rI help.tcl * | grep -v locale/po | cut -f1 -d: | uniq
No, only those two used it.
If we remove GRASS's visualization/nviz/html/help.tcl web browser,
that's 120k less source to distribute!
please go ahead 
> Please test...
with this set in ~/.grass.bashrc:
export GRASS_HTML_BROWSER=dillo
it works fine from NVIZ, but the startup GUI defaults to using klunky
old mozilla as .grass.bashrc hasn't been sourced yet(?). Also is there
any way to get rid of or minimize the residual xterm window?
I observed the same problem but have no idea.
Markus
Hamish wrote:
with this set in ~/.grass.bashrc:
export GRASS_HTML_BROWSER=dillo
it works fine from NVIZ, but the startup GUI defaults to using klunky
old mozilla as .grass.bashrc hasn't been sourced yet(?).
You can always set it in your normal ~/.bash_profile etc.
Also is there
any way to get rid of or minimize the residual xterm window?
Yes; just don't use an xterm, i.e. change:
exec -- $env(GISBASE)/etc/grass-xterm-wrapper -e $env(GRASS_HTML_BROWSER) \
file://$env(GISBASE)/docs/html/helptext.html >@stdout 2>@stderr &;
to:
exec -- $env(GRASS_HTML_BROWSER) \
file://$env(GISBASE)/docs/html/helptext.html >@stdout 2>@stderr &;
I don't see why an xterm should be necessary. If you want to use
lynx/links, you can set GRASS_HTML_BROWSER to a script which starts
lynx/links in an xterm, e.g.:
#!/bin/sh
exec xterm -e lynx "$@"
--
Glynn Clements <glynn@gclements.plus.com>
On Mon, Oct 02, 2006 at 07:53:48PM +0100, Glynn Clements wrote:
Hamish wrote:
> with this set in ~/.grass.bashrc:
> export GRASS_HTML_BROWSER=dillo
> it works fine from NVIZ, but the startup GUI defaults to using klunky
> old mozilla as .grass.bashrc hasn't been sourced yet(?).You can always set it in your normal ~/.bash_profile etc.
> Also is there
> any way to get rid of or minimize the residual xterm window?Yes; just don't use an xterm, i.e. change:
exec -- $env(GISBASE)/etc/grass-xterm-wrapper -e $env(GRASS_HTML_BROWSER) \
file://$env(GISBASE)/docs/html/helptext.html >@stdout 2>@stderr &;
to:
exec -- $env(GRASS_HTML_BROWSER) \
file://$env(GISBASE)/docs/html/helptext.html >@stdout 2>@stderr &;
thanks, fixed (also 6.2).
Markus
Glynn Clements wrote:
> with this set in ~/.grass.bashrc:
> export GRASS_HTML_BROWSER=dillo
> it works fine from NVIZ, but the startup GUI defaults to using
> klunky old mozilla as .grass.bashrc hasn't been sourced yet(?).You can always set it in your normal ~/.bash_profile etc.
well yes, but that's sloppy. my thought was: should ~/.grass.[*]rc be
processed earlier, perhaps even in bin.i686-pc-linux-gnu/grass63 ?
Hamish
Hamish wrote:
> > with this set in ~/.grass.bashrc:
> > export GRASS_HTML_BROWSER=dillo
> > it works fine from NVIZ, but the startup GUI defaults to using
> > klunky old mozilla as .grass.bashrc hasn't been sourced yet(?).
>
> You can always set it in your normal ~/.bash_profile etc.well yes, but that's sloppy. my thought was: should ~/.grass.[*]rc be
processed earlier,
~/.grass.*rc are sourced into the interactive session shell. If your
$SHELL is e.g. csh, you probably aren't going to have a
~/.grass.bashrc, and you aren't going to be able to source a
~/.grass.cshrc into a bash script such as Init.sh.
Even if your $SHELL is bash, ~/.grass.bashrc may contain commands
which don't make sense outside of an interactive shell.
perhaps even in bin.i686-pc-linux-gnu/grass63 ?
There wouldn't be any point. The grass63 script sets $GISBASE then
runs Init.sh; anything useful that could be done in grass63 can be
done equally well in Init.sh.
--
Glynn Clements <glynn@gclements.plus.com>