On Apr 26, 2011, at 11:55, Oleg Andreev wrote: > 2. Is it a good way to solve the problem? Maybe I miss some subtle issues > with AppKit or user experience.
I'd say the difficulty with this approach is that, at any given moment, there may be a stack of dialogs (of fairly critical importance) but all of them except the top one would be invisible to the user. That means the state and behavior of the application as a whole depends on something(s) that the user simply can't see or deal with directly. Consider (as a concept) the alternative of a single sheet or even modeless window that's a scrollable list of panes, each of which is a dialog requesting some information. -- This would allow the user to see everything that's pending. That seems like a huge win. -- You'd probably need some way of "locking" those that depend on an earlier one, but at least this fact could be shown explicitly. Perhaps the list is hierarchical reflecting the dependencies. -- This would allow the user to respond to the dialogs out of order, dependencies aside. Another huge win IMO. There's 3rd party code out there that can display NSViews as rows in a NSTableView or a NSOutlineView, so implementing a list like this isn't very hard, especially if you use NSViewControllers to manage the pieces. Even if that's not the implementation, a "disclosable" UI concept sounds preferable to what you described. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
