Posted by drob on September 23, 2006 at 8:46am
Here is a draft of my latest pass at an Events 2.0 document. Published for the presentation at DrupalCon '06.
| Attachment | Size |
|---|---|
| EventsSpec_v2.0.pdf | 448 KB |
Revised Event Spec
Here is a draft of my latest pass at an Events 2.0 document. Published for the presentation at DrupalCon '06.
| Attachment | Size |
|---|---|
| EventsSpec_v2.0.pdf | 448 KB |
Comments
Great
First of all: Good job!
Events API shouldn't provide functions that are already provided by other modules. You mentioned Location module, but IMO SimpleNews can be leveraged for Event Emails (Updates/Cancellation Notices/Archive/Tracking) and Invite API can be used for invitations, forwarding/recommendation and tracking of recommendations.
Daniel F. Kudwien
unleashed mind
Daniel F. Kudwien
netzstrategen
Right On
Yup - you are correct - the approach should leverage existing work. I am somewhat familiar with the SimpleNews module and not very familiar with the Invite API - but I'll look at them and integrate as appropriate. Your continued oversite and participation is much apreciated.
Events DEP
Are you also involved with the Events DEP at Drupal.org? Or is your approach a different one?
I'd like to help out where I can. If there's something to test, a conceptional/executive task force to hook in or a concrete development task for Events API/contribs let me know, please. I haven't found out where you Event guys are joining forces yet. Groups seem to be a good discussion board, the DEP a documentation what's been done so far but I don't get the missing link to the actual (concrete) task board telling me what questions have to be discussed, what code can already be written and so on.
Daniel F. Kudwien
unleashed mind
Daniel F. Kudwien
netzstrategen
Help is good
It has been my intention to "bring together" all these conversations. The DEP pre-dates groups.drupal.org and my understanding is that we're now using this forum to coordinate activities. I went through the DEP in detail when preparing my original documents and attempted to capture all the detail I could there. Our team (CivicActions) is actually implemnting some of this spec this week for a client. Once we have the output of that work we'll be publishing it. If there are pieces you would like to work on the best thing to do is to claim a piece and bang out some code. My conception is that the tasks can be derived from the document I've published.
Some further info
Simplenews is not a general purpose mail API - it specifically does simple (hence the name) broadcast-only mailing lists.
The Send module is one to look at further (although it is intertwined with CiviCRM somewhat), and the invite module might be examined for more info. Both Send and Invite are mentioned here: http://drupal.org/node/54947
That is my understanding
We've used Send extensively and while it still needs some work it is a very nice bit of functionality. Invite is on the list as well. I need to put the notes from our Events presentation at DrupalCon on-line since it touches on these modules. The document so far has been devoid of implementation details on purpose.
Would it make any sense to
Would it make any sense to use the date module api for some of this? Date.inc was designed to function as an api which creates a date object that has a database and local version of the time, can handle both ISO and timestamp date storage, includes an array of selectors and the logic to convert the selector input back into the right data, has lots of functions to do sql queries, convert dates from one format to another, format the output, etc. Date.module then uses cck to store and retrieve the date using the api.
Don't know if this makes sense within events or not, but it is another available api.
You are talking about the Date field in CCK yes?
I'm assuming that is what you mean. It has been assumed that the Date field in the CCK would be the basic building block for this version of Events.
Yes, the CCK date field. I
Yes, the CCK date field. I didn't realize that was already assumed, sounds good to me :-)