Re: flow of control for sequential data processing
Re: flow of control for sequential data processing
- Subject: Re: flow of control for sequential data processing
- From: Daniel Child <email@hidden>
- Date: Mon, 18 Feb 2008 20:49:57 -0500
Thanks for the suggestion. Sounds brilliant. But I have some
questions about how you'd implement this approach.
First, does such a controller absolutely need an interface, or can it
operate behind the scenes? And if behind the scenes, how would you
load, activate it? Every demo app or tutorial I've seen has a nib-
based app controller. Is it possible to do without one?
Secondly, as it turns out the data I am processing is very large. I
read that in Objective-C you typically pass actual objects rather
than pointers to objects. Is that going to be feasible if I stick it
in a dictionary, or will things bog down?
Thanks.
On Feb 18, 2008, at 4:31 PM, Ricky Sharp wrote:
I would create another (fourth) "master" controller. It's job
would be to manage what step is currently loaded as well as to
manage parameters/results between them. This master controller
could even be your application controller itself. And, if
parameters/results need to be passed around from step to step,
consider using a dictionary.
In my kiosk-style app, I do this quite often where my app
controller loads a particular screen for the user to interact
with. Some screens are "pushed" onto a stack and I thus have
multiple controllers in memory. But, for the most part, stack just
has a single entry; allowing me to effectively swap out controllers
one at a time. I then created a single header with extern
NSStrings to represent the keys into the "parameter" dictionary
passed from screen to screen.
_______________________________________________
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