Skip to main content

Script Utility for my "SOE"

This is a really old one, just re-hashing it here as I forgot to add it to my 10.7 SOE.

We use Lotus Notes in some of our offices. The default font size on larger resolutions is small enough to send people blind. Unfortunately there is no UI for changing the size. This simply applescript gives end users the option to do so.

Please note the values should range from 1-5 with 1 being the default size and 5 being the largest (not really the largest but the maximum you should go to, try it... you'll see what I mean).


set _prompt to display dialog "Lotus Notes Default Font Size?" & return & return & "Please ensure Lotus Notes is not running before proceeding." buttons {"Continue", "Quit", "Reset"} default button 1 with icon stop
set _response to button returned of _prompt

if _response is equal to "Continue" then
 
 set _sizes to display dialog "Lotus Notes Default Font Size?" & return buttons {"Large", "Larger", "Largest"} default button 1 with icon stop
 set _size to button returned of _sizes
 
 if _size is equal to "Large" then
  set Display_Font_adjustment to "2"
 end if
 
 if _size is equal to "Larger" then
  set Display_Font_adjustment to "3"
 end if
 
 if _size is equal to "Largest" then
  set Display_Font_adjustment to "4"
 end if
 
 do shell script ("/bin/cat ~/Library/Preferences/Notes\\ Preferences | grep -v 'Display_Font_adjustment' > ~/Library/Preferences/Notes\\ Preferences.new")
 do shell script ("/bin/cp -f ~/Library/Preferences/Notes\\ Preferences.new ~/Library/Preferences/Notes\\ Preferences")
 do shell script ("/bin/echo 'Display_Font_adjustment=" & Display_Font_adjustment & "' >> ~/Library/Preferences/Notes\\ Preferences")
 
else if _response is equal to "Reset" then
 do shell script ("/bin/cat ~/Library/Preferences/Notes\\ Preferences | grep -v 'Display_Font_adjustment' > ~/Library/Preferences/Notes\\ Preferences.new")
 do shell script ("/bin/cp -f ~/Library/Preferences/Notes\\ Preferences.new ~/Library/Preferences/Notes\\ Preferences")
end if

quit

Popular posts from this blog

Mac OS X "SOE" Day 7

Page Redirection > continued from day 6... In summary, here is my method for creating a Mac OS X 10.7.3 Standard Operating Environment "SOE" Image. Overview The goal is to create a "MASTER" non-booted SOE that can be used with multiple models and it multiple sites with different local requirements. My intention is to use this "MASTER" image in a manual restore procedure due to the fact netboot facilities cannot be made available to all the sites I support however the DMG files are netboot compatible. Requirements Lion Recovery Disk Assistant v1.0 "TARGET" workstation. A compatible workstation that will be used to install Mac OS X 10.7.3 and capture a DMG image(s). "ADMIN" workstation. A workstation with Disk Utility that you will use to capture your DMG image(s). External storage such as a USB HARD DISK. Setup Downloaded the Lion Recovery Disk Assi...
more...

Mac OS X key-based ssh login

To set up key-based SSH, you must generate the keys the two computers will use to establish and validate the identity of each other. To do this run, the following commands in Terminal: Check to see whether a .ssh folder exists in your home directory by running the command ls -ld ~/.ssh. If .ssh is listed in the output, move to step 2. If .ssh is not listed in the output, run mkdir ~/.ssh and continue to step 2. Run: cd ~/.ssh Run: ssh-keygen -b 1024 -t dsa -f id_dsa -P '' This command generates the public and private keys. The -b flag sets the length of the keys to 1,024-bits, -t indicates to use the DSA hashing algorithm, -f sets the file name as id_dsa, and -P '' sets the private key password to be null. The null private key password allows for automated SSH connections. Run: touch authorized_keys2 Run: cat id_dsa.pub >> authorized_keys2 Run: chmod 400 id_dsa The permissions on the private key must be set so that the file is not world readable. Run...
more...

Mac OS X "SOE" Day 6

Page Redirection > continued from day 5... Continuing on from the "firstboot" phase setup we need to script our "localiser" options. I previously set my build phase to autologin and run the firstboot script, the localiser phase essentially sits there and waits for you to run it. In my case I have an applescript GUI wrapper that requests some info to use in the localisation. I request a TAG number which is an organisational internal number and I also request a user name that will be set as the OWNER. NOTE : I ordered these specifically...not just because it makes sense logically but also technically. For example, setting the Language actually zaps a plist file (.GlobalPreferences) which you need to write to for Locale and Country info. This stuff is going to be totally dependant on your environment, as an example here is what I do. So what's the minimum we need in the "localiser" phase? Depends on how many sites you support,...
more...