A few thoughts on extending the existent events module. The target is a consistent, modular, and flexible scheduling add-on to drupal. Probably best implemented as a set of modules. The rough specs below are adventurous and probably over the top. I'll try and knock together some demo code, by refactoring the existing event + some additional code as a proof of concept.
I've created this Drupal module to consolidate and add missing feeds into a single place. This module includes the following protocols: RSS 1.0 (rdf), RSS 2.0, Atom 0.3. It does not try to replace the existing RSS 0.92 feed that exists in Drupal core. This module is based on the atom module.
There is a new flexinode field type which allows users to choose a color from a color table. The code for the color table was modified from HTMLArea.module. It is in the modules/flexinode/contrib directory in CVS.
Ive looked around the site, read documents, ect. Still can't find a simple answer to my questions.
What is a node?
How do you get a certain function executed in code? I see all the name_hook commands and what not, but how does that get called? IE: What does http://drupal.org/project/issues/3202 cause to execute?