[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
some consideration on NSWorkspace
From: |
Enrico Sersale |
Subject: |
some consideration on NSWorkspace |
Date: |
Mon, 17 Jun 2002 17:07:55 +0300 (EEST) |
The recent changes in NSWorkspace don't let anymore GWorkspace to launch
applications with double-click on an icon, a fiend tile or a browser cell
that represents an application.
Ths happens because the changes in NSWorkspace affect also
_launchApplication: that, before, accepted also a path as argument.
Well, this wouldn't be a big problem because I could modify the
GWorkspace's methods where -launchApplication: is called to use the
application name instead of the path.
But one case remains in which, this new beaviour, represents a problem;
if, for example, I've "myapp.app" in $GNUSTEP_SYSTEM_ROOT/Applications and
also an "/home/enrico/myapp.app" and I want to launch *this* myapp.app
double-clicking on its icon, NSWorkspace will launch
$GNUSTEP_SYSTEM_ROOT/Applications/myapp.app anyway.
I think that -launchApplication: should accept a full path to the
application, too.
Or, pherhaps a better solution, we could let - (BOOL) openFile:
(NSString*)fullPath (in this case we have specifically "fullPath" in the
method name) to launch an application if "fullPath" represents such an
object.
An other thing: on openstep, if I give an "open /home/enrico", a new
viewer window, rooted at /home/enrico will appear. I think that -openFile:
should call the -application:openFile: method of the _workspaceApplication
(that I could easily implement in GWorkspace), if "fullPath" represents a
directory. Doing this, gopen would have the same behaviour...
- some consideration on NSWorkspace,
Enrico Sersale <=