[gnome-devel-docs] Links should not be split
- From: Marta Maria Casetti <mmcasetti src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-devel-docs] Links should not be split
- Date: Mon, 25 Feb 2013 10:10:06 +0000 (UTC)
commit aa7e39c2097351824483cde5d3895dec875974c0
Author: Marta Maria Casetti <mmcasetti gmail com>
Date: Mon Feb 25 10:57:28 2013 +0100
Links should not be split
Links to other pages in the tutorials for GTK in python should not be split.
platform-demos/C/checkbutton.py.page | 2 +-
platform-demos/C/dialog.py.page | 2 +-
platform-demos/C/entry.py.page | 2 +-
platform-demos/C/fontchooserwidget.py.page | 2 +-
platform-demos/C/linkbutton.py.page | 2 +-
platform-demos/C/radiobutton.py.page | 2 +-
platform-demos/C/switch.py.page | 2 +-
platform-demos/C/textview.py.page | 2 +-
platform-demos/C/togglebutton.py.page | 2 +-
9 files changed, 9 insertions(+), 9 deletions(-)
---
diff --git a/platform-demos/C/checkbutton.py.page b/platform-demos/C/checkbutton.py.page
index 6ca0368..434171c 100644
--- a/platform-demos/C/checkbutton.py.page
+++ b/platform-demos/C/checkbutton.py.page
@@ -34,7 +34,7 @@
<section id="methods">
<title>Useful methods for a CheckButton widget</title>
- <p>For a discussion on signals and callback functions, see <link xref="signals-callbacks.py">this
page</link>.</p>
+ <p>For a discussion on signals and callback functions, see <link xref="signals-callbacks.py" />.</p>
</section>
diff --git a/platform-demos/C/dialog.py.page b/platform-demos/C/dialog.py.page
index 5e43bf2..108993a 100644
--- a/platform-demos/C/dialog.py.page
+++ b/platform-demos/C/dialog.py.page
@@ -34,7 +34,7 @@
<section id="methods">
<title>Useful methods for a Dialog widget</title>
- <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py">this
page</link>.</p>
+ <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py" />.</p>
<list>
<item><p>Instead of <code>set_modal(True)</code> we could have <code>set_modal(False)</code> followed by
<code>set_destroy_with_parent(True)</code> that would destroy the dialog window if the main window is
closed.</p></item>
<item><p><code>add_button(button_text="The Answer", response_id=42)</code>, where <code>42</code> is any
integer, is an alternative to <code>add_button(button_text="text",
response_id=Gtk.ResponseType.RESPONSE)</code>, where <code>RESPONSE</code> could be one of <code>OK, CANCEL,
CLOSE, YES, NO, APPLY, HELP</code>, which in turn correspond to the integers <code>-5, -6,...,
-11</code>.</p></item>
diff --git a/platform-demos/C/entry.py.page b/platform-demos/C/entry.py.page
index 9dd6b8f..e939b7d 100644
--- a/platform-demos/C/entry.py.page
+++ b/platform-demos/C/entry.py.page
@@ -36,7 +36,7 @@
<section id="methods">
<title>Useful methods for an Entry widget</title>
- <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py">this
page</link>. Some of the signals that a Gtk.Entry widget can emit are: <code>"activate"</code> (emitted when
the user activates the Entry key); <code>"backspace"</code> (emitted when the user activates the Backspace or
Shift-Backspace keys); <code>"copy-clipboard"</code> (Ctrl-c and Ctrl-Insert); <code>"paste-clipboard"</code>
(Ctrl-v and Shift-Insert); <code>"delete-from-cursor"</code> (Delete, for deleting a character; Ctrl-Delete,
for deleting a word); <code>"icon-press"</code> (emitted when the user clicks an activable icon);
<code>"icon-release"</code> (emitted on the button release from a mouse click over an activable icon);
<code>"insert-at-cursor"</code> (emitted when the user initiates the insertion of a fixed string at the
cursor); <code>"move-cursor"</code> (emitted when the user initiates a cursor movement);
<code>"populate-popup"</code> (emitted before showin
g the context menu of the entry; it can be used to add items to it).</p>
+ <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py" />. Some
of the signals that a Gtk.Entry widget can emit are: <code>"activate"</code> (emitted when the user activates
the Entry key); <code>"backspace"</code> (emitted when the user activates the Backspace or Shift-Backspace
keys); <code>"copy-clipboard"</code> (Ctrl-c and Ctrl-Insert); <code>"paste-clipboard"</code> (Ctrl-v and
Shift-Insert); <code>"delete-from-cursor"</code> (Delete, for deleting a character; Ctrl-Delete, for deleting
a word); <code>"icon-press"</code> (emitted when the user clicks an activable icon);
<code>"icon-release"</code> (emitted on the button release from a mouse click over an activable icon);
<code>"insert-at-cursor"</code> (emitted when the user initiates the insertion of a fixed string at the
cursor); <code>"move-cursor"</code> (emitted when the user initiates a cursor movement);
<code>"populate-popup"</code> (emitted before showing the context
menu of the entry; it can be used to add items to it).</p>
<list>
<item><p><code>get_buffer()</code> and <code>set_buffer(buffer)</code>, where <code>buffer</code> is a
Gtk.EntryBuffer object, can be used to get and set the buffer for the entry.</p></item>
<item><p><code>get_text()</code> and <code>set_text("some text")</code> can be used to get and set the
content for the entry.</p></item>
diff --git a/platform-demos/C/fontchooserwidget.py.page b/platform-demos/C/fontchooserwidget.py.page
index a10070f..60b51c8 100644
--- a/platform-demos/C/fontchooserwidget.py.page
+++ b/platform-demos/C/fontchooserwidget.py.page
@@ -32,7 +32,7 @@
</section>
<section id="methods">
<title>Useful methods for a FontChooserWidget</title>
- <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py">this
page</link>.</p>
+ <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py" />.</p>
<list>
<item><p>To set the font which is initially selected, use <code>set_font(font)</code> (where
<code>font</code> is the font name) or <code>set_font_desc(font)</code> (where <code>font</code> is the
PangoFontDescription).</p></item>
<item><p>To get the selected font use <code>get_font()</code> or
<code>get_font_desc()</code>.</p></item>
diff --git a/platform-demos/C/linkbutton.py.page b/platform-demos/C/linkbutton.py.page
index 0af095d..df4ea28 100644
--- a/platform-demos/C/linkbutton.py.page
+++ b/platform-demos/C/linkbutton.py.page
@@ -37,7 +37,7 @@
<list>
<item><p><code>get_visited()</code> returns the 'visited' state (<code>True</code> or
<code>False</code>) of the URI where the LinkButton points. The button becomes visited when it is
clicked.</p></item>
<item><p><code>set_visited(True)</code> sets the 'visited' state of the URI where the LinkButton
points as <code>True</code> (analogously for <code>False</code>).</p></item>
- <item><p>Each time the button is clicked, the signal <code>"activate-link"</code> is emitted. For an
explanation of signals and callback functions, see <link xref="signals-callbacks.py">this
page</link>.</p></item>
+ <item><p>Each time the button is clicked, the signal <code>"activate-link"</code> is emitted. For an
explanation of signals and callback functions, see <link xref="signals-callbacks.py" />.</p></item>
</list>
</section>
<section id="references">
diff --git a/platform-demos/C/radiobutton.py.page b/platform-demos/C/radiobutton.py.page
index 09a3260..535097f 100644
--- a/platform-demos/C/radiobutton.py.page
+++ b/platform-demos/C/radiobutton.py.page
@@ -34,7 +34,7 @@
<section id="methods">
<title>Useful methods for a RadioButton widget</title>
- <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py">this
page</link>.</p>
+ <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py" />.</p>
<p>As seen in <link xref="properties.py"/>, instead of <code>button1 = Gtk.RadioButton(label="Button
1")</code> we could create the button and label it with</p>
<code>
diff --git a/platform-demos/C/switch.py.page b/platform-demos/C/switch.py.page
index b481a22..a87efae 100644
--- a/platform-demos/C/switch.py.page
+++ b/platform-demos/C/switch.py.page
@@ -38,7 +38,7 @@
</section>
<section id="methods">
<title>Useful methods for a Switch widget</title>
- <p>For a discussion on signals and callback functions, see <link xref="signals-callbacks.py">this
page</link>.</p>
+ <p>For a discussion on signals and callback functions, see <link xref="signals-callbacks.py" />.</p>
</section>
<section id="references">
diff --git a/platform-demos/C/textview.py.page b/platform-demos/C/textview.py.page
index 76a270a..5fc6c0e 100644
--- a/platform-demos/C/textview.py.page
+++ b/platform-demos/C/textview.py.page
@@ -47,7 +47,7 @@
<section id="methods">
<title>Useful methods for a TextView widget</title>
- <p>Go to <link xref="strings.py.page" /> for an explanation of how to deal with strings and Unicode.</p>
+ <p>Go to <link xref="strings.py" /> for an explanation of how to deal with strings and Unicode.</p>
<p>A <code>Gtk.TextView</code> displays the text stored in a <code>Gtk.TextBuffer</code>. However, most
text manipulation is accomplished with iterators, represented by a <code>Gtk.TextIter</code> - a position
between two characters in the text buffer. Iterators are not valid indefinitely; whenever the buffer is
modified in a way that affects the contents of the buffer, all outstanding iterators become invalid. Because
of this, iterators can’t be used to preserve positions across buffer modifications. To preserve a position,
we use a <code>Gtk.TextMark</code>, that can be set visible with <code>visible(True)</code>. A text buffer
contains two built-in marks; an "insert" mark (the position of the cursor) and the "selection_bound" mark.</p>
<p>Methods for a TextView widget:</p>
<list>
diff --git a/platform-demos/C/togglebutton.py.page b/platform-demos/C/togglebutton.py.page
index 630f80d..2777600 100644
--- a/platform-demos/C/togglebutton.py.page
+++ b/platform-demos/C/togglebutton.py.page
@@ -35,7 +35,7 @@
<section id="methods">
<title>Useful methods for a ToggleButton widget</title>
- <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py">this
page</link>.</p>
+ <p>For an explanation of signals and callback functions, see <link xref="signals-callbacks.py" />.</p>
</section>
<section id="references">
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]