Launching previously open Finder windows is a bit more tricky that this, though: Tell application "Finder" to set visible of application process "Skype" to false Suppose we need to launch Skype (and hide it also) a little after the Messages app has been launched and got hidden easy: include a delay 1 command to force AppleScript execution to pause for 1 second. Ok, and how might it be possible to create an actual sequence of applications launching one after the other? Well, I did not find an elegant way of doing it, but there is always a “dirty” way delays. Set visible of application process "Messages" to false Tell application "Finder" to set visible of application process "Messages" to false Let’s get to business: launching an application using a AppleScript is easy likeĪnd how about hiding the application (prevent the main app window to show up)? My approach would be to remove everything from the Login items list in System Preferences and create an app in the Script Editor of Mac OS to do the job in a more controlled way. These are apps really time consuming and resource demanding during startup and their simultaneous launching might be problematic. For my case study let the applications needed to start during login be: Finder (previously open windows), Messages, Skype, Activity monitor, Yellow (an app for post-its on the desktop), Bandwidth+ (an app for the display of network activity), Translate Tab (an app for Google translation functionality on the Status Menu), Safari, Google Drive (nowadays called Backup and Sync) and two sessions of Dropbox (two distinctive instances for different login credentials - this is another issue discussed here). In the following paragraphs I propose an alternative way of defining the Login items list, which gives some control over the sequence of actions during login. This might result in applications taking more time to launch (because the share the same resources of the machine at the same time) and if there are dependencies for one application to specifically launch after another, then we have a serious issue. This or the other way, the Login items section could end up with a long list of applications, which is great in its own, but there is an issue: although we might expect those applications to be launched in a serial manner, one after the other, so that we have a control on what and when is happening, we get a number of applications competing to launch at almost the same time. In more “advanced” approaches, one may easily include another application (with no such option) in the login launch list by manually adding it to the Login items section in the System Preferences panel > Users & Groups section for the current or any other user (might need admin credentials). Popular applications such as Dropbox provide a general setting to “Start Dropbox on system startup”. The obvious approach in the case of Mac OS X is for someone to rely on the system and the application settings to “attach” the launching of the application during login. In this post I made up a step-by-step process to optimize the login automation on a Mac OS X machine. One such option is the launching of applications during system startup just after we login. One great automation option we may enjoy in our everyday work is that provided by the operating systems on our computers to perform tasks for us. Automation is conservation of energy its like the habits we people are into, the habits that seem to be there for all living entities.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |