NSDocument and a 'persistent profiles palette'
NSDocument and a 'persistent profiles palette'
- Subject: NSDocument and a 'persistent profiles palette'
- From: "Hans Kuder" <email@hidden>
- Date: Tue, 5 Jun 2007 17:56:04 -0400
Hi everyone,
I'm creating a tool for voice teachers and students as part of a research
project. The primary purpose of the app involves analysis and synthesis of a
singer's voice using lots of DSP - I've got that part covered.
As sort of an auxiliary function, though, the app needs to allow a voice
teacher to be able to manage a list of his or her students' "profiles" - to
be able to save new recordings under a student's profile, to add new
profiles for new students, to load recordings from a profile into the
analysis/synthesis engine, and so on. I'd like for this functionality to be
contained in a single palette-style window, with a list of the teacher's
students on the left and all of the selected student's past recordings,
information, etc. on the right. All of this information should be persistent
across multiple sessions of the app, so I need a way to save both individual
profiles and the entire list of the teacher's students' profiles.
I've got a pretty robust class that encapsulates a single student's profile,
and I've got the palette interface all set up and ready to bind, but I'm
having trouble trying to figure out how to go about managing the
loading/unloading of a set of profiles. I'm hoping to make each profile a
subclass of NSDocument, but my understanding is that each NSDocument has its
own window, which I don't want. Is there a way to override this and have
each document "register" with the NSArrayController I'm using to manage the
palette? Is it possible to store all of the active profiles/documents in the
user's preferences and have them loaded at launch time?
I also thought about making the entire set of profiles one NSDocument
subclass, but I'm not sure if that would give me enough fine-grained control
over adding/importing recordings to an individual profile. Also, I don't
really think NSDocument fits at this level, since it doesn't make sense to
have multiple palettes open. Would anybody recommend this approach over the
former?
Any other ideas? This is the first project of this scale where I've needed
this sort of document-based functionality, and I could use all the help I
can get.
Thanks!
Hans
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden