Re: [Q] Get rid of NSDocumentController ?
Re: [Q] Get rid of NSDocumentController ?
- Subject: Re: [Q] Get rid of NSDocumentController ?
- From: Charles Srstka <email@hidden>
- Date: Sun, 11 Nov 2001 14:27:05 -0600
Actually, I do the same thing as you want to do, and it's easy to get
just the file path of the file you're opening. Look up the method
readFromFile:ofType: in the AppKit docs under NSDocument.
On Sunday, November 11, 2001, at 11:48 AM, [..'] ruyon wrote:
[..'] Hello.
I'm trying to write a drag&drop multi-file batch processing
application, similar to Dropstuff.
The problems are;
1. Adding document plist, which seems to be necessary to enable
file-dragging onto my app, also make an instance of
NSDocumentController that I really don't want. I don't want 'Open
Recent' menu and unnecessary memory use (although not that much) either.
2. Impossible to get a list of dragged files. since what I need is just
the list of path, not contents of hem.
After a few days of digging docs, I thought 3 possible (I think)
solution, listed in order that is easiest but unfavorable, to difficult
but attractive.
1. Write my app in carbon and utilize apple event, which returns me a
list of dragged files.
2. Write my app in carbon and utilize apple event, along with
FoundationKit.
3. Get rid of, or subclass NSDocumentController and get NSArray of
dragged files somehow.
So, what would be the best approach to this kind of application?
By the way, I don't think apple's DocController-Doc-WinController
paradigm is the worst of this world, but It should be optional for more
flexibility.
TIA
Ru
---------------------------
[..'] Dost thou remember those days? - "Hello, world!"
http://homepage.mac.com/ruyon
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev