Thursday 01 April 2010 12:02:28 pm
You guys should start a new project on projects.ez.no !
Now for the ideas... I'd would say this would need to be made as open as possible.
Without further thinking, it seems to me that a datatype would be a good basis, along with a few persistent objects dedicated to storing booking data. Each place available for booking would then be a content object with standard informations (pictures, text, etc), and some sort of booking attribute that would be used to automatically show the booking interface. Regarding the open approach, it seems mandatory to me since this most likely has to be adapted to very different situations. It is quite easy to re-use several mechanisms the extension API offers. For instance, custom triggers could be implemented around the standard actions (book, etc) so that any custom process can be hooked there. The template engine is the perfect tool for graphical customization, especially if the templates have been carefully organized. Good CSS naming would also make it very easy.
Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier
|