To manage the methods exposed in the RBScripts you either expose everything in a single class or you break up the methods into separate classes that are all linked through inheritance. The latter way allows you to break up the functionality into functional blocks that are easier to manage, but the price is that you can't easily cross share bits and pieces of the functionality between different instances of RBScripts that require different sets of functionality in the context object. So with the ability to use multiple context objects, we could easily create and manage generic context objects that could be reused without having to worry where in the inheritance chain to link the class. Thus multiple context objects would greatly reduce the maintenance aspect of using context objects. This would naturally spawn the reuse of a ton of independent context objects which could be just dropped into programs. People could then write and share contexts objects that independently expose parts of the RB built-in libraries etc.
Yes, but it's still much more work than should be necessary to expose classes, built in stuff, etc.
-- Joe Ranieri _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
