Shawn, > > My only concern was that it may be sluggish driving all > > that with JS, but I guess it's not really a problem. > > Sice it only needs to show one month at a time, I can't imagine it'd > be very heavy on overhead, even if it processed the entire year in > order to generate the dates.
Nah, you're probably right. > > Then there's the issue if some calendar doesn't comply to > > the rule-set. > > Do holidays exist that don't follow some form of ruleset for > determining the date? I don't know, but I wouldn't be surprised... In fact, it's bad enough if it follows some rule we haven't implemented, say the fourth full-moon after the fourth of July, or whatever. Your example was a data model for my Swedish Halloween sample, but the question is if there are holidays that aren't expressible with the four rules I thought up. And the big question is how many rules it takes to cover all "interesting" calendars. The current model is a bit clunky, but it doesn't have *any* restrictions (barring holiday-file-builder patience), which is why I prefer it so far. Kim ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ To unsubscribe visit: https://lists.sourceforge.net/lists/listinfo/dqsd-users [EMAIL PROTECTED] http://sourceforge.net/mailarchive/forum.php?forum_id=8601
