Have session schedule list days on tabs

working on a solution to this. Trying out 2 possible workaround:
- URLs for tabs to follow program/schedule/[date]
- use jquery for horizontal tabbing

this seems like a related issue - http://drupal.org/node/1379382

Not a fan of having additional urls here, nor am I a proponent of trying to do something 'weird' with a field_group implementation.

jquery.ui in core makes me lean towards using the ui.tabs. Here is a rudimentary patch that does this:

Using hook_init in the .module to invoke the ui.tabs and throw in some dirty js. This seems to be common practice for UI tabs implementations but I'm not opposed to adding a cod_session.js file to the Feature - I think this is cleaner, personally.

I also modified cod-session-schedule.tpl.php to add anchor links for the tabs and appropriate div wrappers to make this work.

The patch applied cleanly. I think this solution is the simplest.

I also applied the patch cleanly, and the functionality works well. Please note that I had to clear the cache before the changes appeared.

Regarding the idea of adding a cod_session.js - I'm not familiar with the best practice for this kind of thing. Maybe others have some input?

I've attached a screenshot for those who are curious how this looks.

Got this working as well. Same issue I had with #1673018: Speaker confirmation shows incorrectly, add cod_session helper functions, update flag node title token. I had to apply the patch for entityreference in order to enable cod_session on my end. To have it working, I changed all instances of field_session_slot to field_session_time_slot and 'nid' to 'target_id' in template_preprocess_cod_session_schedule. References module has both node_reference and user_reference module.

Also working on my end..need to clear cache so the patch will effect... this is good to go..

Patch is clean and the tabs look good. But, I realized today that if we add more than 3-4 rooms to a time slot, the table starts to crunch together awkwardly.

DrupalCon sites store information on many rooms, so we use a themed list rather than a table. The list is organized by time slot, and each day lives in a different tab. See http://munich2012.drupal.org/program/schedule or the second image attachment below.

Tagging.

+1 for theme list

#2 Additional URLs are valuable for multi-day events when you have primary navigation to the schedule that you want to stay current as the event progresses and you don't want to lose the ability for people to navigate to past days. For DrupalCon Denver I did this by swapping the schedule Wednesday page to be the default menu tab for /program/schedule on Tuesday night. People could still navigate back to Tuesday's schedule but the landing page was up-to-date.

You could JS switch based on a URL fragment for the day but Drupal core's support for that in menu links has been poor.

JS tabs does have the benefit of making it really fast to look at content between days since the content is already local tho.

Not sure what brantwynn mean's by "something 'weird' with a field_group implementation" for the tabs. You can use filters on the View pages to limit the schedule to single days.

@coltrane Yes, I was talking about using a Field group filter in Views. The 'something weird' would probably involve rendering multiple Views - each in its own quicktab or something along those lines. Anyway- not a good idea just a digression.

I very much like the idea of having multiple URLs that can drive the 'default' tab. I imagine it would work something like:

/program/schedule - default tab is either the first tab or possibly 'Today' (like in the case of Denver in #11)
/program/schedule/[date] - default to the correct date tab if it matches the URL request

This could probably be pulled off on the theme layer. Does anyone else have an opinion on this?

I very much like the idea of having multiple URLs that can drive the 'default' tab. I imagine it would work something like:
[snip]
This could probably be pulled off on the theme layer. Does anyone else have an opinion on this?

These tabs need to persist across themes, be accessible for screen readers, and degrade gracefully when JS isn't enabled which means this should be in the module layer.

I agree that the tabs should have dedicated URLs and that Quicktabs module could be a good way to implement this.

Updating the default tab based on the day automatically would be awesome, but is a "nice to have" in my view.

I think we should consider merging this issue with #1379382: Single column session schedule to simplify working towards the goal here: Providing a vertical schedule view with tabs for each day.

Ok - closing this and moving to #1379382: Single column session schedule

Added URL scheme