Jonas Sicking wrote:
L. David Baron wrote:
This considers the comments in that thread and also eliminates the subdirectories within layout/style/ (which don't have a clear distinction) and distributes the atom lists files to various places.
Moving the atom-lists to their siblingclasses (i.e. xul-atoms should go to the xul code, svg atoms to svg code) sounds like a very good idea. I would prefer if the atomlists lived in mozilla/content/{xul|html|svg}/content, rather then in layout. I tend to think of layout as being built on top of content and that stuff that are used by both of them should live in layout. Of course, this is likly because i mostly work in content :)
content/html/content/public/nsHTMLValue.cpp (or content/base/public/ ?)
content/html/content/src/nsHTMLValue.h (or content/base/src/ ?)
Please move both these to content/html/content/src. This class is being replaced by nsAttrValue which lives there. And neither nsHTMLValue or nsAttrValue is used (or usable) outside of content so no need to put the .h file in public.
Thoughts?
To minimize the pain for developers it might be good to land this sometime in the middle of the alpha cycle. That way people with patches get a chance to land after the tree-freeze, and lets people modify patches before the craze right before the 1.8a freeze.
/ Jonas
-- jst _______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
