cvs: php-gtk /docs/en/chapters widget.xml
| From: | Steph Fox | Date: | Mon, 12 Mar 2001 18:56:54 +0000 |
| Subject: | cvs: php-gtk /docs/en/chapters widget.xml | ||
| Groups: | php.gtk | ||
| Request: | Send a blank email to php-gtk+get-711@lists.php.net to get a copy of this message | ||
sfox Mon Mar 12 10:56:54 2001 EDT
Modified files:
/php-gtk/docs/en/chapters widget.xml
Log:
general clean-up
Index: php-gtk/docs/en/chapters/widget.xml
diff -u php-gtk/docs/en/chapters/widget.xml:1.2 php-gtk/docs/en/chapters/widget.xml:1.3
--- php-gtk/docs/en/chapters/widget.xml:1.2 Thu Mar 8 13:16:40 2001
+++ php-gtk/docs/en/chapters/widget.xml Mon Mar 12 10:56:54 2001
@@ -13,21 +13,19 @@
<title>What are Widgets</title>
<simpara>
A Widget is a term used in the world of X for any user interface.
- A Widget can be a text box, label, frames, windows or anything else
- that you might need. GTK Widgets are all derived from the base
+ A Widget can be a text box, label, frames, windows or any GUI component. GTK Widgets are all
derived from the base
class <literal>GtkWidget</literal>.
</simpara>
<simpara>
- From a programmers point of view a widget has five parts to
- its life cycle.
+ From a programming point of view a widget has five parts to
+ its life cycle:
</simpara>
<para>
<orderedlist>
<listitem>
<simpara>Creation</simpara>
<simpara>
- In PHP-GTK terms this is all done in the creation of
- an object, e.g.
+ In php-gtk this is done by creating an object, e.g.
<literal>$window = &new GtkWindow;</literal>
</simpara>
</listitem>
@@ -36,33 +34,30 @@
<simpara>
This is the step of adding a widget to a
<link linkend="gtk.containers.whatare">container</link>.
- This is achived in php-gtk by
- <literal>$container->add($widget)</literal>
+ This is achived in php-gtk by using the syntax
+ <literal>$container->add($widget);</literal>
</simpara>
</listitem>
<listitem>
<simpara>Signal Connection</simpara>
<simpara>
- This is the step of setting up call back functions for use
- when various signals are sent by GTK+. an example of this
+ This is the step of setting up call back functions for use. An example of this
might be <literal>
- $widget->connect("focus-in-event","my_focus_func")</literal>
+
$widget->connect("focus-in-event","my_focus_func");</literal> where
'focus-in-event' is a predefined state such as 'clicked' and
'my_focus_func' is the called subroutine.
</simpara>
</listitem>
<listitem>
<simpara>Display</simpara>
<simpara>
- This section is the actual time when the widget is on display
- to the user, this is started by calling
- <literal>$widget->show()</literal> and is finished by
- <literal>$widget->hide()</literal>.
+ This describes whether the widget is on display to the user. It is started by calling
+ <literal>$widget->show();</literal> and finished by
+ <literal>$widget->hide();</literal>.
</simpara>
</listitem>
<listitem>
<simpara>Destruction</simpara>
<simpara>
- This occurs when your program is shut down, all actions that
- are necessary here are handled by PHP-GTK itself.
+ This occurs when the shutdown routine is called. All actions that are necessary here are
handled by php-gtk itself.
</simpara>
</listitem>
</orderedlist>
@@ -74,10 +69,10 @@
<simpara>
A container is simply a
<link linkend="gtk.widgets.whatare">widget</link>
- that can contain another widget, examples of these are
+ that can contain another widget. Examples of these are
<literal>GtkWindow</literal>, <literal>GtkTable</literal>
- and <literal>GtkBox</literal> other than this fact they are
- exactly the same as widgets. They are all derived from the
+ and <literal>GtkBox</literal>. Other than this property they are
+ exactly the same as widgets. They are derived from the
<literal>GtkContainer</literal> base class, which itself is
derived from the <literal>GtkWidget</literal> class.
</simpara>