Better support for multiple Macs
Posted: Wed Aug 29, 2007 7:45 am
The current procedure:
Mount disk to where the main database resides, make sure there is only one copy of ***Pedia running (otherwise you can easily overwrite your updates without any warning).
I think this is pretty cumbersome. I also think it will become more of an issue, as the greatly improved Front Row/Apple DVD Player in Leopard encourages more people to have dedicated HTPC Macs, the logical thing to do is to have your main database on the HTPC or at any rate an "always on" desktop machine.
What I would suggest is eliminating the disk mounting requirement, so long as ***Pedia is running on the "server" have the DB visible on all client machines (think iTunes/iPhoto, etc.), and allow updates from any of the machines with autosaves of changes (say each time OK is hit on the Add/Edit window) to prevent overwriting.
Mount disk to where the main database resides, make sure there is only one copy of ***Pedia running (otherwise you can easily overwrite your updates without any warning).
I think this is pretty cumbersome. I also think it will become more of an issue, as the greatly improved Front Row/Apple DVD Player in Leopard encourages more people to have dedicated HTPC Macs, the logical thing to do is to have your main database on the HTPC or at any rate an "always on" desktop machine.
What I would suggest is eliminating the disk mounting requirement, so long as ***Pedia is running on the "server" have the DB visible on all client machines (think iTunes/iPhoto, etc.), and allow updates from any of the machines with autosaves of changes (say each time OK is hit on the Add/Edit window) to prevent overwriting.