Re: Document App or not?[little ot]
Re: Document App or not?[little ot]
- Subject: Re: Document App or not?[little ot]
- From: email@hidden
- Date: Sun, 8 Feb 2004 18:20:55 -0500 (EST)
I would have agreed with you 3 weeks ago.
sharedDocumentController changed my mind. I am sure there is a reason I am
wrong about this but I have an app with many nibs and doc types and it
pratically wrote itself after I implemented the shared document
controller. As long as the shared controller instanciates?sp the document,
and the document has a reference to the shared controller they can
communicate.
SomeDocController * docArbitraitor = [NSDocumentController
sharedDocumentController];
if([[self window] isEqualTo:[NSApp keyWindow]]){
//I'm being talked to so I'll talk back
return someData;
- or -
[self performATask];
}
I think the above is correct but again, at work, no books, might be
incorrect, but you get the idea.
>
I created an application that handles documents similar to TextEdit,
>
but it was a single-window application. I decided to make it a document
>
based application to take advantage of the automatic file handling it
>
provides (open recent menu, file icons, etc.). Some say that the
>
document architecture is a great example of MVC, but I found it
>
extremely awkward to make a single-window document based application
>
because the document is so closely tied to the window controller. I
>
suggest not making it document based because it limits the flexibility
>
of the program's design - or at least it did for me.
>
>
Ryan
>
>
On Feb 8, 2004, at 7:23 AM, Peer Allan wrote:
>
>
> I planning on creating an application that will have a similar
>
> interface
>
> structure to iTunes, but I am not sure if I should use a Document-based
>
> application or not. Any advise as to pro or con of each option would
>
> be
>
> greatly appreciated.
>
>
>
> Basically the app will have a predefined collection of players that
>
> will
>
> load in a window like the main window for iTunes. Users don't add or
>
> remove
>
> from this collection but they can manage their own groupings of the
>
> players
>
> from the collection. A single click on a group will list its members
>
> in a
>
> table view (like a playlist and its songs). If a user double-clicks
>
> on the
>
> group, a separate window would open with more details of the group and
>
> all
>
> of its members. The user should be able to have multiple group
>
> windows open
>
> at a time. Any changes or updates the users make to the groups would
>
> be
>
> saved automatically.
>
>
>
> My question is, would a document-based application be better for this
>
> app
>
> because of the management issues of multiple group windows or can this
>
> be
>
> done in a standard application?
>
>
>
> Peer
>
> _______________________________________________
>
> cocoa-dev mailing list | email@hidden
>
> Help/Unsubscribe/Archives:
>
> http://www.lists.apple.com/mailman/listinfo/cocoa-dev
>
> Do not post admin requests to the list. They will be ignored.
>
_______________________________________________
>
cocoa-dev mailing list | email@hidden
>
Help/Unsubscribe/Archives:
>
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
>
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.