On Jan 8, 2011, at 10:30 PM, Niclas Hedhman wrote: > On Sun, Jan 9, 2011 at 9:01 AM, Greg Brown <gk_br...@verizon.net> wrote: > >>> This means just dropping 'final' from a few classes in wtk, and providing >>> sample Java codes in a separate tutorial(sample) for pure Java developer >>> using the builder styles GUI construction so that users can easily copy and >>> pastes from it. >> >> Agreed on dropping the final modifier. If you are willing to volunteer the >> time to create such examples, that would be great. > > Designing for inheritance is tricky for future compatibility, and > plainly dropping final is IMHO not a good approach. Let usecase drive > the need, and seek delegation/behavior patterns instead, which will be > much more robust in the long run.
There are select cases where the final modifier is being used but not strictly needed, and these are preventing developers from fully utilizing the builder pattern calathus has suggested. Other classes (such our our "structs") would remain final. G
