[Date Index][Thread Index]
[Date Prev][Date Next][Thread Prev][Thread Next]

Re: I like this navbar

On 8 Apr 1999, Florian Hars wrote:

> > Concerning the ``nohints'' attribute, it's a good idea. 
> [...]
> > wml_p8_htmlstrip to suppress JavaScript code. I prefer the latter, any
> > opinion?
> I might want to be able to suppress javascript hints on navbars, but
> still be able to use the image replacement (see the example below,
> navbar-FH actually produces different javascript code for nb_imgOver
> depending on nohints), to set hints on selected <href ...>s or to
> include hand-coded javascript stuff (http://www.hars.de/misz/rado.html
> uses javascript to supply a functionality that can't be achieved
> otherwise), this might be difficult to do with a global option to
> remove javascript code.

Yes, you're right. I've added a ``nohints'' attribute to navbar:render,
the http://www.engelschall.com/sw/wml/test/gimp shows the result.

> > And i don't understand what your ``imgstyle'' attribute is for. Do you
> > have an example?
> It is relevant for the automatic button creation, see
> http://www.hars.de/www/wml_nav_img.en.html for a description.  It is
> used like (real world applications should probably use PerlMagick or
> something instead of banner and netpbm):

Thanks for the explanations.
I think you should not mix button definition and image generation. 
You may define a tag to build your pictures, with the ``imgstyle''
attribute. Take a look at <wml::des::gfont>, it provides a ``notag''
attribute for writing images without generating <img> tag.

It's easier to debug and maintain. And in your template you can define
your own macros to generate image files and appropriate navbar


Website META Language (WML)                www.engelschall.com/sw/wml/
Official Support Mailing List                   sw-wml@engelschall.com
Automated List Manager                       majordomo@engelschall.com