I have the ability to be brief somewhere; let me see where I've put it ... oh yes, hidden under the expositional style that technical writers adhere to religiously, for fear of being unclear.
1. I'm not asking for documentation. I've just finished a large,
state-of-the-art-documentation project for these XPFE folk.2. I'm not asking for a tutorial cure for difficult-to-learn material. I've attempted a solution to that problem myself, and to the general problem of a lack of mid/high-level info on Mozilla.
3. I'm not asking for full exposure of the layout engine.
All I said originally was, gee, A-F are potential improvements to this broad area of Mozilla for learners, and please don't take away frames as a crutch concept. Please enhance Mozilla to be learnable. I'm happy to debate what of layout should/might be exposed, but I prefer to point to my original set of anecdotal problems as a first list of what to improve.
it. There has been some great work recently at documenting large-scale relationships: e.g. biesi's doc on how non-native content is handled, and jkeiser's great introduction a while back on how HTML is parsed into content and fed into the layout engine.
Could you privately email me where these are? That would be helpful.
regards, Nigel
_______________________________________________ Mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
