Dear Kirk: While I probably won't be using that in my current project, it sounds like a good idea and I will probably look into it if I ever have a need...
On 4/5/09 6:33 AM, "Kirk Kerekes" <[email protected]> wrote: > Along with threads and various asynchronous techniques already > mentioned, you should also consider creating a separate UI-less > "foundation tool" to perform your lengthy task, controlled with NSTask > in your main app. This yields all of the benefits of a thread, with > none of the threading pitfalls. Getting real-time feedback (for a > progress indicator, for example) from the task is more complex than > with a thread, and getting result data back is slightly more involved, > but the absolute freedom from threading issues is often worth it. > > Several of Apple's utility apps are constructed as a UI shell that > invokes one or more tools. > > > _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
