> 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.
Actually, WTKX includes are intended to help facilitate division of labor across team members. However, earlier versions of Pivot didn't make this quite as easy as it should have been. The Bindable interface (introduced in Pivot 1.4 but improved for Pivot 1.5) makes it much easier to associate WTKX files with "controller code". I'm using it throughout my current app and it is working great. The best example of this right now is probably the 1.5 version of Stock Tracker (specifically, StockTrackerWindow): http://svn.apache.org/repos/asf/pivot/trunk/tutorials/src/org/apache/pivot/tutorials/stocktracker/ I just recently updated the tutorial docs, but they won't be pushed out to the web site until 1.5 is released. In the meantime, feel free to post any questions here. > 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. This isn't something you get "for free" with WTKX includes, but you can easily incorporate it into your app (the Kitchen Sink does something similar). When you need to instantiate your sub-panels, just create a new WTKXSerializer, load your class, and add it to the component hierarchy.
