• 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: Advice needed for properties editor
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Advice needed for properties editor


  • Subject: Re: Advice needed for properties editor
  • From: Dustin Voss <email@hidden>
  • Date: Fri, 20 Jun 2003 18:19:05 -0700

On Thursday, June 19, 2003, at 09:00 AM, Florent Pillet wrote:

I'm writing a UI constructor for Palm software. Right now all the back-end is done and some of the UI is up.

I need some advice on each UI element's properties editing: is it better to create one different view for each UI element, or a generic property editor that would look clumsier than a specialized view per UI element ?

I'd definitely appreciate any insight you experts have on this. I especially would like to know the pros and cons of having 1 nib per UI element type (I have about 15 of them to cover), or if have one nib files containing all the distinct views with a single controller view that would be loaded once and for all...

My advice is to create a properties window, its controller, a raw view for each element editor, and a controller for each editor. The editor views and the window should all go into the same NIB. The window controller can manage the window and load/unload each editor's view and controller instances. The editor controllers should not be included in the NIB, but should be instantiated and connected to the view at run-time. One controller and view should be instantiated per selected element.

My reasoning is as follows:
1) You'll want to thoroughly test each element editor as you support it, which is easier if it is a clean, separate class and view.
2) Each editor is guaranteed to be harder than you think it will be, which means a master controller for the window and views will be even more unmanageable than you already know it will be.
3) As a general rule, when it comes to programming, a stitch in time does NOT save nine.
4) This modular structure will allow you to more easily handle multiple selections or new custom controls, should you offer any.
_______________________________________________
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: Advice needed for properties editor
      • From: Florent Pillet <email@hidden>
References: 
 >Advice needed for properties editor (From: Florent Pillet <email@hidden>)

  • Prev by Date: Re: NSOpenGLView in NSSplitView, redraw problems
  • Next by Date: Bundle not loading
  • Previous by thread: Advice needed for properties editor
  • Next by thread: Re: Advice needed for properties editor
  • Index(es):
    • Date
    • Thread