events

I have a mostly-working Views Calendar module available at http://www.drupal.org/project/calendar. It's still a little buggy and the css needs tweaking but it is generally working. Create a view and select the Calendar display (instead of table or teaser). Add any date field to the view (CCK dates, event dates, node updated dates, whatever). Add three arguments, Calendar: Year, Calendar: Month, and Calendar: Day.

Navigate to the view where you will see a year of mini calendars. Click on a month name to see the month or a day name to see the day. Back and next navigation is provided for month and day views (not yet added to the year view). It comes with a default calendar that displays all nodes in a calendar by their last updated dates. If you like, select the Calendar view for the block, too to get a mini calendar in a block.

At the Events 2.0 presentation DWW took notes during the session. Most of the presentation was to provide context for the Revised Event Spec – published here earlier.

Huge shout out to DWW for taking such detailed notes - I've gone through and tried to edit a bit so that people who were not there would have a little more context - DWW - if I've screwed something up please don't hesitate to point it out....

Drivers for Events 2.0 -

There is not a lot of functionality within the Drupal modules around Events.
Some of the modules don't “play well with others” and are not being maintained

Direction Forward:

CCK
Signup
RSVP
SendMail
Workflow
Actions

Here is a draft of my latest pass at an Events 2.0 document. Published for the presentation at DrupalCon '06.

Since part of the purpose of this group is to track views development, I thought I would share my solution for creating flexible date range arguments for the Date module.

Creating arguments for date fields is hard because there are so many possible ways people might want to use them. You may need to find a full date or a part of a date or you may want to look for a date + duration or maybe specify that the duration will start on the current date or some other date, etc. etc. In creating arguments for dates I have been finding that the list of arguments in views gets longer and longer, but no matter how many you create, someone will always come back and ask for another type of argument.

Does anybody know the status of major upgrades to the event module? I saw postings about a complete rewrite in recent months, to support dates prior to 1970, etc. Is that an active project?

I have been playing with the Timeline project from simile.mit.edu.
http://simile.mit.edu/timeline/

The Timeline project delivers a scrollable, DHTML timeline which is analogous to the Google Maps interface (as seen in GMap module) except this shows a timeline of nodes. This project is new and under active development, but working mostly.

The attached module requires views module. It provides 2 views plugins: Timeline Horizontal (works) and Timeline Vertical (does not work due to bug in Timeline project). It also provides the beginnings of an API of sorts, where you can programmatically make timelines. E.g. this function

Da sich vermutlich keine eigene Gruppe für die "LinuxWorldExpo Köln" rentiert, poste ich mal einen vorbereitenden Artikel hier auf der Germany-Group.

Und nun ersteinmal die Gretchenfrage: Gibt es bereits Ambitionen einen Stand im ORG-Pavillon aufzustellen?

Ein entsprechender Antrag ist über http://www.linuxworldexpo.de/linux_messe.php?ID=85&STEP=&lang=de hier http://www.linuxworldexpo.de/upload/lw06_orgpavilion_d.pdf zu bekommen.
Ich würde sonst einen entsprechenden Antrag vorbereiten.

Gretchenfrage Nummer 2: Hält jemand aus dem Drupal-Umfeld eine Keynote?

In my opinion, the use of timestamps for the representation of dates in Drupal core is problematic. It is fine for recording all events that happen now, and it is even fine for recording historical events, as long as they happened 1970 or later. They are utterly useless if you want to make a geneology site.

More disturbingly, the event module also relies on timestamps for representation of events. As far as I can tell, this is a huge limitation. The CCK date field uses the ISO 8601 standard which saves times as as string: 20060610T20:47:48+01:00. While there are lots of arguments about how the data should be persisted in the database, to me, it is clear that the ISO 8601 string is ideal for representing the date in Drupal code (unless you're doing archeology, then I've got no idea what you do with BC dates).

Another in the series of screens. This is a list of attendees - versions could be used for public, attendee and event organizers.

Here's a mock-up of an RSVP/Register Screen. Hopefully it isn't too busy. So the obvious question is how to use "Signup". The biggest issue is that I want to be able to use CiviCRM as the data store - anybody should be able to define their own data store. Signup has a nice "lightweight" store which is cool for lots of uses - but this may be too complicated?

Also looking at RSVP - but I dont' think there are CiviCRM hooks....