115310 - Block and Line Layout need to be fully documented

Status: RESOLVED INVALID

(Developer Documentation Graveyard :: Mozilla Platform, defect)

Description

[Marc Attinasi]

Block and line layout is a difficult area that is not well documented. We need
to document it to make it more penetrable and to better understand where its
strengths and weaknesses are.

Comment 1

[Marc Attinasi]

Attachment: Layout Documentation Overview

This is an overview of the documentation strategy I plan to use for documenting
the design of layout (block and line initially). This is a work In Progress -
comments and criticisms are welcome.

Comment 2

[Marc Attinasi]

Attachment: Dummy Class Diagram..

for reference in the High Level design Template (WIP)

Comment 3

[Marc Attinasi]

Attachment: High Level Design Template

A template to be used for High Level Design documents (WIP)

Comment 4

[Marc Attinasi]

P1 --> 098

Comment 5

[Alexandru Savulov]

For those interested, there is a complete spec of UML to find under:

http://www.rational.com/uml/resources/documentation/index.jsp

Comment 6

[Marc Attinasi]

Attachment: Detailed Design Template

Simple template for Layout Detailed Designs (WIP)

Comment 7

[Marc Attinasi]

I'm working on sample designs for the Space Manager now. I will attach them as
they are completed. They should have been in this week, but I got sick and
progress was slowed as I reallocated my internal resources to fight the invading
army of evil, terrorizing microbes.  Stay tuned, I am hoping to do some of this
over the Holiday, family willing.

Comment 8

[Marc Attinasi]

Attachment: SpaceManagerClasses.gif

Comment 9

[Marc Attinasi]

Attachment: Space Manager Class Diagram UML source file (DOME)

Comment 10

[Chris Waterson]

What's DOME?

Comment 11

[Marc Attinasi]

DOME is a free UML editor: http://www.htc.honeywell.com/dome/

How the diagrams are generated is not important, but I wanted to include the
DOME source file in case it needs future edits.

Comment 12

[Marc Attinasi]

Attachment: Space Manager High Level Design - for review and sanity check, and as a possible example

Comment 13

[Chris Waterson]

Wow; looks great. Is a bug the best place to keep this stuff? Why not just check
it all in on gila under html/newlayout/doc? (Or, if you want it in the source
tree, under mozilla/layout/doc?)

Comment 14

[Marc Attinasi]

I think the source tree is a good place.  I'm putting up the Space Manger docs
here, along with the templates, to get the format ironed out.  Once all
interested parties are happy with 'em, we should move them to the source tree,
and /mozilla/layout/doc sounds like a good spot.

CC'ing dbaron in hopes he can review the Space Manger HLD.

Also, I'd like to get a short list of bite-sized topics we should start working
on documenting.  I am going finishing up the Detailed Design of the Space
Manager first, but it is short.

A couple candidates for the short-list:

* Frame Constructor (probably several sub-topics rather than one biggie)
* Block Frame (ugh, this is a big one too)
* LineBox / line_iterator
* State Recovery / Margin Collapsing
* Debugging facilities

Comment 15

[Marc Attinasi]

Also, once we move the docs to the source tree we need to update Mozilla.org
with a doc that points to some LXR links or something, I think, or maybe even
mirror them to Mozilla.org periodically.

Comment 16

[Bernd]

Marc, I understand your preference for the source tree but, I would recommend to
put them on gila, this would at least ease a little bit the pain (shame) of
having only old and outdated layout documentation there.

Comment 17

[Chris Waterson]

We shouldn't get too hung up on where these docs go: it's trivial to point from
a page on gila to an LXR page that is the HTML doc.

Marc, the block code might not be too awful if we break it out into the
component objects:

  nsBlockReflowState
  nsBlockReflowContext
  nsLineLayout
    PerSpanData
    PerFrameData
  nsLineBox
    nsLineList
    nsLineList_iterator
  nsFloaterCache
    nsFloaterCacheList
    nsFloaterCacheFreeList

To get coverage, we'll probably need to also do these:

  nsInlineFrame
  nsHTMLReflowState

and to a lesser degree:

  nsAbsoluteContainingBlock
  nsContainerFrame
  nsFrame
  nsHTMLContainerFrame
  nsHTMLReflowCommand
  nsTextFrame

Comment 18

[Bernd]

I volunteer for the debugging facilities.

Comment 19

[Marc Attinasi]

Attachment: Detailed Design of Space Manager

Comment 20

[Marc Attinasi]

I have moved the templates and space manager docs to the /mozilla/layout/doc
directory.  The docs that previously lived there are woefully out of date and
have been moved to /mozilla/layout/doc/obsolete

If you start working on a doc, first check the index file in /mozilla/layout/doc
to see if somebody is already working on that, or has already done it.  Put a
link to the doc in the 'Works In Progress' section to signal to others that you
are working on it too.

As new documents are added to the tree, update the index file in
/mozilla/layout/doc to point to the new doc. 

We'll need to get the Mozilla site to link to these docs - I'll look into the
gila systems 'cause I don't know anything about it.

Comment 21

[Marc Attinasi]

Bulk push to next milestone

Comment 22

[Marc Attinasi]

Removing milestone as this is a recurring task

Comment 23

[Håkan Waara]

Marc, would you obsolete the files you've already checked in / uploaded?  Thanks.

Comment 24

[Alexandru Savulov]

Marc?.... Maaaaarc!... Duuude, where are ya!...

error line 1: dude not found!

Comment 25

[Alexandru Savulov]

hwaara:

you want the files removed from CVS? marc does not work for netscape anymore (he
cannot read the mail since this was an employee account) so i think i will take
over this bug .

taking

Comment 26

[Håkan Waara]

No, no, why would I want that!  I meant obsolete the attachments in bugzilla, as
I didn't know if any of these documents were still pending review or whatever.

Comment 27

[Alexandru Savulov]

ah, ok. i wasn't sure. well, the problem is that this was meant to be a
collection bug for all kind of doc pieces as we thougth to go along and write
them. unfrotunately nobody found enough time to do this so the whole thig got
stuck. there is now a new documentation effort started by jkeiser and me.
jkeiser is working now with alex vincent on a larger issue, though jkeiser will
limit his activity to gecko and alex vincent tries to do the organizational work
in order to get a unified collection of documents covering not only the
developer documentation but also the embedder doc, web-author doc and so on.
check n.p.m.documentation for more information.

Comment 28

[Daniel Wang]

-> documentation

Comment 29

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

->block&line

Comment 30

[Mike Shaver (:shaver emeritus)]

Pretty sure dbaron meant what he said when he assigned the bug in comment 29, so I'm putting it back there.  (It can stay in this product/component, I suppose, though I find the "severity: critical" labeling to be somewhat lol-worthy in the context of MDC.)

Comment 31

[John Karahalis [:openjck]]

Automatically closing all bugs that have not been updated in a while. Please reopen if this is still important to you and has not yet been corrected.

Comment 32

[John Karahalis [:openjck]]

Reopening for review by Sheppy.

Comment 33

[Florian Scholz (Open Web Docs)]

The material here is from 2001. Please reopen if you think this is still relevant or open a new bug that contains a new request/plan for what to document here.