Re: [MRBS-general] Different end time for a specific day (or days)
Brought to you by:
jberanek
From: Anselm M. H. <an...@ho...> - 2010-01-29 21:00:13
|
Am Freitag, den 29.01.2010, 08:59 -0600 schrieb Cory Jaeger: > If Thursday's time is earlier, book a recurring event to block off the rest of the day like "Early Close" > > If it is later, book a recurring event that blocks off the extra time on Fri-Wed. I second that idea. The important advantage is that it comes with a well-known check against bookings in that time. Imagine you change the display logic for day/week view to not allow bookings starting in the "evil" time slots. Do not forget to check for new/changed bookings wether their end time is "invalid" in your changed time frame. Do not forget to add logic to check recurring bookings when added / changed. It is a Pandora's box of bugs if you do not exactly know what you are doing (and even then, I might guess :-). If you follow Cory's suggestion, all collision checking comes "free" as it is already implemented. My personal way of achieving one weekday with differing end time would be to use booking type e.g. "Z" for the forbidden time slots, change the add/modify pages to not offer this booking type in the list of allowed booking types, change month view to completely ignore type "Z" bookings (it's only one SQL query to be changed there, I guess) and change day/month view to make those bookings "unclickable" (while drawing cells, instead of displaying anything, just print a without any <a> around it). You might also want to choose an appropriate colour for those magic bookings, like, white or light gray... > -or- > > Make some serious modifications to MRBS that will make it difficult to upgrade as new versions come out. I can understand that upgradability is not an important concern for you, so lots of changes to the codebase might be OK. On the other hand, why code dozens of lines and do bug tracking when doing about 20 with low bug risk is already enough? Just my $0.03 (inflation-adjusted) BR Anselm |