The window produced that way is shown on Figure 4.1. Such a browser is called an embedded Browser, compared to a stand-alone Browser using its own toplevel widget.

Figure 4.1: An Embedded Application Browser

Note that when a Browser object is created, either stand-alone or embedded, its window does not appear immediately. This happens when either createWindow or browse methods are applied.

A Browser window can be closed by means of the closeWindow method. Each time a Browser window is closed its buffer is flushed. A Browser object itself can be closed by means of the close method, which deletes its window and frees used by the object memory. A subsequent application of a Browser object closed this way proceeds as it were just created\footnote{This feature is used in the pre-defined Browser, which can be closed many times but never dies. Note that this behavior is not ``re-creating'' since no new Browser object is created immediately.}.

Note that the closeWindow method has no effect for embedded application browsers.

An embedded browser and its frame should be closed by sending the close messages on the Browser object and on the frame object in that sequence. For instance, in our example it would be

Browser objects are controlled by user through the Browser GUI, and by means of application of them to the BrowserClass methods. At the glance, there are the following public methods of a Browser object, where X and Y are certain internal default values: