Hi Kim, > Anyway, there seem to be a couple of rules sufficient to > express an entire holiday season: > - Fixed dates > - Dates relative to Easter (Easter sunday is > algorithmically available for any year) > - Nth weekday in month > - Weekday in between two dates (i.e. Saturday in between > 31/10 and 6/11 is Halloween [at least in Sweden]) > ... > If we could extend the event file generator with the last > two (it already has the first two), it'd be perfect for > batch-generating holidays.
Wouldn't it be better to provide a ruleset style system that DQSD could then parse to generate the actual dates on it's own? I've always tried to avoid hard-coding dates when possible - just cause they're a PITA to maintain. I think a solution that parsed *rules* out of the events file for the displayed month would be a better solution, since it would only really require updating the events file when new holidays were created. Not to mention it would be a pretty cool way to deal with this type of issue. Regards, Shawn K. Hall http://ReliableAnswers.com/ '// ======================================================== Efficiency is a highly developed form of laziness. ------------------------------------------------------- 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
