• 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
newbie q: application window architecture
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

newbie q: application window architecture


  • Subject: newbie q: application window architecture
  • From: Carrie Brezine <email@hidden>
  • Date: Fri, 15 Nov 2002 19:55:21 -0500

hello,

I am new to Cocoa so I beg some patience as I try to explain my questions.

I am building a data-entry application so that users can enter information about a very complex set of objects. Each object can be thought of heirarchically: the highest level qualities of an object, say color and pattern, are also found at the lowest or most detailed level, and must be completely specified wherever they occur. There is far too much information about any one object to go on one data entry window, and the data validations that must occur between controls are significant. Therefore, I plan to split up the data into categories or levels and create separate windows for different areas. I think these should probably go in separate nib files as well, because otherwise I'm afraid the nib will get too large.

Because some characteristics occur at all levels, I would like to reuse certain data entry views on different windows. For instance, it seems to me that the data entry view for color and pattern (I am using "view" loosely here) could be reused on different windows so that I wouldn't have to duplicate the controls and validations. One question is, what is the difference between using a custom NSView and using a group of controls subclassed into an NSBox? I've played around with each and I think I can get either one to work. I don't need fancy drawing, coloring, or mouse events (yet), just a group of controls. However I *do* need lots of validations on the controls before I send the info to the db. Instead of subclassing NSView for this, is it correct to use NSBox and just add a subclass of NSObject to the nib which would have the job of validating data? Or should data validation always go in the NSWindowController?

One thing I haven't yet gotten to work correctly is loading the same NSView content into different windows or boxes at the same time. Suppose I have a custom NSview called MyView in its own nib and a window with Box1 and Box2. I would like both Box1 and Box2 to show the content of MyView, so I guess what I really need is to create two instances of MyView? If anyone can point me to a reference for something like this I'd be grateful.

Also a general application question-- my understanding is that the MainMenu.nib is the one loaded when the app starts up. So if there is a login screen, I presume it goes in there? and then the app launches what will be the primary screen for the application?

thank you

Carrie _______________________________________________
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: newbie q: application window architecture
      • From: Ondra Cada <email@hidden>
  • Prev by Date: [OT] jobs?
  • Next by Date: Cocoa app within a browser window
  • Previous by thread: Re: [OT] jobs?
  • Next by thread: Re: newbie q: application window architecture
  • Index(es):
    • Date
    • Thread