Greg or John, can you re-post the entire original message? -T
On Wed, Mar 18, 2009 at 9:07 AM, Greg Brown <[email protected]> wrote: > Moving discussion to pivot-dev - John, you should subscribe to this list if > you have not already done so. > >>There's plenty of cool inner classes, but there are too many inner classes. >>And the ApplicationContext$DisplayHost (family) are first class examples of >>the kind that really should not be inner classes. They're too heavy .. > > As much as I appreciate the feedback, I don't share your perspective on inner > classes. :-) Moving DisplayHost out of pivot.wtk would introduce problems, > as it currently relies on access to protected methods within that package. It > also shares private members of ApplicationContext. > > There's nothing inherently "heavy" about inner classes - it really is just > another namespace, with some different rules about member access. > >>Dropping the heavier inner classes would be a cheap and easy way to cut the >>pivot learning curve by ten or twenty percent.. > > FYI, DisplayHost is only public for historical reasons - it could (and > probably should) be protected. It is not meant to be used by application > developers. > > Greg > >
