• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Document App or not?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Document App or not?


  • Subject: Re: Document App or not?
  • From: Dustin Voss <email@hidden>
  • Date: Sun, 8 Feb 2004 20:38:45 -0800

On 8 Feb, 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?

I'm no expert, but the document framework has some pros and cons. On the con side, it expects a one-document-per-window arrangement, and expects documents to be files. On the pro side, multiple windows can show the same document, and the same document can be represented by multiple views. Also, AppleScript support is easier with documents.

In your case, I would think that a group is a document. The group list could be managed by a model object outside of the document architecture. I think you would have two different controllers interacting with the group and windows. One controller would be the simple table view, interacting with the main window, and the other controller would be the detail window view.
_______________________________________________
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.
  • Follow-Ups:
    • Re: Document App or not?
      • From: "M. Uli Kusterer" <email@hidden>
References: 
 >Document App or not? (From: Peer Allan <email@hidden>)

  • Prev by Date: How do I soft-wrap text at a specific line length?
  • Next by Date: Re: Need help moving an NSSlider
  • Previous by thread: Re: Document App or not?[little ot]
  • Next by thread: Re: Document App or not?
  • Index(es):
    • Date
    • Thread