Re: Utility window architecture question
Re: Utility window architecture question
- Subject: Re: Utility window architecture question
- From: Brock Brandenberg <email@hidden>
- Date: Fri, 17 May 2002 15:05:19 -0500
Hi Chris & Ondra.
On Friday, May 17, 2002, at 01:28 PM, Chris Giordano wrote:
Having looked at the OAPreferences framework (in an attempt to see how
they did things while trying to implement something which ended up
being very much like theirs, but it was a really good learning
experience...), the general idea seems to match yours fairly closely --
you create a number of separate preferences objects (the panes), and
there is a controller which handles the loading of the appropriate pane
into the view, etc.
Chris, I've browsed through the regex files in the Omni frameworks, but
haven't been through the OAPreferences yet. Thanks for the tip. You're
right in that I probably won't do a toolbar like is used in preference
panes, but it sounds (from you, Glen, Erik and Ondra) like the view and
controller paradigm is right, so I'll look through the Omni code to
learn some more.
On Friday, May 17, 2002, at 01:30 PM, Ondra Cada wrote:
Why not? I'd do it that way, probably with a middleware support for
automatic adding the panes whenever a bundle containing them is loaded,
and perhaps even with a possibility to tear out a tab into a separate
window like Final Cut Pro does. I do like this kind of distributed
architecture, did it many times myself, and must say that Cocoa/ObjC is
just the ideal environment for such things.
Ondra, tearing out a tab is a great idea. I too like the Adobe
implementations similar to this in Photoshop. Glen suggested using tabs
also (tabless ones at that, which is good because I have limited room
until we get east and west tabs in Cocoa... just need to add icons or
buttons to switch), and it seems like a cleaner and quicker way to swap
views than manually adding/retaining/removing content views.
In all, it sounds like implementing a clean MVC design is the key.
Thanks to this and the Cocoa environment, it makes it almost trivial to
go in any of the suggested UI directions without having to completely
tear up code and rewrite it for each implementation.
Thanks for the help,
Brock
----- industrial design @ bergdesign.com ------
_______________________________________________
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.