I would just use Google Calendar for that. On Thu, Mar 20, 2014 at 3:53 AM, kurofune <jesseluisd...@gmail.com> wrote: > > At my job, I have to meet clients multiple times a week and schedule > appointments with them at various places around town. Recently, I have seen > a boom in business and while this is very fortunate it has made scheduling > tedious. Lamenting this fact, it dawned on me that I might be able to make a > web-application that tells me if there are any scheduling asymmetries > between me and my clients. I am thinking of something with a front page like > this: > > | myself: > | other-person: > | appointment-time: > | location: > > Both parties would enter the appropriate information on separate devices or > desktops. The information would be pushed to a database, new users would be > automatically added. A scan will be made at intervals to find mismatched > appointments, the asymmetry logged and a notice sent out to one or both of > the users, suggesting they reconfirm the appointment. Well aligned > appointments will have green status; mis-aligned ones, red, both viewable > via a monitoring screen that updates automatically. Of course, there might > be other functionality that I will want to add in later: login/security, > aesthetics, customized behavior for appointments with multiple users and > clear distinctions between business and client. In the beginning, however, I > just want to breathe a little easier knowing that my appointments are > sorted, something that simple calendar apps cannot do. > > I am relatively new to both Clojure and programming, but have managed to get > myself to a point where I can make websites that include functionality and > rendering. I have done a few tutorials utilizing databases (Datomic, jdbc, > postgresql), read a handful of books, and completed a lot of tutorials. I > still feel, however, that I don't know how to tie everything I have learned > together to tackle larger tasks that require complexity management. I don't > really know where to start, and would be grateful if someone could give me > advice in terms of what technologies I should use and how I should organize > the project. Should I use Clojures built in state management features and > jdbc/postgresql or view this as an opportunity to dip into Datomic and > core.async. I am excited about making something that utilizes all of > Clojure's technologies that other people can use and learn from, but is it > possible to go too far down the Clojure rabbit-hole? Also, if this type of > web-app already exists and you happen to have heard of it, please tell me > and I will be happy to use it instead of having to make it from scratch. > > Jesse > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
