Once you have the design, then write the code that works for each event. It is a standard technique for event-driven programs.
There are two main frames of the message editor. The top frame displays the control panel. It is as wide as the browser allows and it has a fixed height sufficient to contain all of the controls.The top panel subdivided into a left and right section. The left just displays the last font color used. It is a fixed width. The right contains all of the controls and extends to the edge of the screen.
And the second frame will hold the text box where the message edited. Like the other frame, the width is the same as the screen. Its height is variable, taking up the remainder of the vertical space.
It makes it easier to refer to a property in another frame accurately. You don't need to know the relative relationship between frames since they are each a child of the parent.
It described as a system of ownership, and, even then, the analogy is not exact. For example, a window that creates another window could think of as the parent of the new window. However, if you try to refer to the original window from the child by saying parent.someobject, it will not work.
It is also responsible for responding to global window events. The Navigator is not a visual object. You cannot see it. You only interact with it through its visual construct: its windows.
Most Navigator window components manipulated in a yes/no fashion at the time of window creation. These include the menu, button bar, location display, status display, history list display, and scroll bars. At the time of window creation, you can determine whether the window resized as well as find its dimensions.
It might seem like a significant restriction. By rewriting the document, however, you can change the contents of a window. This technique enables you to modify the values of form elements, the content of the status bar, the position of the pointer in the history list, and the location at any time.