Hi.This is something I've been thinking about for a while without making much progress. Let's say that you have an application where you would have one or many "documents" but where the documents itself are not tied to a specific file. Examples of such applications could be terminal emulators or FTP clients.
My first idea was to use a standard single window application and have each "session" controlled by an instance of a controller object. That however would give a lot of manual tasks, things like setting the location of new windows stacked relative to the previous window etc. That's things that I would more of less get for free by using NSDocument and NSDocumentController, but they seem to be more tied to the concept of working with files.
I have done some testing with both methods but I can't decide which one is the most appropriate to use. How would you approach making that kind of application?
Thanks Marcus
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
