FreeLists / haiku-web / [haiku-web] Re: Trac (reevaluated)

[Waldemar Kornewald <wkornew@xxxxxxx>]

Mikael Jansson (mailing lists) wrote:
> Since changing the model of components in Trac would take too long
> time, I propose the following: If we store the components as e.g.
> "drivers/audio/ac97", split them up by "/" to get separate lists, fill
> Javascript arrays with the values plus some Javascript code that would
> automatically change the value of the "lower-level" HTML SELECT with
> the values underneath. This way, you'd first select "drivers" in the
> first SELECT, upon which the second SELECT's contents would change
> (listing all drivers). Select "audio" and in the third you can now
> select "ac97".  The exact way to show it to the user isn't very
> important -- for example, you could do it with nested <UL>s and some
> CSS/Javascript to display a popup menu which would degrade nicely in
> non-Javascript/CSS-capable browsers.
>
> The general idea though, what do you think?

Could we please move this to the end of our task list? I'd rather do the first
tests with simple one-level categories before starting with
over-categorization. Didn't you warn me about over-categorizing and 
blowing the
website? Your words were "start with the bare minimum". Let's do this 
with Trac,
too.

Bye,
Waldemar Kornewald


-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List