Tabs and styling

Looks fine! Nice how all the non-biblio-entry stuff moves out of the way :-)
Talking about design, would you consider to put a div with a common class around every year or every letter ot every type? Like

<div class="new_year"> // or whatever
<div class="biblio_year">2008</div>
... all 2008 papers
</div>
<div class="new_year"> 
<div class="biblio_year">2007</div>

This would allow to style every year into a collapsible fieldset where you could uncollapsed every year to see its papers.

This is off topic for here ;-) Just came into my mind whenI saw the png :-)

This is pretty cool, thanks a lot!

While trying this I'm having problems getting the sort tabs to show correctly. The biblio-header div needs a class="clear-block" to break the two float:left settings from the ul stuff. Otherwise the first separator bar and the sort links overlay each other. Adding the clear-block class solves this.

This is a general problem, the moment I installed the new -dev this problem showed up. As far as I understand it can depend on surrounding divs. We use a style where the main page sections are ordered using floats, and then inner floats can do such things. I've learnin from w3schools etc. that in general every element that uses floating should be surrounded by some other element having a "clear:both" or, in Drupal, a "class='clear-block'".

About the fieldsets (maybe we should change the topic or use a different thread :-)) it is possible to do with a jquery function, but it is not as nice as I thought because you need to fetch the text from the separator-bar and put that into the legend etc.
I will set up a demo how it looks with fieldsets. And if you like that we could think about a different approach, e.g. a option in the biblio settings like "Use fieldsets for category sections". And if that's checked, biblio could just produce different code, i.e.

<fieldset class="collapsible collapsed biblio-fieldset">
<legend class="biblio-separator-bar">2009</legend>
<div>
.. all the publications
</div>
</fieldset>

With such a code we just need to add collapse.js and the stuff automatically turns into fieldsets which can be styled (due to the classes in fieldset and legend) to anything you like. And everyone could decideif or if not to use fieldsets.

Give some time to set it up at our server.

Ok, take a look at http://naur.bio.ifi.lmu.de/publications (you can also see the problem with the floats there).

This is a quick hack, i.e. I added the fieldset code in biblio.pages.inc and instead of using a jquery function I took our body filter which converts fieldsets into collapsible ones. That's because it is much more efficient to use a filter instead of a jquery function because the server is usually faster than the jquery stuff on a client.

So this is just to show how it could look like. It's only implemented for sort-by-year. It should not be applied if the user did a search or has selected a filter I guess.

Don't wonder if you look at the code: I've made biblio.pages inc produce the code as listed above. But our filter turns all fieldsets into a different format without a legend but a preceding div an anchor with the same classes. That's due to styling issues with fieldsets and IE vs. Opera vs. FF. It's just not possible to have that grey background bar with all three browsers when styling a legend. But that's completely unrelated to the fieldsets in general. When adding collapse.js instead of using our filter, they would look like normal fieldsets (not very nice here, so I didn't use this :-))

I think that using graphics is always difficult to handle :'-( Even if you get the background done, curved tabs may look strange in a theme that is only using cornered tabs...

About the fieldsets let me know if you are interested in a first try for patch. I'm thinking of per-sort options, i.e. let the user chose if fieldsets should be generated for sort-by-year but not by-title etc. There should be an option to disable fieldsets when filters/search are active. And one to chose if fieldsets should be disabled for inline/profile views. Plus a keyword for biblio_db_search to active or deactivate them. I would take approach to generate fieldset-code and re-using collapse.js instead of using an additional similar jQuery function.

Doing all this carefully would take some time, so let me know if you are interested. Personally, I don't need all of this, I can use the current DIVs (as long as you mark the closing div the way you do now, otherwise my preg_match wouldn't be able to find the ending div anymore :-)), so I'm happy. But I wouldn't mind to create the patch for others.

Ok!