My plans for version 4.0 are to make it easier for non-OOP developers to learn. I want to remove the package attribute from all tags and make the class names their full path ( ex: class = "Grandparent.Parent.Child" instead of package = "Grandparent.Parent" class = "Child")
To support this, when a class is registered, it's entire inheritance hierarchy will also be registered rather than its designated superclass. This just makes more sense and is more compliant.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also want to consider integrating DynAPI somehow. I don't want to decrease the performance of the base tags, so it won't be a full integration, but perhaps making it an "logical extension" to cfObjects would be better.
My plans for version 4.0 are to make it easier for non-OOP developers to learn. I want to remove the package attribute from all tags and make the class names their full path ( ex: class = "Grandparent.Parent.Child" instead of package = "Grandparent.Parent" class = "Child")
To support this, when a class is registered, it's entire inheritance hierarchy will also be registered rather than its designated superclass. This just makes more sense and is more compliant.
I also want to consider integrating DynAPI somehow. I don't want to decrease the performance of the base tags, so it won't be a full integration, but perhaps making it an "logical extension" to cfObjects would be better.
Read more about DynAPI at: http://dynapi.sourceforge.net/