Well, I guess it's a separate argument as to whether or not "Import"
should be used instead of "Open". I tend to think of "Import" as
being used to add to an existing document's data (creating one if
none exists), and for data types that are not "native" to the app.
Yes it's a separate argument, but one that is worth thinking about.
"Import" has its place, but not as often (in my view) as you actually
see it. Users don't care about the semantic differences (usually),
they just want to open a file. Note that Adobe apps typically use
"Place" to mean open a file to add its contents to the document; I
find that more meaningful.
It's easy enough to make my app open more document types, but that
doesn't really get at the core of the problem...how does one add
fundamental commands similar to Open? They're targeted at the first
responder, and it seems that typically, one does not subclass
NSApplication. Who handles these actions when the messages are sent,
in the varying cases of having a document open, vs. no document
open, etc?
Your application delegate is a good place, and it can use the global
NSDocumentController to handle much of it. App delegate will receive
anything directed at first responder that hasn't already been handled
otherwise.
------
S.O.S.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
