Re: Application Architecture or approach
Re: Application Architecture or approach
- Subject: Re: Application Architecture or approach
- From: Louis Demers <email@hidden>
- Date: Wed, 11 Feb 2009 20:27:42 -0500
On 11-Feb-09, at 20:20 , Kyle Sluder wrote:
On Wed, Feb 11, 2009 at 8:07 PM, Louis Demers <email@hidden>
wrote:
Now, I need to rewrite the app so that it can talk to multiple
devices. I
want to use bindings and write as little code as possible 8-) I'm
considering an NSDocument based Applications and using panels/
palettes to
display status and controls (100's) Each device will be represented
by a
different document.
If the concept is to control lots of devices at a time, then I would
hesitate to use the NSDocument architecture. Instead, I'd use a
plugin architecture, where each device's code and interface is stored
in a separate bundle inside your bundle's PlugIns folder. You can
then enumerate these for choosing to display certain interfaces.
I Had not thought about plugins because all the devices are identical
in capabilities. The devices are complex cameras. I wanted to have
each cameras have it document window to display the specific video
feed, but a single palette to control the brightness/zoom of the
frontmost window/camera. This is an over simplification because in
reality, each camera has lots of controls and status. If each camera/
device has its own exclusive gui element, the screen will be cluttered
beyond acceptable. I was modeling my solution around something like
Photoshop or Illustrator where multiple documents use the same set of
palettes.
Louis Demers eng.
www.obzerv.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden