#2318 NORM Untriag: Changing the "Open" functionality of CTRL-O shortcut

[Zarro Boogs per Child]

#2318: Changing the "Open" functionality of CTRL-O shortcut
--------------------------+-------------------------------------------------
  Reporter:  mcfletch     |       Owner:  uwog                             
      Type:  enhancement  |      Status:  reopened                         
  Priority:  normal       |   Milestone:  Untriaged                        
 Component:  sugar        |     Version:  Development build as of this date
Resolution:               |    Keywords:                                   
  Verified:  0            |  
--------------------------+-------------------------------------------------
Changes (by Eben):

  * status:  closed => reopened
  * resolution:  invalid =>
  * type:  defect => enhancement
  * component:  write-activity (abiword) => sugar
  * summary:  No "Open" Icon in Write => Changing the "Open" functionality
              of CTRL-O shortcut

Comment:

 This is not a bug; this is by design.  Though the metaphor is different
 that that we're used to, we're focusing on an object model where there is
 no distinction between the file being opened and the application it opens
 in; They are one and the same thing.  The Journal should provide a space
 for quickly locating and launching old projects as separate instances.

 In fact, that said, we should do something about the CTRL-O shortcut.
 ::idea springs to life::  Rather than eliminating this shortcut
 altogether, why don't we make it automatically switch to the Journal
 activity, and also automatically apply the filter for the activity that
 initiated it.  That way, one keystroke will reveal a list of all the files
 created with, for instance, the Write activity, and one more click will
 launch a selected object in a new instance.

 This achieves nearly the same functionality as a file open dialog, but it
 removes the need for a modal dialog window and eliminates the confusion
 that would come with "replacing" one document object with another in the
 same running instance of an activity?  Are there any drawbacks to this
 implementation that I might not have yet foreseen?

-- 
Ticket URL: <http://dev.laptop.org/ticket/2318#comment:3>
One Laptop Per Child <http://laptop.org/>