Author: cmeyer, Chris Meyer, [EMAIL PROTECTED]

This changes the 'ScreenLoader' to load a screen via a public method 
of 'Screen' called 'buildScreen' instead of 'build'. 'buildScreen' is 
a public method that typically would not be overridden for specific 
screens. 'buildScreen' invokes the protected method 'doBuildScreen' 
to build the actual screen. The 'build' method has been deprecated 
but full support for 'build' still remains in order to retain 
backwards compatibility.

The purpose of this change is to add some flexibility to the system 
of building pages so the 'Screen' class can implement behavior common 
to all screens in the system. It also cleans up the code a little and 
makes it easier to read.

One side effect is that the 'build' method was changed away from 
being abstract so there is now no compile-time error for failing to 
define the 'build' method in a Screen derivative. Users should 
override the 'doBuildScreen' method instead anyway. At some point in 
the future, the turbine-gods may decide to drop support for the 
'build' method at which point the 'doBuildScreen' method can be made 
abstract and return the compile-time error checking. Or not.

The naming convention for 'buildScreen' and 'doBuildScreen' was taken 
from the 'Naming conventions' example in the Gang of Four design 
patterns book in the Template pattern. This code follows that pattern.

This same setup and naming convention should be applied to the other 
types of objects in the system like Actions, Pages, Layouts, etc.

The methods are documented using JavaDoc 1.2 style; does the 
community have any preference as to JavaDoc 1.1 or JavaDoc 1.2 style 
JavaDoc stuff?

http://www.ultratask.com/turbine-patches-2000041401.txt



------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to