Hi, Erik and thanks for the info!

Concerning your comments:

"As a matter of storage, I'd personally go with the previously mentioned
linked table (events and event dates) option and just entering all the
recurring event/time stamps in one blast for 3 years, creating some sort
of refresh or trigger option as the user browsed through the calendar to
create the successive dates"

So that approach would actually create 3 years of specific occurrences of
recurring
events in the calendar table...right?  If that's true, then it would allow
a user to modify a specific instance of a recurring event for
flexibility...right?

Also, can you describe the "refresh or trigger option" a little more?  Is
this
for creating specific occurrences of recurring events only when the calendar
is called up for viewing of a previously unviewed time period on the
calendar?

Rick



-----Original Message-----
From: Erik Yowell [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 2:18 AM
To: CF-Talk
Subject: RE: RE: How to handle Calendar Scheduling of Recurring Events?


I think someone mentioned Outlook a couple of messages back in the
thread, which I believe (if I'm not mistaken, if I am flame on) uses the
RFC 2445 Standard. ( http://www.ietf.org/rfc/rfc2445.txt ,
http://www.ietf.org/internet-drafts/draft-ietf-calsch-many-xcal-02.txt )
Digging further on this there is quite a bit of notation on how to
describe recurrence events through this and the ISO 8601 date time
standard, of which there are some good docs on it here:

http://www.pvv.ntnu.no/~nsaa/ISO8601.html

Also, while I hate to bomb you with links here, if you're using CFMX
check http://recurrance.sourceforge.net somebody created a recurrence
rule engine in Java.

As a matter of storage, I'd personally go with the previously mentioned
linked table (events and event dates) option and just entering all the
recurring event/time stamps in one blast for 3 years, creating some sort
of refresh or trigger option as the user browsed through the calendar to
create the successive dates. Then perhaps some sort of cleanup operation
for the archived dates applying the same trigger going backwards if a
user starts going "back in dates". As long as you have some sort of
origin (ISO8601 or RFC2445) and a parser of sorts you can create event
date times whenever you want (i.e. on calendar "next" "prev" events).
How many users like to cycle through a calendar that far forward or
backwards anyways? This is all for presentation mostly is it not?) It
may get bulky eventually depending on it's usage, but I've seen well
tuned sql dbs handle millions of records at a time with lightning fast
execution times (let's hope if you're generating millions of event
records you're making some money to pay for a well tuned database).

I'm sure there is much more data beyond what I've provided, but there's
some more kindling for the fire. Let us know how it turns out, as I'd
love to collaborate on such endeavors for cold fusion considering I'm
constantly running across building apps where this would be handy. Of
course time and budget constraints never allow me to flesh this idea in
full... that and I'm lazy.

Cheers,

Erik Yowell
[EMAIL PROTECTED]
http://www.shortfusemedia.com


-----Original Message-----
From: Rick Faircloth [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 9:52 PM
To: CF-Talk
Subject: RE: RE: How to handle Calendar Scheduling of Recurring Events?

Hi, and thanks for the reply.

I'd appreciate any code and advice you're willing to share!

Thanks!

Rick

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 5:28 PM
To: CF-Talk
Subject: Re: RE: How to handle Calendar Scheduling of Recurring Events?


Ahh yes, that was a PITA to do.  I've got some code to deal with it, so
if
you need some, just ask.

----- Original Message -----
From: Rick Faircloth <[EMAIL PROTECTED]>
Date: Tuesday, January 14, 2003 3:21 pm
Subject: RE: How to handle Calendar Scheduling of Recurring Events?

> Hi, Howard.
>
> Thanks for pointing me to that feature of Outlook.
> I use Outlook, but hadn't used that feature.
> The only problem I noticed it didn't solve is the "stickiest"
> problem of the app:  That of handling recurring events
> that are held with a description like "2nd Tuesday of each month".
>
> Joshua has come with an approach.  I've got to give that a look...
>
> Thanks for your input.  Let us know what you consider
> when determining your approach to your calendar app.
>
> Rick
>
>
> -----Original Message-----
> From: Owens, Howard [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 14, 2003 3:30 PM
> To: CF-Talk
> Subject: RE: How to handle Calendar Scheduling of Recurring Events?
>
>
> This discussion has come up at a timely time, as I'm getting ready
> to build
> a calendar app.
>
> I just wanted to point out -- take a look at the recurrence screen in
> Outlook. It's a pretty intuitive GUI and might provide some useful
> guidanceon how to set up such an interface, provide some good
> ideas on how to
> collect data (and what needs to be collected) and provide further data
> storage hints for the best way to store and retrieve the info.
> Also, with a
> bit of JavaScript, the GUI could be emulated pretty nicely.
>
> H.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Howard Owens
> Internet Operations Coordinator
> InsideVC.com/Ventura County Star
> [EMAIL PROTECTED]
> AIM: GoCatGo1956
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to