-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Owen Leonard Sent: Wednesday, 31 August 2016 4:00 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Interface patterns (tabs)
Do you have any documentation for preferred use of jQuery tabs?
Hi David,
Sorry to have let your question hang for so long!
If I had to describe how tabs are generally used in Koha I would say that
are used to present distinct sub-categories of information about a thing in a way which conserves space. I consider the bibliographic detail page to be
best example.
There are other pages like members/pay.pl which use "static" tabs. These are tabs which look like jQueryUI tabs but are actually links to separate pages. That doesn't feel very consistent to me but it seems to work.
I realized I'd forgotten it when I looked again at Bug 12773 ("Branch
Hi Owen, No worries. I haven't been checking my koha-devel mail for a little while, so it's quite the coincidence I found your message today! I suppose I was looking for an established guideline or a recommendation, but I appreciate your input nonetheless and it does answer the question! That is a lot of collection codes! That does seem to suggest that a dropdown menu might be better than tabs for that interface, I guess? I'm working on an interface for the OAI-PMH import at the moment, and I'm unsure how best to group the content. I don't want to make a bunch of subpages for all the different tables, especially as some are related and thus one would want to be able to rapidly switch back and forth, but I'm not sure that tabs are the answer either. But at the moment they stretch down the page pretty far if there's a lot of data. Maybe I can use tabs to group together the most related information, and then maybe make another page for the most tangentially related content. Sort of like "Stage MARC for import" and "Staged MARC management". They're different enough to warrant separate pages, I suppose. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 they the transfer
limits show codes instead of descriptions (item types/collections)"). The transfer limits page uses tabs to allow for fast switching between
collection > code configurations. In my library's system the tabs get a little crazy: > > http://zivotdesign.com/p/#1/14725785555465 > > Of course we may simply have too many collection codes! I think the > screenshot is a strong hint that tabs are not the correct way to be handling > that interface. I would be interested to hear if anyone has other examples of > where a tabbed interface becomes unwieldy because of a large number of > generated tabs. > > David does that answer your question? > > -- Owen > > -- > Web Developer > Athens County Public Libraries > http://www.myacpl.org > _______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ bugs : http://bugs.koha-community.org/