added a friendly message for where the app is located when you're done running the script
Merge pull request #13 from deanmalmgren/finish-instructions

alert user where name.app is located
absolute paths a la https://github.com/lhl/chrome-ssb-osx/pull/14
make the generated SSB's retina-enabled
Merge pull request #15 from aerickson/master

make the generated SSB's retina-enabled
launch chrome directly (vs via a symlink)

* Now behaves like original script and AppleScript. 
  <https://www.lessannoyingcrm.com/blog/2010/08/149/create+application+shortcuts+in+google+chrome+on+a+mac>
* No longer needs/creates a symlink to Chrome app.
* Doesn't have PDF plugin loading issue. fixes
  <https://github.com/lhl/chrome-ssb-osx/issues/8>
Merge pull request #16 from aerickson/master

launch chrome directly (vs via a symlink)
doc update
Merge pull request #17 from aerickson/master

doc update
absolute paths on dirname calls

This is minor, but I made all paths absolute to be consistent with the rest of the script in case people have strange aliases on dirname (which I've admittedly never heard of...)
Merge pull request #18 from deanmalmgren/patch-1

absolute paths on dirname calls
Reverted commit 2444557e65 to address issue #20 ; note, PDF viewing
works w/ Chrome v30
added a note so that it doesn't get taken out in the future...
fix for #22 - copy binary stub instead of symlinking
update notes for Mavericks compatibility
added note on issue #23 (code signing)
Save a symlink to Chrome executable on SSB creation; copy at each SSB startup to ensure current Chrome launcher is being used
Merge pull request #24 from tw1nturb0/hybrid_symlink

Hybrid symlink approach for Mavericks launcher issue