/usr/share/mozart/doc/wp/node15.html is in mozart-doc 1.4.0-8ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>4.1 Widgets and Parcels</TITLE><LINK href="ozdoc.css" rel="stylesheet" type="text/css"></HEAD><BODY><TABLE align="center" border="0" cellpadding="6" cellspacing="6" class="nav"><TR bgcolor="#DDDDDD"><TD><A href="node14.html">- Up -</A></TD><TD><A href="node16.html#section.geometry.pack">Next >></A></TD></TR></TABLE><DIV id="section.geometry.intro"><H2><A name="section.geometry.intro">4.1 Widgets and Parcels</A></H2><P> A geometry manager computes the size and location of widgets, that is the geometry, and displays the widgets on the screen. The geometry manager computes the geometry according to the widget hierarchy. During computation of the geometry, the manager takes the following three things into account: </P><OL type="1"><LI><P>The geometry requested by slave widgets. Widgets like labels and messages request just enough space to displays their text or bitmap. </P></LI><LI><P>The geometry requested by master widgets. Usually master widgets do not request an explicit geometry. But for example, if a frame widget is initialized with explicit values for width and height, the geometry manager takes these values into account. </P></LI><LI><P>The options given to the geometry manager. </P></LI></OL><P> </P><DIV class="apropos"><P class="margin">parcels</P><P> The geometry manager computes for each slave of a master widget a so-called <A name="label138"></A><EM>parcel</EM>. The parcel is a rectangle and describes the space and the position computed for the slave. From the slaves' parcels the manager computes the parcel for the master. If the master does not request a specific geometry on its own, the manager will assign the master a parcel that encloses all slave parcels. Otherwise the geometry manager distributes the space in the parcel for the master to the slave parcels. This may shrink or grow the parcels for the slaves. </P></DIV><P> Options to the geometry manager affect usually the way how parcels are computed and how widgets are put into their parcels, if the parcels are larger (or smaller) than the parcel initially requested by the widget. </P><P> <A name="label139"></A><A name="label140"></A><A name="label141"></A>In the following we will show the two most important geometry managers which are provided in Tk. One is the packer, which can be used for simple arrangements, like placing several widgets in a row or in a line. The other geometry manager we will discuss is implemented by the <CODE>grid</CODE> command. As the name suggests, the grid command allows for arranging widgets in a grid-like fashion. </P><P> It is perfectly possible to mix geometry managers in a single toplevel widget provided that all slaves of a master are managed by the same manager. For example, suppose a toplevel widget that contains two frames which contain widgets themselves. Both frames must be managed by the same manager. The widgets in the frames can be managed by two different managers. </P><P> We discuss only the most important options these two managers provide, a complete description can be found in <A href="../tcltk/TkCmd/pack.htm"><KBD>pack</KBD></A> and <A href="../tcltk/TkCmd/grid.htm"><KBD>grid</KBD></A>. More information on the packer can also be found in <A href="bib.html#ousterhout.94">John Ousterhout's book</A> in Chapter 17. </P></DIV><TABLE align="center" border="0" cellpadding="6" cellspacing="6" class="nav"><TR bgcolor="#DDDDDD"><TD><A href="node14.html">- Up -</A></TD><TD><A href="node16.html#section.geometry.pack">Next >></A></TD></TR></TABLE><HR><ADDRESS><A href="http://www.ps.uni-sb.de/~schulte/">Christian Schulte</A><BR><SPAN class="version">Version 1.4.0 (20110908185330)</SPAN></ADDRESS></BODY></HTML>
|