[sword-devel] Website - module lists

[Eeli Kaikkonen]

Maybe it was due to the server updates but this didn't come through and
I resend it now.

On Tue, 16 Dec 2008, Eeli Kaikkonen wrote:

> Quoting Peter von Kaehne <refdoc at gmx.net>:
>
> >
> > Our language list and module list becomes ever longer.
> >
> > Some info is poorly presented in the old one and I want to do it better
> > - but am not sure yet how to accomplish that/
> >
> > Language:af means little - Africaans would be nicer. How can I get there?
>
> By translating :) Every frontend has to do this if it wants to be user
> friendly. Could this be the time to gather one list into the CrossWire
> server where people could update and reuse it? It's quite stupid to
> duplicate the work for each frontend, especially when new languages
> come to the module list evey now and then.
>
> If nobody else gives some links before me, I'll find out where the
> translations in BibleTime come from. There are some authoritative
> lists in internet.
>
> >
> >
> > I never liked the internal module names as a presentation item, i think
> > the short description is much more useful for that. I think i would want
> > to drop the internal module name.
>
> The presentation is one thing, but don't drop. People are used to the
> short module names. It's very hard to get rid of them mentally.
>
> >
> > But there is more:
> >
> > What navigation would be efficient, robust and would bypass scrolling to
> > an ever expanding list?
> >
> > I am sure most frontend developers have the same problem.
> >
> > I am wondering about two drop downs - language and category
> >
> > If you choose nothing you get all
> >
> > If you choose English you get all English
> >
> > if you choose English and Bible you get only English Bibles
> >
> > Has anyone a better idea?
> >
>
> Have you tested BibleTime 1.7 betas? :) The modules can be sorted a
> little bit like this. You can choose "just modules",
> "language/modules", "category/modules", "category/language/modules",
> "language/category/modules". But they are all in the same tree, so
> it's not the same as filtering. Anyways, something like this would be
> very good. If we want to avoid javascript it's most probably some
> forms with dropdown lists.
>
> --Eeli Kaikkonen
>

  Yours,
	Eeli Kaikkonen (Mr.), Oulu, Finland
	e-mail: eekaikko at mailx.studentx.oulux.fix (with no x)