This is not a Perl question (yet) .. it's a programming question.
So I'd start with the guts .. figure out a database structure that support the functionality you need (that's also known as the model). Then write functions that will talk to the database doing stuff like adding appointments (maybe checking for conflicts first? -- that's known as the controller). Finally, wrap the whole mess in a user interface (that's known as the view).
Then you've completed a model-view-controller or MVC application. And please come back when you have a Perl question for us!
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
In reply to Re: Designing a Schedule Synchronizer
by talexb
in thread Designing a Schedule Synchronizer
by pinque
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |