On Aug 4, 2010, at 11:02, Jason Bruce wrote:

> My app is a presentation app for presenting trial exhibits in a court room.  
> The 
> main window of the app would consist of a tab view w/an NSTableView on one 
> tab 
> and an IKImageBrowserView on the second tab -- both bound to the same 
> nsarraycontroller.  The filter window would be for each document only, and 
> would 
> be open just to create filters and then disappear.
> 
> By clicking on a particular image in the image view or on a particular row in 
> the table view, the user could then open a third window with a IKImageView or 
> PDFView showing a particular image or pdf -- which could then be sent to an 
> external display or projector.  
> 
> So, 1 main window per document holding an array of images, with 1 window 
> which 
> may stay open for a period of time to display an image, and another window 
> which 
> will only appear for purposes of creating filters and filter the table and 
> then 
> disappear.  
> 
> So, at this point, if I had two documents open, I want to see 6 windows  (3 
> windows per document); not 1 filter window for all documents.

OK, that makes sense.

FWIW, I'd recommend that your image browser windows and your image display 
window should be document-linked windows, and that the other window should not.

Your document would initially open with its browser window in the normal way. 
There's actually no reason to disallow opening *multiple* image display windows 
for a single document, although your application may have independent reasons 
for limiting this to 1 image. (In that case, it's worth exploring the idea of 
making the image an extra pane of the browser window, rather than a separate 
window, but that's another discussion.) You would use 'addWindowController:' 
and 'removeWindowController:' to link the image window(s) to the document as 
discussed already.

The filter window, since it's short-lived and specific to a single document, is 
probably better off as a sheet rather than a separate window, for UI reasons. 
Aside from that, passing the document as a parameter when creating its window 
controller seems appropriate, and I *wouldn't* suggest linking this window 
controller to the document via 'addWindowController:'.


_______________________________________________

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

Reply via email to