On Saturday 2003-11-15 22:48 -0600, Boris Zbarsky wrote:
I think we could certainly make nsFrameManager a plain non-XPCOM class, though, and just have the prescontext own it...
This seems reasonable to me.
On Monday 2003-11-17 08:44 -0500, Robert O'Callahan wrote:
How about we make nsIPresContext be the got-it-all interface that frames pass around. Pour nsIFrameManager into it. Create nsIPresentation or
I'm not sure why you'd want to "pour" nsIFrameManager into it. If you have a bunch of related functions (and data -- the primary frame map and the undisplayed map), why not keep them separate?
The overhead of fetching it through an indirection, and the hassle of remembering which interface the methods are defined on. Although we could make nsFrameManager a direct member of nsPresContext and return a pointer to it with "nsFrameManager* FrameManager() { return &mFrameManager; }" to get rid of all overhead.
What are we going to do about situations like nsIView/nsView? Should we just move everything from nsView into nsIView, then do a massive search+replace rename of nsIView to nsView and then remove the vestigial nsView?
Rob
_______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
