Home > Tutorials : XUL Tutorial : 7.4 - Box Objects

Previous Next

## Box Objects

This section describes the box object, which holds display and layout related information about a XUL box as well as some details about XUL layout.

### About Mozilla Layout

Mozilla divides things into two sets of trees, the content tree and the layout tree. The content tree stores the nodes as they are found in the source code. The layout tree holds a different tree of nodes for each individual component that can be displayed. The layout tree holds the structure as the nodes are expected to be displayed There is not necessarily a one to one relationship between content and layout nodes. Some content nodes may have several layout objects, for example, each line of a paragraph has a separate layout object. Conversely, some content nodes have no layout objects at all. For instance, the key element doesn't have any layout objects since it isn't displayed in any way. Similarly, any element that has been hidden will not have a layout object either.

The DOM is generally used only to get and modify information pertaining to the content or structure of the document. It's relatively simple to determine what kind of content tree node will be created for a given element. A XUL element, for example, will have a XULElement type of content node.

The layout objects that will be created are determined in a more complex manner. Various pieces of information are used such as the tag name, the attributes on an element, various CSS properties, the elements and layout objects around the element, and the XBL associated with an element (XBL is described in a later section). Unless you change the style for an element, most XUL elements will usually use the box layout object or one of its subtypes. Recall that all XUL elements are types of boxes, that is the box is the base of all displayed XUL elements. However, there are a number of subtypes, about 25 or so, for specific XUL elements. Some of these subtypes, such as the stack or listbox are needed for more complex layouts than the basic box, while others such as the button are used only to add extra mouse and key event handling.

The layout object associated with an element can be removed and a completely different type of object created just by changing the CSS display property, among others. For example changing the display property of an button element to block will cause the button layout object to be deleted and a block object to be created instead. Naturally, this will change the appearance and function of the element.

It isn't necessary to know the details of how the layout objects are constructed but it is quite useful to at least have at least the knowledge of what is described above of XUL layout for more advanced XUL development.

### Box Objects

The layout objects are not accessible to the developer for manipulating. They are internal to the XUL layout components. However, XUL provides some helper objects, called box objects, which can provide some layout related information. As the name implies, they are available for all box-based elements.

There are several subtypes of box object, although only a couple of them are generally used. The others have functions which are more easily accessible by methods mapped directly onto the element, since those types are generally only used with one particular element. The base box object, or the interface BoxObject, however, has a number of properties which are quite useful for XUL development.

The base box object has two useful features. First, you can retrieve the position and size of the XUL element as displayed, and second, you can determine the order of the elements in the box as displayed, instead of their order as they are stored in the DOM.

The box object provides four properties, x, y, width and height, for determining the position and size of an element. The x and y coordinates are relative to the top left corner of the document in the window (excluding the window border and title) and are measured in pixels. The width and height properties are also measured in pixels and return the width and height of the element including CSS padding and border, if any.

The values are always the position and sizes as currently displayed, so the values will be different if the element is moved or resized. For example, a flexible element will change in size and the box object dimensions will update accordingly. The following example shows this.

Example 7.4.1: Source View

    <button label="Click Me"
            oncommand="alert('The width is ' + this.boxObject.width);"/>

You can use the width and height attributes to specify the width and height of an element, respectively. Normally, these attributes would not be used so the element would determine a suitable size to fit its contents. Thus, these attributes override the default size and use a specific size. The corresponding width and height properties may be used to adjust the dimensions of an element at any time, if you wish to display an element at a specific size. Retrieving the values of these properties will return the size if it was explicitly specified. Note that these properties will return an empty string if the width or height attributes or properties were not set already. That is, you cannot get the current size with these properties; instead you must use the box object properties.

This may be a bit confusing, but, the key is to remember that the width and height properties on an element return the size that was set in the XUL while the width and height properties of the box object return the current size.

The hidden attribute will hide an element such that it will not be displayed. Since it is not displayed, all four position and size properties of the box object will have the value 0. When an element is hidden, it is removed from the display and the layout objects are removed for it. Thus, since it isn't displayed anywhere, it will have no position or size.

The collapsed attribute will have the same effect to the user element visually, except that it leaves the element on screen and keeps the layout objects intact, but changes the size of the element to 0. This means that while both hidden and collapsed elements have 0 width and height, hidden elements have a x and y position of 0, while collapsed elements will retain their position in the window.

To retrive or modify the hidden or collapsed state use the corresponding properties as in the following example.

Example 7.4.2: Source View

    <script>
    function showPositionAndSize()
    {
      var labelbox = document.getElementById('thelabel').boxObject;

      alert("Position is (" + labelbox.x + "," + labelbox.y +
            ") and size is (" + labelbox.width + "," +
            labelbox.height + ")");
    }
    </script>

    <button label="Hide"
            oncommand="document.getElementById('thelabel').hidden = true;"/>
    <button label="Show"
            oncommand="document.getElementById('thelabel').hidden = false;"/>
    <button label="Collapse"
            oncommand="document.getElementById('thelabel').collapsed = true;"/>
    <button label="Uncollapse"
            oncommand="document.getElementById('thelabel').collapsed = false;"/>
    <button label="Show Position/Size"
            oncommand="showPositionAndSize();"/>
    <label id="thelabel" value="I am a label"/>

Note that if you hide and collapse the label, it will be treated as hidden. You will then have to unhide and uncollapse the label for it to appear again.

### XUL Element Ordering

The box object may also be used to determine the display order of elements, which may not be the same as the order in the source. Recall that DOM properties such as childNodes, firstChild, and nextSibling may be used to navigate the document tree. The box object also allows navigation in a similar means but retrieves the elements in display order.

The box object provides several properties, firstChild, lastChild, nextSibling, previousSibling, and parentBox. Their function should be self explanatory from their names. These properties return elements, for example, the firstChild property returns the first displayed child element. There is no corresponding childNodes property for box navigation; instead you must navigate by sibling using the nextSibling or previousSibling properties.

Unlike with navigating the DOM tree, hidden elements are not included when navigating by box objects. That means that for a box with six children where the first two are hidden, the firstChild property will return the third element. However, collapsed elements are included since they are still displayed but have no size. For example, the next box sibling of button 1 is this next example will be button 3, because button 2 is hidden. But the next box sibling of button 3 will be button 4 because it is only collapsed.

Example 7.4.3: Source View

    <hbox>
      <button label="Button 1"
              oncommand="alert('Next is: ' + this.boxObject.nextSibling.label);"/>
      <button label="Button 2" hidden="true"/>
      <button label="Button 3"
              oncommand="alert('Next is: ' + this.boxObject.nextSibling.label);"/>
      <button label="Button 4" collapsed="true"/>
    </hbox>

When a XUL box is laid out on a window, the elements are ordered according to a number of properties, for instance the orientation, their ordinal group and their direction. The orientation is commonly modified using the orient attribute. There is also a corresponding CSS property -moz-box-orient which may be used instead, depending on the situation. This attribute was explained earlier in the section on boxes.

The ordinal attribute on an element may be used to specify the ordinal group of the element, or you can use the CSS property -moz-box-ordinal-group.

Elements with a lower ordinal value are placed in the box before elements with a higher ordinal value. For example, if one element has an ordinal of 2, it would be placed before an element with ordinal 3 or higher but after one with ordinal 1. The default value if the ordinal is not specified is 1. This means that if you want to change the displayed order of elements, you will often need to adjust the ordinals of several elements.

Adjusting the ordinal of an element is not commonly done as you would usually just place the elements in a different order in the source. It might be used to rearrange items later without adjusting the DOM. The following example demonstrates this.

Example 7.4.4: Source View

    <hbox>
      <button label="One" oncommand="this.ordinal++;"/>
      <button label="Two" oncommand="this.ordinal++;"/>
      <button label="Three" oncommand="this.ordinal++;"/>
    </hbox>

If you press the first button, its ordinal will increase by one, from 1 to 2. It will appear at the end of the row since the other buttons have an ordinal of 1. If you press the second button, its ordinal will increase by one and will be moved to the end of the row. Items with the same ordinal value appear in the same order as in the source. If you then press the button labeled One again, its ordinal will increase to 3 and will move to the end. Finally, pressing the button labeled Three will increase its ordinal to 2 and it will appear in between the other two buttons.

The final box ordering attribute is the dir attribute, or the -moz-box-direction CSS property. If this is set to reverse, all of the children in the box or displayed in reverse order. In a horizontal box, the elements will be displayed from right to left and in a vertical box, the elements will be displayed from bottom to top. Here is an example:

Example 7.4.5: Source View

    <hbox dir="reverse">
      <button label="Left"/>
      <button label="Center"/>
      <button label="Right"/>
    </hbox>

Navigation through the nodes using the box object ordering will return the elements in the order they are displayed accounting for the ordinal adjustments made. Thus, if you change the ordinal of an element, it will have a different position in the box order. Reversing the direction, however, does not change the box order.

(Next) Next, we'll find out how to use XPCOM objects from XUL and scripts.

Examples: 7.4.1 7.4.2 7.4.3 7.4.4 7.4.5

Previous Next

Copyright (C) 1999 - 2004 XulPlanet.com