Would anybody be interested in developing the Views Calendar project as outlined for the Summer of Code 2006 - http://drupal.org/node/58995

The resulting module needs to be available for 4.7, and 5.0 of Drupal.

If you can do it, for a fixed price, please contact me to discuss.

Comments

Bounty

Easiest way for you to do it is to announce a bounty and see how many developers that report being interested.

--
Jakob Persson
Drupal developer, web designer and usability consultant
http://www.jakob-persson.com

--
Jakob Persson - NodeOne

As I've not had time to

As I've not had time to actually look in to the amount of work required to produce such as module I didn't want to put anybody off by offering peanuts to people.

Currently I'm looking for a predicted cost to implement the Views Calendar which can be passed on to the client.

There is a views calendar in

There is a views calendar in the Event Views module that works for events, cck date fields, and node timestamp fields. There was a recent change to cck that broke the way that cck date fields work, but that will be fixed, and the calendar will be added to the cck date module, too, or at least made available for cck dates in one way or another (maybe as a separate module).

I planned to do this sooner or later anyway, but if someone is willing to fund the development, I can accelerate the process. My main problem is that I can only work on it parttime since I've committed most of my time to another project. However I have it very close to working, so it might still be possible in a fairly short timeframe. Contact me if you're interested.

I've been having a play with

I've been having a play with the Views Event/Calendar functionality from the event.module this afternoon. However that's not quite the same as the SoC module referenced earlier. This provides a calendar (like the Event module) to browse nodes created on that date. Like archive.module does.

--
Ixis (UK) providing Drupal consultancy and Drupal theme design.

I don't know if that's really what's useful

A calendar view for events would just be another view. It would only display events created on given dates if you put them in the view by their creation date (sorted by it?) If you instead decided to view them based on a date or datetime field, or by their last date of modification, then they would be displayed in that way instead - kind of like when you display a list view, you decide which fields to display, and then decide which to sort on.

Any calendar view that didn't let you display events by any date or datetime, not just the creation date, would not be worthy of being a views module. The best part is the criteria can come right from the sort order.

Really, breaking the calendar generation out of event and event_views and making it a views module would be absolutely brilliant even as is. Since event is not ready for 5.0 and won't be any time soon, but views is, a views calendar is mandatory for event.module-like functionality on 5.0, at least until the actual events module is ported.

On the other hand, a calendar view coupled with cck and views would make the events module obsolete as it currently stands; it seems to me like it would end up more an API for event-related modules if anything. The calendar is really the only meaningful thing provided by event that isn't provided by CCK plus the cck date module.

--
You are what you do when it counts.

I would chip in for a bounty

I don't know what progress has been made on your proposal, but if you are rounding up interested people for a bounty, I'd be willing to chip in, as this is something I am looking for as well.

If I read the description correctly, the aim is to have something similar to Joomla's JEvents extension, correct? http://www.jevents.net/index.php?option=com_events&task=view_month&year=...

---
David N
http://www.autoconcourse.com (coming soon)

Had a tight timeline so just

Had a tight timeline so just went with the standard event module now rather than using Views at all.

I noticed a work in progress Views Calendar module popped up in CVS the other day too.

events.module (for 4.7-) does that already

the idea is just to get the same functionality for non-event nodes, in fact for all nodes. nodes could be sorted (and displayed) by any date or datetime field so you could list them by creation date, modification date, an event start or stop date, or any cck date.module field. AFAIK event_views module only lists event nodes, although I could be wrong - in any case it requires event and event is not present for 5.0.

it would make more sense IMO to replace event completely with a calendar view module, CCK, and the date.module for CCK, because those modules would provide all of the same functionality we have now. event.module, if it even existed, would mostly provide views, menu items, and the like.

what I'd like to see would be event resource management in drupal - this would also be a nice piece of functionality for an event.module to provide. For instance, I am working on a drupal site for my employer that lists musical events for three different venues. I would like the event module to know that only one event can have a specific taxonomy term associated with it, during a given time slot, and throw an error if I have multiple events scheduled for the same slot. Optimally it would be able to tell the difference between published and unpublished events, so that an unpublished event wouldn't be checked for conflicts until you tried to publish it.

Not that any of it's up to me of course, but this would seem to make the most sense. The only functionality in the event module not yet provided by other modules is the calendar view and the other modules (views, cck) are pretty much staples of drupal.

--
You are what you do when it counts.

Advertising helps build a successful ecosystem around Drupal.
nobody click here