I am starting to write a course-instructor-room scheduling application
with a number of separate lists (e.g., courses, rooms, instructors),
each of which will be fairly short, but might have quite a few
fields. The main application window will be trivial - a set of
buttons, each of which opens a window to edit the relevant array
(e.g., "Edit Course List"), and a single "Do it" type button. (The
scheduling is done algorithmically, not interactively.)
I've decided not to use Core Data for this.
My question: given this setup, is it worth the trouble to have
separate nibs for each of the list-editing windows? I'm leaning
towards having one single nib, but perhaps that is unwise.
Thanks in advance,
Dave
============================
Dave Hirsch
Associate Professor
Department of Geology
Western Washington University
persistent email: dhir...@mac.com
http://www.davehirsch.com
voice: (360) 389-3583
aim: dhir...@mac.com
vCard: http://almandine.geol.wwu.edu/~dave/personal/DaveHirsch.vcf
============================
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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 arch...@mail-archive.com
