Re: Dependent NSOperations (and best practices)
Re: Dependent NSOperations (and best practices)
- Subject: Re: Dependent NSOperations (and best practices)
- From: Ronny Reichmann <email@hidden>
- Date: Mon, 4 Aug 2008 22:07:14 +0200
Hello Andrew,
...
While dependent operations may produce a particular behavior, or be
configurable to produce certain behaviors, what behavior would be a
best practice from a UI and user-experience perspective?
In my eyes you should keep it simple for the users sake. The algorithm
and the processing of it's associated log are both belonging to the
same task in the users point of view. Executing a queue of such tasks
can be made visible very cleanly. In this order, even canceling a task
can just be done in one logical way. Or canceling the whole queue. But
splitting everything up leads to big confusion. You should think about
the reason why you "need“ to split it up and why you "need“ to make it
visible in behavior/interface. Are there any benefits at all?
Cheers,
Ron_______________________________________________
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