>From looking at the examples and tutorials, I found that most of them deal >with combined WTKX files using includes. I think that approach may not scale >to large application with a number of developers working on separate pieces. >Ideally, I would like to use MVC style design similar to Apple's Cocoa >development where Nib files that are equivalent to WTKX files are associated >with each View/Controller. For example, I might have a root controller that is >responsible for showing initial view (with menus/menu-buttons) and then have >different controllers for various views. When user clicks on some action, it >would then load the controller and load the view from the WTKX files. I am >curious how other folks actually manage WTKX files for large applications >especially when working with multiple developers so that they don't step on >each other's work. Thanks.
______________________________________________ See http://www.peak6.com/email_disclaimer.php for terms and conditions related to this email
