Good morning, Am 11.11.2011 um 23:36 schrieb Henry Maddocks: > On 12/11/2011, at 10:07 AM, Timo Springmann <t...@orangeorb.de> wrote: >> class AnotherController < NSWindowController >> def windowNibName() >> return "Another" >> end >> end > > From a code point of view what you have done here is correct, one controller > per window (view), the rails paradigm is similar to cocoa. > But from a UI point of view this isn't very Mac like. Mac apps tend to have > the list and detail views in panes in the same window, a split view. Look at > mail.app, message list down one side, message details on the other side.
To stay with your Mail.app example: when you create a new mail you do this in a new window (at least in Mail.app from Snow Leopard, don't know about Lion). As my data will have many attributes I would like to open a new window to enter all the details. I've also planned a "preview pane", where you can see the objects details when you select them in the TableView. I think one controller per window is fine. What I don't like about the code is the windowNibName method. Do I really have to do it this way? Or is there a better way to 'connect' my in IB designed window to my ruby contoller class? Regards, Timo -- twitter.com/orangeorb _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
