When set True, each generated web page will use a distinct controller class for defined actions and read/writes. When false, the action logic is generated into the main Task class.
Separate controller classes are recommended if you plan on migrating one or more screens to an alternate source of data and logic than the originating screen(s). When a web page has a separate controller class module, this provides a handle focal point for changing the screen input/output to database and/or web service calls.
Without a separate controller class, the action methods for a screen page can still be easily overridden in the user Task class, but then all the different screen I/O methods will start to pile-up in the single class, making it difficult for developers to extend more than one screen at a time.
Default: false (initialized to true for new UIProject objects)
