[Chandler-dev] Function-key scripts

[Morgen Sagen]

Out of the box Chandler ships with the following scripts that are
triggered by function keys, and I think we should take a quick pass at
which ones to remove:

'F1 - Create a new script' (Script) //parcels/osaf/app/New Script

   Running this one creates a Script item in the repo but doesn't
expose it to the user anywhere, so repeated pressing will fill up the
repo with garbage.

'F2 - Block under cursor' (Script) //parcels/osaf/app/Block Inspector

   This prints to stdout the name and UUID of the CPIA block under the
mouse cursor.

'F3 - Item selected' (Script) //parcels/osaf/app/Item Inspector

   This one always prints "None" to stdout.

'F4 - Browse selected item' (Script) //parcels/osaf/app/Browse Selected

   My favorite: launches the web browser to display details about
selected item.

'F5 - Paste new item' (Script) //parcels/osaf/app/Paste New Item

   I could have sworn I saw this work recently, but when I try it now,
nothing happens.

'F6 - Print selected item to stdout' (Script) //parcels/osaf/app/Print
Selected to stdout

   This calls Item.printItem( ) for the currently selected item,
displaying all attributes to stdout.



I wouldn't mind losing all of these except for F4 which I use
constantly, and I think for support purposes we will likely ask end
users to use F4 to provide us debugging info.  I imagine that other
devs use F2 ?  Should we remove any of these, and/or bind them to
different function keys?

~morgen