Ankur Sethi wrote: > Some general thoughts: > > Decouple the actual calendar UI from the server that actually manages > notifications. Create a directory called 'events' in /boot/home/ and > store every event in that directory as an empty file with the event > information stored as attributes. The cal_server could monitor this > directory to be notified of new events. (Talking of notifications, > take a look at this: http://dev.osdrawer.net/projects/infopopper). This was exactly the design I thought from the very beginning, with some minor tweaks. IMO, there are at least 4 parts of the application: the EventEditor (used to create and edit events), the EventDaemon (the thing you called cal_server - a daemon running live queries and executing actions when events' time comes; it can't be a "server" since it's not a part of the OS), the GUI and the server part. Besides, the EventEditor itself should be implemented as a GUI to a shared library, in order to enable creation of additional plugins by other programmers. (This was not written in the user story, since user is not supposed to know the internal implementation, but "plugins" is a buzzword novadays). I hope to find mentors for this project. Without mentors, it will not go, and I'll have to think about something else. Thanks, Alexey Burshtein.