On 22-Apr-05, at 3:11 AM, Gerhard Killesreiter wrote:
I think it's a big problem to depend on it. Flexinode is incredibly complex for what we are trying to do. Most of the sites we develop don't use flexinode, and until some form of node caching is in core, I don't believe we should depend on it for functionality like that.
Boris mailed me about this "problem". I really do not want to re-introduce a new (old) event type. If Bryght wants to have a simple module for events I suggest treating story.module with sed -e 's/story/basicevent/g'. We could put the result into a subdirectory of event module.
It's not quite the same as story. It would have the location field, just like the existing event module, and be "event-enabled" by default. And it's not just Bryght....I'm thinking about all the users out there right now that have the event module installed, and don't use flexinode today (never mind any arguments about the complexity of flexinode -- theming it, and so on). Even with CCK, I can see the utility of having a pre-defined "basic" event type. For instance, we'll likely add some other views to it, like a tabular view of an entire year's worth of events (which is something that has been oft requested). -- Boris Mann http://www.bryght.com Vancouver 778-896-2747 / San Francisco 415-367-3595 IM boris_mann@jabber.org / SKYPE borismann