On Saturday 2004-03-27 01:02 -0500, Robert O'Callahan wrote:
L. David Baron wrote:
I'm also wondering whether nsHTMLReflowState, nsHTMLReflowMetrics, and nsReflowPath should be in base or generic (for now they're in generic).
I don't really grok the distinction between base and generic. For example, why is nsIFrame in generic and not base? If it was up to me I might make base include everything that you absolutely must use to have a working presentation, and generic include the rest. So generic could include block-and-line, pagination, text, etc, but not nsIFrame and nsFrame themselves.
The idea was that generic contain the basic frame classes and supporting code, while base contain other core things (pres shell, etc.).
Okay, that sounds very reasonable, except that it's hard to have good names for that. Maybe we should just bite the bullet, call "generic" "frames", and do what we can to redirect people looking for the implementation of <FRAME>. They'll need to wise up to our use of 'frame' quickly anyway... With this approach I would put in 'base' probably nsIFrame.h, nsFrame.*, nsSplittableFrame.*, nsContainerFrame.*, and nsHTMLContainerFrame.* (nsHTMLContainerFrame should be merged into nsContainerFrame anyway, IMHO).
Rob _______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
