BOb,
>Actaully, if you look at the way it is done in the new release of codebook by Flash you will see that the inheritence is maintained and the developer is given a place to modify the framework without needing to subclass as much, and loose inheritence.>
I'm familiar with the i-Layer, but I am not sold on it. I would definitely take pause before adding this many extra layers of inheritance to the classes that I am using! In the earlier days of OO programming inheritance was considered a panacea...more modern techniques favor alternative methods..."composition" for example.
As I've said before, we have yet to come across a situation where we have been unable to solve the problem by providing hooks or adding the needed functionality directly to the Framework files.
>If you want the specific problem we have I will outline it... but the above type senerio which adds a developer controlled level for each class would help us alot.>
I'd really like to hear about the scenario you have in mind...
Regards,
Kevin McNeish
Eight-Time .NET MVP
VFP and iOS Author, Speaker & Trainer
Oak Leaf Enterprises, Inc.
Chief Architect, MM Framework
http://www.oakleafsd.com