Re: Advice needed for properties editor
Re: Advice needed for properties editor
- Subject: Re: Advice needed for properties editor
- From: Florent Pillet <email@hidden>
- Date: Sat, 21 Jun 2003 10:58:27 +0200
Thanks for the advice, Dustin. I followed the same reasoning and first
implementations showed that this was the way to go. Especially when it
comes to undo, dnd and multiple selections, it's better to have a
separate controller for each time.
Florent
On samedi, juin 21, 2003, at 03:19 Europe/Paris, Dustin Voss wrote:
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.
--
Florent Pillet, Code Segment email@hidden
Developer tools and end-user products for Palm OS & Mac OS X
ICQ: 117292463
http://perso.wanadoo.fr/fpillet
_______________________________________________
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.