The response to my release of DropboxAppSync this week has been awesome. People are really enjoying the benefits that it’s bringing them. I have received some really great feedback and have the first update ready for everyone. Thanks to Brett Terpstra for his blog post that brought some great insight into things as well. Here is a list of the enhancements…
- The Application that you have selected will be asked to Quit for you. If you have any open documents open with changes, you should be prompted to save your changes (unless auto-save is used).
- The Application Support folder is no longer located just by using the name of the application. Some application have custom App Support folders. These are now quieried for and used if found.
- If a custom location is not found, then the CFBundleName is used. If for some very odd reason, there isn’t a CFBundleName defined, then the application name will be used.
- A log file is now stored at ~/Library/Logs/DropboxAppSync.log
There is one feature that I have been hesitant to add. That is the ability to move your entire App Support folder for every application to Dropbox. To be honest, this is dead simple to implement. However, I dont think that I want to add this, at least for now. I think that its safer to add the handful of apps that you really need/want.
Now essentially, this app is a glorified Automator script. This means that there are no automatic updates and it somewhat limited when it comes to user interface. Who knows, maybe this can be a start of a actual app utility. But for now, I think that it should suit us well. I hope that you enjoy DropboxAppSync!
Update: I wanted to let users be aware of an upcoming issue that DropboxAppSync may face. Starting later this year, applications submitted to the MAS will be required to be sandboxed. This means that nothing outside the individual application will be allows to access the App Support folders. Where does this leave DropboxAppSync? I don’t know for right now, I will cross that bridge when I get to it.