Slide wrote:
I liked the idea someone mentioned about having a sort of source control mentality about it all. You can grab a working copy and put it on your laptop for meetings and then when you are done, you can "commit" the changes back into the main repository or database. This could be achieved in a variety of ways.
In a pass calling I was a Stake Assistant Clerk... As one of my calling responsibilities I was asked to keep track of the building schedule for our stake center. I did it as a hosted web app (written in PHP/mySQL). This way the leaders could see what was scheduled any time of the day or night. For planning meetings I would also have the building schedule web app installed on my laptop (Powerbook running Mac OS X, Apache, etc.) and a "read-only" copy of the database installed. In fact, this is how I kept the database backed up. I would copy it down to my laptop on a weekly basis.
FYI, you can see my building scheduler app running at http://lds.son.org/schedule/. I guess I should have used the LDS ward web site stuff but I found using the "resource calendars" were more bother than help since it had no way to detect resource conflicts, etc.
-stacey. _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
