[Wpigdc-cms-development] Events classes checked in

[Liam M. <lm...@WP...>]

I love cygwin. I love vi. I HATE cygwin vi. You'll see some nasty log
entries for a few files; if you were looking over my shoulder while I was
trying to use this bastardized editor, you'd understand why. You'd
sympathize. It refreshes the screen when it wants to, seemingly completely
at random. You have no idea where the cursor is, except for a little
number at the bottom telling you row-column, and when it specifies two
columns simultaneously you know you're fucked.

Also, when I started writing the events classes, sometimes I copied
directory structures. Like I copied sources/news to sources/events.
However, forgetting to delete the CVS directory underneath events,
EventSource got checked in to the news directory. ARRGH. It was a happy
check-in. Ok, it went miserably. I removed EventSource from the
repository, but you can still see it there in the "Attic".

Never. Never. EVER. NEVER EVER EVER EVER NEVER. Try the cygwin vi editor.
Those of you who don't like vi... you'd cry. Those of you who love vi
(like me)... you'd cry. you really would. you really really really would.

Events are added to CVS... however the XSLT stuff for it is all on my HD,
as XML/XSL has yet to hit CVS. So, if you want to see a working version,
write your own XSL :o) no, I'm kidding. ha ha ha. I'll send you along what
I have, just email me if you want it.

by the way: as far as events go. Dates haven't really been worked out.
Currently two sets of dates are sent through SAX:
start-date-long/end-date-long and start-date-short/end-date-short (the
long versions will give you "March 13th, 2001" whereas the short versions
will give you "03/13/2001"- the methods I wrote to do this might become
handy utility methods, in which case eventually we may write a lil utils
package and throw stuff like this there). There is currently no support
for time as I'm not sure how the time will be stretched, but to tell you
the truth if time is left out until after beta I won't be upset. Time IS
supported in the database however, as the schema is using DATETIME.

I made a few small changes to the schema I set up, largely adding a unique
string field for URL detection. Here's how that works. Everything in
either "events", "events/", or "events/*.html" is sent to "events.xml".
Then, the datasource figures out what the url is. if it's
past.html, it serves up all past events (to be changed when user
preferences is firmed up and users can select how many past events
they want displayed); if the URL is future.html, it serves up
future events; if the URL ends with events, events/, or events/index.html,
it serves up a past and future (just like on the index page as it's
currently implemented). Anything else goes to the event described in the
URL. for example:

/events/gen_assembly_033101.html

EventSource will look in the database for an event with a "cms_short_name"
of 'gen_assembly_033101'. If it finds it, it serves the information
associated with it; if it doesn't, it handles it as a 404. Currently 404
stuff is handled directly within the EventSource itself (the 404 is caused
by an exception in the result set, I can probably throw whatever I want
though in the future when we want to handle stuff like this universally;
as we're not ready yet, it's going in EventSource). Keep in mind this is a
virtual 404; it's not actually searching for a gen_assembly_033101.html.
Such is the miracle of Cocoon... COMPLETELY transparent to the user.

(note to self: install a REAL vi editor... scratch that, install a REAL
Operating System.)

Of course with the way that cvs is installed on this machine, merges are
somewhat difficult, so please make sure nothing got thrown out. I
apologize profusely if I fucked anything up. I can't wait for my CD-RW,
processor, and mobo to arrive so I can install anything I want...


-------
Liam Morley

"light the deep, and bring silence to the world.
light the world, and bring depth to the silence."