Re: [ANNOUNCEMENT] HTML_TreeMenu-1.0 (stable)Released.
| From: | Brent Cook | Date: | Mon, 17 Jun 2002 15:57:46 +0000 |
| Subject: | Re: [ANNOUNCEMENT] HTML_TreeMenu-1.0 (stable)Released. | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-7141@lists.php.net to get a copy of this message | ||
On Mon, 17 Jun 2002, Richard Heyes wrote:
> Michael Dransfield <mike@blueroot.net> wrote:
>
> > Personally I think that using DHTML in PEAR exts is not a problem
> > _as_long_as_ people write it for MODERN browsers (eg v.5+). It should
> > DEGRADE for other browsers, showing the same information and still allowing
>
> > browsing of the site. TreeMenu can degrade by showing all of the trees
> > open by default. If someone decides to extend the class later on so that
> > it 'works' in NS4 then good for them, personally I dont concider rewriting
>
> > everything else again worthwile just for the 0.01% of the _public_ that
> > actually uses the bloody thing.
> >
> > I think that we should say that any DHTML being contributed to PEAR should
>
> > work on all modern browsers and degrade in text based ones... Thats not too
> > hard is it?
Don't forget; links v2 (a text-mode browser) has javascript too ;). I'm
personally more in-favor of server-side menus, but that's why there's a
choice. That said, the name TreeMenu doesn't really convey what this is; a
functionally equivalent TreeMenu could exist without the use of DHTML. So,
why not call this HTML_JSMenu, or DHTML_Menu or somesuch thing. It's not
really HTML that is the magic word here. Just a suggestion.
- Brent