[gnome-devel-docs] Remove trailing white space.
- From: Tiffany Antopolski <antopolski src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-devel-docs] Remove trailing white space.
- Date: Thu, 19 Apr 2012 16:00:44 +0000 (UTC)
commit 5bf3cc188503d1c02f1f3c2db7382b8416d5a875
Author: Tiffany Antopolski <tiffany antopolski gmail com>
Date: Thu Apr 19 11:44:54 2012 -0400
Remove trailing white space.
platform-demos/C/GtkApplication.vala.page | 4 +-
platform-demos/C/aboutdialog.vala.page | 2 +-
platform-demos/C/beginner.js.page | 2 +-
platform-demos/C/button.js.page | 2 +-
platform-demos/C/button.vala.page | 2 +-
platform-demos/C/dialog.vala.page | 2 +-
platform-demos/C/entry.js.page | 14 +++++-----
platform-demos/C/entry.vala.page | 4 +-
platform-demos/C/getting-ready.page | 6 ++--
platform-demos/C/grid.js.page | 2 +-
platform-demos/C/guitar-tuner.cpp.page | 30 +++++++++++-----------
platform-demos/C/guitar-tuner.js.page | 22 ++++++++--------
platform-demos/C/helloWorld.js.page | 10 ++++----
platform-demos/C/helloworldautotools.js.page | 4 +-
platform-demos/C/image-viewer.js.page | 22 ++++++++--------
platform-demos/C/messagedialog.vala.page | 2 +-
platform-demos/C/record-collection.js.page | 10 ++++----
platform-demos/C/toolbar.js.page | 2 +-
platform-demos/C/toolbar.vala.page | 2 +-
platform-demos/C/treeview.c.page | 2 +-
platform-demos/C/treeview.js.page | 2 +-
platform-demos/C/treeview.py.page | 2 +-
platform-demos/C/treeview.vala.page | 2 +-
platform-demos/C/weatherApp.js.page | 8 +++---
platform-demos/C/weatherAppMain.js.page | 30 +++++++++++-----------
platform-demos/C/weatherAutotools.js.page | 18 +++++++-------
platform-demos/C/weatherGeonames.js.page | 34 +++++++++++++-------------
platform-demos/C/widget.c.page | 2 +-
platform-demos/C/widget.js.page | 2 +-
platform-demos/C/widget.py.page | 2 +-
platform-demos/C/widget.vala.page | 2 +-
platform-demos/C/window.js.page | 2 +-
platform-demos/C/window.vala.page | 4 +-
33 files changed, 128 insertions(+), 128 deletions(-)
---
diff --git a/platform-demos/C/GtkApplication.vala.page b/platform-demos/C/GtkApplication.vala.page
index 569bcc7..1ee723a 100644
--- a/platform-demos/C/GtkApplication.vala.page
+++ b/platform-demos/C/GtkApplication.vala.page
@@ -10,7 +10,7 @@
<email>desrt desrt ca</email>
<years>2012</years>
</credit>
-
+
<credit type="author">
<name>Tiffany Antopolski</name>
<email>tiffany antopolski gmail com</email>
@@ -36,7 +36,7 @@
</tr>
</table>
<p>A demonstration of the menu integration.</p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
//A window in the application
public class Window : Gtk.ApplicationWindow {
diff --git a/platform-demos/C/aboutdialog.vala.page b/platform-demos/C/aboutdialog.vala.page
index 6028e20..c066e6a 100644
--- a/platform-demos/C/aboutdialog.vala.page
+++ b/platform-demos/C/aboutdialog.vala.page
@@ -24,7 +24,7 @@
<media type="image" mime="image/png" src="media/aboutdialog.png"/>
<p>An AboutDialog example using Gtk.Application</p>
<note><p><em style="bold">You need to be running Gtk3.4 or later for this to work</em></p></note>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
//A window in the application
public class Window : Gtk.ApplicationWindow {
diff --git a/platform-demos/C/beginner.js.page b/platform-demos/C/beginner.js.page
index 76f1933..92ae31e 100644
--- a/platform-demos/C/beginner.js.page
+++ b/platform-demos/C/beginner.js.page
@@ -16,7 +16,7 @@
<title>0 Beginner's Tutorials and samples</title>
<p>In these tutorials and samples we use JavaScript and GTK+. These tutorials and samples expect you to be familiar with the syntax of JavaScript, if not, read <link href="http://eloquentjavascript.net/contents.html";>Eloquent JavaScript</link> or your preferred guide to JavaScript. </p>
-
+
<section id="tutorials">
<title>Tutorials</title>
</section>
diff --git a/platform-demos/C/button.js.page b/platform-demos/C/button.js.page
index eda7468..1e39371 100644
--- a/platform-demos/C/button.js.page
+++ b/platform-demos/C/button.js.page
@@ -17,7 +17,7 @@
<title>Button</title>
<media type="image" mime="image/png" src="media/button.png"/>
<p>A button widget that changes its label when you click it.</p>
-
+
<code mime="text/javascript" style="numbered"><![CDATA[
]]>#!/usr/bin/gjs
diff --git a/platform-demos/C/button.vala.page b/platform-demos/C/button.vala.page
index 1130bed..b577883 100644
--- a/platform-demos/C/button.vala.page
+++ b/platform-demos/C/button.vala.page
@@ -18,7 +18,7 @@
<media type="image" mime="image/png" src="media/button.png"/>
<p>A button widget connected to stdout.printf (), and a modal window.</p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
/*callback for the "clicked" signal.*/
void button_clicked_cb () {
diff --git a/platform-demos/C/dialog.vala.page b/platform-demos/C/dialog.vala.page
index b9c18de..bc623a4 100644
--- a/platform-demos/C/dialog.vala.page
+++ b/platform-demos/C/dialog.vala.page
@@ -17,7 +17,7 @@
<title>Dialog</title>
<media type="image" mime="image/png" src="media/dialog.png"/>
<p>A dialog with the response signal hooked up to a callback function.</p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
void on_response (int response_id) {
diff --git a/platform-demos/C/entry.js.page b/platform-demos/C/entry.js.page
index 3b8b12d..e0b0feb 100644
--- a/platform-demos/C/entry.js.page
+++ b/platform-demos/C/entry.js.page
@@ -15,10 +15,10 @@
</info>
<title>Entry widget</title>
-
+
<media type="image" mime="image/png" src="media/entry.png"/>
<p>This an entry widget. An entry widget is a container that you can type in to. </p>
-
+
<code mime="text/javascript" style="numbered"><![CDATA[
#!/usr/bin/gjs
Gtk = imports.gi.Gtk;
@@ -46,7 +46,7 @@ this.resultlabel = new Gtk.Label({
connectionbutton.connect("clicked", function(widget, event) {
//getting the text from the entry widget and updating the label
var whatWasTyped = entry.get_text();
- this.resultlabel.set_text(whatWasTyped);
+ this.resultlabel.set_text(whatWasTyped);
});
grid.attach(label, 1, 1, 1, 1);
@@ -55,10 +55,10 @@ grid.attach_next_to(connectionbutton,label,3,1,1);
grid.attach_next_to(resultlabel,entry,3,1,1);myW.show_all();
Gtk.main();]]></code>
<p>In this sample we use the following widgets:
-<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Window.html";>Gtk.Window</link>,
-<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Grid.html";>Gtk.Grid</link>,
-<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Entry.html";>Gtk.Entry</link>,
-<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Label.html";>Gtk.Label</link>,
+<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Window.html";>Gtk.Window</link>,
+<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Grid.html";>Gtk.Grid</link>,
+<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Entry.html";>Gtk.Entry</link>,
+<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Label.html";>Gtk.Label</link>,
<link href="http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/Gtk.Button.html";>Gtk.Button</link>.</p>
</page>
diff --git a/platform-demos/C/entry.vala.page b/platform-demos/C/entry.vala.page
index 51f8d8d..38605eb 100644
--- a/platform-demos/C/entry.vala.page
+++ b/platform-demos/C/entry.vala.page
@@ -15,10 +15,10 @@
</info>
<title>Entry widget</title>
-
+
<media type="image" mime="image/png" src="media/entry.png"/>
<p>This an entry widget. An entry widget is a container that you can type in to. </p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
]]></code>
diff --git a/platform-demos/C/getting-ready.page b/platform-demos/C/getting-ready.page
index 892c475..3b8ad95 100644
--- a/platform-demos/C/getting-ready.page
+++ b/platform-demos/C/getting-ready.page
@@ -4,9 +4,9 @@
<info>
<link type="guide" xref="index#start"/>
-
+
<desc>Install GNOME development tools</desc>
-
+
<revision pkgversion="0.1" version="0.1" date="2011-03-21" status="review"/>
<credit type="author">
<name>GNOME Documentation Project</name>
@@ -19,7 +19,7 @@
<section id="install">
<title>Install the required tools</title>
<p>Before you can start coding you will have to install the required tools for
-GNOME development on your computer. This shouldn't take you more than ten
+GNOME development on your computer. This shouldn't take you more than ten
minutes.</p>
<section id="auto">
diff --git a/platform-demos/C/grid.js.page b/platform-demos/C/grid.js.page
index 50bff10..c645899 100644
--- a/platform-demos/C/grid.js.page
+++ b/platform-demos/C/grid.js.page
@@ -18,7 +18,7 @@
<media type="image" mime="image/png" src="media/grid.png"/>
<p>A button widget connected to a progress bar.</p>
-
+
<code mime="text/javascript" style="numbered"><![CDATA[
#!/usr/bin/gjs
Gtk = imports.gi.Gtk;
diff --git a/platform-demos/C/guitar-tuner.cpp.page b/platform-demos/C/guitar-tuner.cpp.page
index 62abf14..b365e10 100644
--- a/platform-demos/C/guitar-tuner.cpp.page
+++ b/platform-demos/C/guitar-tuner.cpp.page
@@ -4,9 +4,9 @@
<info>
<link type="guide" xref="index#cpp"/>
-
+
<desc>Use GTKmm and GStreamermm to build a simple guitar tuner application for GNOME. Shows off how to use the interface designer.</desc>
-
+
<revision pkgversion="0.1" version="0.1" date="2011-03-17" status="review"/>
<credit type="author">
<name>GNOME Documentation Project</name>
@@ -61,7 +61,7 @@
<section id="build">
<title>Build the code for the first time</title>
- <p>This is a very basic C++ code setting up GTKmm. More details are given below;
+ <p>This is a very basic C++ code setting up GTKmm. More details are given below;
skip this list if you understand the basics:</p>
<list>
<item>
@@ -125,9 +125,9 @@ six strings) and the orientation to vertical.</p>
<code>Gtk::Main kit(argc, argv);</code> line in <file>main.cc</file>:</p>
<p><code> Gst::init (argc, argv);</code></p>
<p>While we are on it, also make sure that the <file>gstreamermm.h</file> is included in <file>main.cc</file> properly.</p>
-
+
<p>In this simple example we will use a tone generator source called <code>audiotestsrc</code> and send the output to the default system sound device, <code>autoaudiosink</code>. We only need to configure the frequency of the tone generator; this is accessible through the <code>freq</code> property of <code>audiotestsrc</code>.</p>
-
+
<p>To simplify the handling of the pipeline we will define a helper class <code>Sound</code>. We do
that in <file>main.cc</file> in order to keep this example simple, whereas you might usually want
to use a separate file:</p>
@@ -174,8 +174,8 @@ bool Sound::stop_playing()
return false;
}
]]></code>
-
- <p>The code has the following purpose:</p>
+
+ <p>The code has the following purpose:</p>
<steps>
<item>
<p>In the constructor, source and sink GStreamer elements (<code>Gst::Element</code>) are created, and a pipeline element (which will be used as a container for the other two elements). The pipeline is given the name "note"; the source is named "source" and is set to the <code>audiotestsrc</code> source; and the sink is named "output" and set to the <code>autoaudiosink</code> sink (default sound card output). After the elements have been added to the pipeline and linked together, the pipeline is ready to run.</p>
@@ -190,7 +190,7 @@ bool Sound::stop_playing()
any sound output anymore. As GStreamermm uses reference counting through the <code>Glib::RefPtr</code> object, the memory
is automatically freed once the <code>Sound</code> class is destroyed.</p>
</item>
- </steps>
+ </steps>
</section>
<section id="signals">
@@ -198,8 +198,8 @@ bool Sound::stop_playing()
<p>We want to play the correct sound when the user clicks a button. That means that we have to connect
to the signal that is fired when the user clicks the button. We also want to provide information to the
called function which tone to play. GTKmm makes that quite easy as we can easily bind information with the <em>sigc</em>
- library.</p>
-
+ library.</p>
+
<p>The function that is called when the user clicks a button can be pretty simple, as
all the interesting stuff is done in the helper class now:</p>
<code mime="text/x-csrc"><![CDATA[
@@ -212,8 +212,8 @@ on_button_clicked(double frequency, Sound* sound)
<p>It only calls the helper class we defined before to play the correct frequencies. With some more
clever code we would also have been able to directly connect to the class without using the function
but we will leave that to use as an exercise.</p>
-
- <p>The code to set up the signals should be added to the <code>main()</code> function just after the
+
+ <p>The code to set up the signals should be added to the <code>main()</code> function just after the
<code>builder->get_widget("main_window", main_win);</code> line:</p>
<code mime="text/x-csrc"><![CDATA[
Sound sound;
@@ -234,7 +234,7 @@ button->signal_clicked().connect (sigc::bind<double, Sound*>(sigc::ptr_fun(&on_b
</item>
<item>
<p>Finally we connect the <em>clicked</em> signal. This isn't fully straightforward because this is done in a fully type-safe
- way and we actually want to pass the frequency and our helper class to the signal handler.
+ way and we actually want to pass the frequency and our helper class to the signal handler.
<code>sigc::ptr_fun(&on_button_clicked)</code> creates a <em>slot</em> for the <code>on_button_clicked</code> method
we defined above. With <code>sigc::bind</code> we are able to pass additional arguments to the slot and in this
case we pass the frequency (as double) and our helper class.</p>
@@ -242,7 +242,7 @@ button->signal_clicked().connect (sigc::bind<double, Sound*>(sigc::ptr_fun(&on_b
</steps>
<p>Now that we have set up the <em>E</em> button we also need to connect the other buttons according to their frequencies:
440 for A, 587.33 for D, 783.99 for G, 987.77 for B and 1318.5 for the high E. This is done in the same way, just passing
- a different frequency to the handler.</p>
+ a different frequency to the handler.</p>
</section>
<section id="run">
@@ -258,7 +258,7 @@ button->signal_clicked().connect (sigc::bind<double, Sound*>(sigc::ptr_fun(&on_b
<section id="further">
<title>Further Reading</title>
- <p>Many of the things shown above are explained in detail in the
+ <p>Many of the things shown above are explained in detail in the
<link href="http://library.gnome.org/devel/gtkmm-tutorial/stable/";>GTKmm book</link> which also
covers a lot more key concept for using the full power of GTKmm. You might also be interested
in the <link href="http://library.gnome.org/devel/gstreamermm/";>GStreamermm reference documentation</link>.</p>
diff --git a/platform-demos/C/guitar-tuner.js.page b/platform-demos/C/guitar-tuner.js.page
index dc1adfc..bcd2eb0 100644
--- a/platform-demos/C/guitar-tuner.js.page
+++ b/platform-demos/C/guitar-tuner.js.page
@@ -15,10 +15,10 @@
</info>
<title>2 Guitar Tuner</title>
-
+
<synopsis>
<p>In this tutorial we'll construct a small application, Guitar Tuner, using JavaScript and GTK+ and GStreamer. To do and run all the code examples yourself, you need an editor to write code in, terminal and GNOME 3. or higher installed into your computer.</p>
- <list>
+ <list>
<item><p> <link xref="#gstreamer">GStreamer pipelines</link> </p></item>
<item><p> <link xref="#script">Script for running the application</link> </p></item>
<item><p> <link xref="#imports">Libraries to import</link> </p></item>
@@ -28,7 +28,7 @@
<item><p> <link xref="#connecting">Connecting buttons to playSound</link> </p></item>
<item><p> <link xref="#guitarjs">The whole program</link> </p></item>
<item><p> <link xref="#terminal">Running the application form Terminal</link> </p></item>
- </list>
+ </list>
</synopsis>
<p>After reading this tutorial, you should see this in your screen:</p>
<media type="image" mime="image/png" src="media/guitar-tuner.png"/>
@@ -45,7 +45,7 @@
<title>Script for running the application</title>
<code mime="text/javascript" style="numbered"><![CDATA[
#!/usr/bin/gjs]]></code>
- <p> This line tells how to run the script. It needs to be the first line of the code and it needs to be executable. To get the execution rights go to terminal and run in right folder: chmod +x scriptname. Or you can use the graphical filemanager. Just go to the right folder where your code is, right click you code file, choose properties, click the permissions tab and check the box for allow executing file as a program
+ <p> This line tells how to run the script. It needs to be the first line of the code and it needs to be executable. To get the execution rights go to terminal and run in right folder: chmod +x scriptname. Or you can use the graphical filemanager. Just go to the right folder where your code is, right click you code file, choose properties, click the permissions tab and check the box for allow executing file as a program
</p>
</section>
<section id="imports">
@@ -58,7 +58,7 @@ const Mainloop = imports.mainloop;]]></code>
<p>In order to have a working program we need to import a few GObject Introspection -libraries to our use. For working UI, we need Gtk and for Gstreamer to work we need Gst. These are imported in the beginning so we have them at use everywhere. Also in the beginning we import a construct Mainloop to handle the timeout to be used with the tuning sounds.</p>
</section>
<section id="mainwindow">
- <title>Creating the main window for the application</title>
+ <title>Creating the main window for the application</title>
<code mime="text/javascript" style="numbered"><![CDATA[
Gtk.init(null, 0);
Gst.init(null, 0);
@@ -105,14 +105,14 @@ function playSound(frequency){
var pipeline = new Gst.Pipeline({name: "note"});
var source = new Gst.ElementFactory.make("audiotestsrc","source");
var sink = new Gst.ElementFactory.make("autoaudiosink","output");
-
+
source.set_property('freq', frequency);
pipeline.add(source);
pipeline.add(sink);
source.link(sink);
pipeline.set_state(Gst.State.PLAYING);
- Mainloop.timeout_add(500, function () {
+ Mainloop.timeout_add(500, function () {
pipeline.set_state(Gst.State.PAUSED);
return false;
});
@@ -177,14 +177,14 @@ function playSound(frequency){
var source = new Gst.ElementFactory.make("audiotestsrc","source");
var sink = new Gst.ElementFactory.make("autoaudiosink","output");
-
+
source.set_property('freq', frequency);
pipeline.add(source);
pipeline.add(sink);
source.link(sink);
pipeline.set_state(Gst.State.PLAYING);
- Mainloop.timeout_add(500, function () {
+ Mainloop.timeout_add(500, function () {
pipeline.set_state(Gst.State.PAUSED);
return false;
});
@@ -232,6 +232,6 @@ Gtk.main();]]></code>
<title>Reference Implementation</title>
<p>If you run into problems with the tutorial, compare your code with this <link href="guitar-tuner/guitar-tuner.js">reference code</link>.</p>
</section>
-
-
+
+
</page>
diff --git a/platform-demos/C/helloWorld.js.page b/platform-demos/C/helloWorld.js.page
index ffcf3b1..07bfd78 100644
--- a/platform-demos/C/helloWorld.js.page
+++ b/platform-demos/C/helloWorld.js.page
@@ -24,8 +24,8 @@
<item><p> <link xref="#label">Label for the window</link> </p></item>
<item><p> <link xref="#js">helloWorld.js</link> </p></item>
<item><p> <link xref="#terminal">Running the application form Terminal</link> </p></item>
- </list>
-
+ </list>
+
</synopsis>
<p>After taking this tutorial, you should see this on your screen:</p>
<media type="image" mime="image/png" src="media/helloWorldJs.png"/>
@@ -35,7 +35,7 @@
#!/usr/bin/gjs]]></code>
<p>This needs to be the first line of your script, because it tells GNOME that we'll be using Gjs -- the JavaScript bindings for GNOME -- in order to run it.</p>
</section>
-
+
<section id="imports">
<title>Libraries to import</title>
<code mime="text/javascript" style="numbered"><![CDATA[
@@ -44,7 +44,7 @@ var Gtk = imports.gi.Gtk;]]></code>
</section>
<section id="mainwindow">
- <title>Creating the main window for the application</title>
+ <title>Creating the main window for the application</title>
<code mime="text/javascript" style="numbered"><![CDATA[
// Initialize GTK+
Gtk.init(null, 0);
@@ -58,7 +58,7 @@ mywindow.connect("destroy", function(){Gtk.main_quit()});
]]></code>
<p>After importing Gtk, we need to initialize it. After that, we can start building our first window. We do this by creating a variable called mywindow and assigning it a new Gtk.Window of type TOPLEVEL.</p> <p>After setting up our first window we'll give the window a property called title. The title can be any string you want it to be. To be on the safe side, it's best to stick to UTF-8 encoding.</p> <p>The next thing we need to do for our application is connect the close button that's automatically generated along with the window to the close functionality. That happens with the method connect(). When the close button is pressed it gives out the signal "destroy", so in this part we're connecting the "destroy" signal to function(){Gtk.main_quit()}, which does the actual closing.</p><p>Now we have a window that has a title and a working "close" button. Let's add the actual "Hello, world" text.</p>
</section>
-
+
<section id="label">
<title>Label for the window</title>
<code mime="text/javascript" style="numbered"><![CDATA[
diff --git a/platform-demos/C/helloworldautotools.js.page b/platform-demos/C/helloworldautotools.js.page
index a5d46e2..d0d3af4 100644
--- a/platform-demos/C/helloworldautotools.js.page
+++ b/platform-demos/C/helloworldautotools.js.page
@@ -21,7 +21,7 @@
<item><p>autogen.sh</p></item>
<item><p>Makefile.am</p></item>
<item><p>configure.ac</p></item>
- <item><p>README</p></item>
+ <item><p>README</p></item>
</list>
<p>autogen.sh</p>
<code mime="text/sh" style="numbered"><![CDATA[
@@ -38,7 +38,7 @@ bin_SCRIPTS = helloworld.js
EXTRA_DIST= \
$(bin_SCRIPTS)
-# The desktop files
+# The desktop files
desktopdir = $(datadir)/applications
desktop_DATA = helloworld.desktop]]></code>
<p>configure.ac</p>
diff --git a/platform-demos/C/image-viewer.js.page b/platform-demos/C/image-viewer.js.page
index b02c741..28c8746 100644
--- a/platform-demos/C/image-viewer.js.page
+++ b/platform-demos/C/image-viewer.js.page
@@ -3,11 +3,11 @@
id="image-viewer.js">
<info>
-
+
<link type="guide" xref="index#js"/>
-
+
<desc>A little bit more than a simple "Hello world" application - write an image viewer in GTK. Includes an introduction to the JavaScript language.</desc>
-
+
<revision pkgversion="0.1" version="0.1" date="2011-03-19" status="review"/>
<credit type="author">
<name>Jonh Wendell</name>
@@ -16,8 +16,8 @@
<credit type="author">
<name>Johannes Schmid</name>
<email>jhs gnome org</email>
- </credit>
-
+ </credit>
+
</info>
<title>1 Image Viewer</title>
@@ -87,7 +87,7 @@ MyClass.prototype = {
print (this.propertyA);
print (this.propertyB);
}
-
+
}]]></code>
<p>This defines a class called <code>MyClass</code>. Let's go through each part of the class definition:</p>
<steps>
@@ -117,7 +117,7 @@ o.aMethod ("Hello", "world");
o.propertyA = "Just changed its value!";
o.dumpProperties ();]]></code>
<p>This code creates a new instance of the class called <code>o</code>, runs <code>aMethod</code>, changes <code>propertyA</code> to a different string, and then calls <code>dumpProperties</code> (which outputs the fields).</p>
- <p>Save the code in the <file>main.js</file> and then run it by using
+ <p>Save the code in the <file>main.js</file> and then run it by using
<guiseq><gui>Run</gui><gui>Execute</gui></guiseq> from the menu or using the toolbar.</p>
</section>
@@ -146,9 +146,9 @@ Gtk.main ();]]></code>
<item><p>The next line explicitly shows the window. In Gtk, every widget is hidden by default.</p></item>
<item><p>Finally, <code>Gtk.main</code> runs the main loop — in other words, it executes the program. The main loop listens for events (signals) from the user interface and then calls a signal handler which will do something useful. We'll learn more about signals shortly.</p></item>
</list>
-
+
<p>Save the code in <file>main.js</file> and run it. You will notice that the application does not quit when you close the window. This is because we haven't set up a signal handler to deal with the window's <code>destroy</code> (close) signal yet. We'll do this shortly, but for now you can just hit <keyseq><key>Ctrl</key><key>C</key></keyseq> in the terminal window to quit the program.</p>
-
+
</section>
<section id="classes2">
@@ -196,7 +196,7 @@ object.connect (<signal_name>, <function_to_be_called>);]]></code>
<code mime="text/javascript"><![CDATA[
b.connect ("clicked", function () { print ("you clicked me!"); });]]></code>
</note>
-
+
</section>
<section id="close">
@@ -264,7 +264,7 @@ open_button.connect ("clicked", Lang.bind (this, this._openClicked));]]></code>
chooser.add_button (Gtk.STOCK_CANCEL, 0);
chooser.add_button (Gtk.STOCK_OPEN, 1);
chooser.set_default_response (1);
-
+
var filter = new Gtk.FileFilter ();
filter.add_pixbuf_formats ();
chooser.filter = filter;
diff --git a/platform-demos/C/messagedialog.vala.page b/platform-demos/C/messagedialog.vala.page
index 9d6a640..6002bd6 100644
--- a/platform-demos/C/messagedialog.vala.page
+++ b/platform-demos/C/messagedialog.vala.page
@@ -17,7 +17,7 @@
<title>MessageDialog</title>
<media type="image" mime="image/png" src="media/messagedialog.png"/>
<p>A modal message dialog which can cause the world to explode.</p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
void dialog_response (int response_id) {
switch (response_id) {
diff --git a/platform-demos/C/record-collection.js.page b/platform-demos/C/record-collection.js.page
index d752844..4cb6c13 100644
--- a/platform-demos/C/record-collection.js.page
+++ b/platform-demos/C/record-collection.js.page
@@ -4,9 +4,9 @@
<info>
<link type="guide" xref="index#js"/>
-
+
<desc>Create a small database application for ordering your music collection</desc>
-
+
<revision pkgversion="0.1" version="0.1" date="2011-02-22" status="review"/>
<credit type="author">
<name>GNOME Documentation Project</name>
@@ -15,7 +15,7 @@
<credit type="author">
<name>Johannes Schmid</name>
<email>jhs gnome org</email>
- </credit>
+ </credit>
</info>
<title>3 Record Collection</title>
@@ -104,7 +104,7 @@ Gtk.main ();]]></code>
<code mime="text/javascript" style="numbered"><![CDATA[
setupWindow: function () {
this.window = new Gtk.Window ({title: "Data Access Demo", height_request: 350});
- this.window.connect ("delete-event", function () {
+ this.window.connect ("delete-event", function () {
Gtk.main_quit();
return true;
});
@@ -250,7 +250,7 @@ Gtk.main ();]]></code>
if (!this._validateFields ())
return;
- // Gda.execute_non_select_command (this.connection,
+ // Gda.execute_non_select_command (this.connection,
// "insert into demo values ('" + this.id_entry.text + "', '" + this.name_entry.text + "')");
var b = new Gda.SqlBuilder ({stmt_type:Gda.SqlStatementType.INSERT});
diff --git a/platform-demos/C/toolbar.js.page b/platform-demos/C/toolbar.js.page
index 919c3c4..1362cf1 100644
--- a/platform-demos/C/toolbar.js.page
+++ b/platform-demos/C/toolbar.js.page
@@ -18,7 +18,7 @@
<media type="image" mime="image/png" src="media/toolbar.png"/>
<p>Toolbar is a widget that may contain either text or stock icons. In this sample we use stock icons.</p>
-
+
<code mime="text/javascript" style="numbered"><![CDATA[
#!/usr/bin/gjs
Gtk = imports.gi.Gtk;
diff --git a/platform-demos/C/toolbar.vala.page b/platform-demos/C/toolbar.vala.page
index b282f5c..216f0d1 100644
--- a/platform-demos/C/toolbar.vala.page
+++ b/platform-demos/C/toolbar.vala.page
@@ -18,7 +18,7 @@
<media type="image" mime="image/png" src="media/toolbar.png"/>
<p>Toolbar is a widget that may contain either text or stock icons. In this sample we use stock icons.</p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
]]></code>
diff --git a/platform-demos/C/treeview.c.page b/platform-demos/C/treeview.c.page
index 5c0c1ba..146ba42 100644
--- a/platform-demos/C/treeview.c.page
+++ b/platform-demos/C/treeview.c.page
@@ -17,7 +17,7 @@
<title>TreeView widget</title>
<media type="image" mime="image/png" src="media/widget.png"/>
<p>More specific description of this particular example.</p>
-
+
<code mime="text/x-csrc" style="numbered"><![CDATA[
]]></code>
diff --git a/platform-demos/C/treeview.js.page b/platform-demos/C/treeview.js.page
index 53b2bca..f03cde1 100644
--- a/platform-demos/C/treeview.js.page
+++ b/platform-demos/C/treeview.js.page
@@ -17,7 +17,7 @@
<title>TreeView widget</title>
<media type="image" mime="image/png" src="media/widget.png"/>
<p>More specific description of this particular example.</p>
-
+
<code mime="text/javascript" style="numbered"><![CDATA[
]]></code>
<p>
diff --git a/platform-demos/C/treeview.py.page b/platform-demos/C/treeview.py.page
index c6a94e9..101c6e1 100644
--- a/platform-demos/C/treeview.py.page
+++ b/platform-demos/C/treeview.py.page
@@ -17,7 +17,7 @@
<title>TreeView widget</title>
<media type="image" mime="image/png" src="media/widget.png"/>
<p>More specific description of this particular example.</p>
-
+
<code mime="text/x-python" style="numbered"><![CDATA[
]]></code>
<p>
diff --git a/platform-demos/C/treeview.vala.page b/platform-demos/C/treeview.vala.page
index cefa25b..8d47d74 100644
--- a/platform-demos/C/treeview.vala.page
+++ b/platform-demos/C/treeview.vala.page
@@ -17,7 +17,7 @@
<title>TreeView widget</title>
<media type="image" mime="image/png" src="media/widget.png"/>
<p>More specific description of this particular example.</p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
]]></code>
diff --git a/platform-demos/C/weatherApp.js.page b/platform-demos/C/weatherApp.js.page
index f59cdf6..6b66289 100644
--- a/platform-demos/C/weatherApp.js.page
+++ b/platform-demos/C/weatherApp.js.page
@@ -12,23 +12,23 @@
</credit>
<desc> How to plan an application that uses asynchronous calls. Asynchronous calls will be presented through a weather application.
- </desc>
+ </desc>
</info>
<title>4 Weather Application</title>
<synopsis>
<p>In this guide well construct a weather application using asynchronous calls. Weather information in this example is fetched from geonames.org and the application is using the <link href= "http://en.wikipedia.org/wiki/List_of_airports_by_ICAO_code:_E";>ICAO codes </link> to place your weather request. To write and run all the code examples yourself, you need an editor to write code in, Terminal and GNOME 3 or higher installed into your computer. In this guide we we'll go through the following parts:</p>
-
+
<list>
<item><p> <link xref="#planningUi">Planning the graphical user interface</link></p></item>
<item><p> <link xref="#asynchronous">Asynchronous calls</link></p></item>
<item><p> <link xref="#main">The main program file</link></p></item>
<item><p> <link xref="#main">Local library GeoNames</link></p></item>
<item><p> <link xref="#main">Autotools and Icons</link></p></item>
- </list>
+ </list>
</synopsis>
-
+
<p>After reading this tutorial, you should see this in your screen:</p>
<media type="image" mime="image/png" src="media/weatherAppJs.png"/>
diff --git a/platform-demos/C/weatherAppMain.js.page b/platform-demos/C/weatherAppMain.js.page
index 2b19617..5c191b8 100644
--- a/platform-demos/C/weatherAppMain.js.page
+++ b/platform-demos/C/weatherAppMain.js.page
@@ -16,7 +16,7 @@
<title>The main program file</title>
<synopsis>
- <p>In this part of the guide well construct the main program file of the weather application. To write and run all the code examples yourself, you need an editor to write code in, Terminal and GNOME 3 or higher installed into your computer. In this part we we'll go through the following parts:</p>
+ <p>In this part of the guide well construct the main program file of the weather application. To write and run all the code examples yourself, you need an editor to write code in, Terminal and GNOME 3 or higher installed into your computer. In this part we we'll go through the following parts:</p>
<list>
<item><p> <link xref="#script">Script for running the application</link> </p></item>
<item><p> <link xref="#imports">Libraries to import</link> </p></item>
@@ -25,16 +25,16 @@
<item><p> <link xref="#asynccall">Requesting the weather information asynchronously</link></p></item>
<item><p> <link xref="#connectingbuttons">Connecting signals to button and entry."></link></p></item>
<item><p> <link xref="#weatherapp.js">weatherapp.js</link></p></item>
- </list>
+ </list>
</synopsis>
<section id="script">
<title>Script for running the application</title>
<code mime="text/javascript" style="numbered"><![CDATA[
#!/usr/bin/gjs]]></code>
- <p> This line tells how to run the script. It needs to be the first line of the code and it needs to be executable. To get the execution rights go to Terminal and run in right folder: chmod +x scriptname. Or you can use the graphical filemanager. Just go to the right folder where your code is, right click you code file, choose properties, click the permissions tab and check the box for allow executing file as a program
+ <p> This line tells how to run the script. It needs to be the first line of the code and it needs to be executable. To get the execution rights go to Terminal and run in right folder: chmod +x scriptname. Or you can use the graphical filemanager. Just go to the right folder where your code is, right click you code file, choose properties, click the permissions tab and check the box for allow executing file as a program
</p>
</section>
-
+
<section id="imports">
<title>Libraries to import</title>
<code mime="text/javascript" style="numbered"><![CDATA[
@@ -44,7 +44,7 @@ const WeatherService = imports.geonames;]]></code>
</section>
<section id="mainwindow">
- <title>Creating the main window for the application</title>
+ <title>Creating the main window for the application</title>
<code mime="text/javascript" style="numbered"><![CDATA[
// Initialize the gtk
Gtk.init(null, 0);
@@ -69,7 +69,7 @@ var weatherIcon = new Gtk.Image();
//Set some labels to your window
var label1 = new Gtk.Label({label: ""});
-var label2 = new Gtk.Label({label: "Looking in the sky..."});
+var label2 = new Gtk.Label({label: "Looking in the sky..."});
var label3 = new Gtk.Label({label: ""});
var entry = new Gtk.Entry();
@@ -88,7 +88,7 @@ grid.attach_next_to(weatherIcon,label2,1,1,1)
]]></code>
<p>In this section we create the grid we are going to use for positioning the widgets. All the buttons, labels and entrys are initialized and placed on the grid. As seen from the placing of the different widgets, they don't need to be related only to one widget. At this point some of the labels don't have any content. The content for those widgets is applied later. If you run the application at this stage, you have the UI ready, but the widgets are not connected to anything. For this we need to first build the weather searching local library, and then get the information we need asynchronously. When we have our local library ready we can connect it to the necessary widgets.</p>
</section>
-
+
<section id="asynccall">
<title>Requesting the weather information asynchronously</title>
<code mime="text/javascript" style="numbered"><![CDATA[
@@ -99,11 +99,11 @@ function getWeatherForStation() {
GeoNames.getWeather(function(error, weather) {
//this here works bit like signals. This code will be run when we have weather.
- if (error) {
+ if (error) {
label2.set_text("Suggested ICAO station does not exist Try EFHF");
return; }
weatherIcon.file = GeoNames.getIcon(weather);
-
+
label1.set_text("Temperature is " + weather.weatherObservation.temperature + " degrees.");
if (weather.weatherObservation.weatherCondition !== "n/a"){
label2.set_text("Looks like there is " + weather.weatherObservation.weatherCondition + " in the sky.");
@@ -118,7 +118,7 @@ function getWeatherForStation() {
]]></code>
<p>This function is dedicated for calling for the weather information and updating labels and icons accordingly. In the beginning of the function we get the user input for the search. So here for the first time we use our own library and assign it to variable GeoNames. While assigning WeatherService we give it the station. The firs thing we do with GeoNames is to request weather. Everything after GeoNames.getWeather(function(error, weather) happens only if we either get an error message or weather information. If either doesn't come, the rest of the program works as normal, so main_Quit works.</p>
</section>
-
+
<section id="connectingbuttons">
<title>Connecting signals to button and entry.</title>
<code mime="text/javascript" style="numbered"><![CDATA[
@@ -134,8 +134,8 @@ button1.connect("clicked", function(){
getWeatherForStation();
});]]></code>
<p>And finally we have the connections that make the whole application run as it should. We connect both the entry and the button to do the same thing, getting the weather. So it doesn't matter weather you press enter of click the search button.</p>
- </section>
-
+ </section>
+
<section id ="weatherapp.js">
<title>Weatherapp.js</title>
<p> Weatherapp.js file looks like this:</p>
@@ -162,7 +162,7 @@ var weatherIcon = new Gtk.Image();
//Set some labels to your window
var label1 = new Gtk.Label({label: ""});
-var label2 = new Gtk.Label({label: "Looking in the sky..."});
+var label2 = new Gtk.Label({label: "Looking in the sky..."});
var label3 = new Gtk.Label({label: ""});
var grid = new Gtk.Grid();
@@ -196,11 +196,11 @@ function getWeatherForStation() {
GeoNames.getWeather(function(error, weather) {
//this here works bit like signals. This code will be run when we have weather.
- if (error) {
+ if (error) {
label2.set_text("Suggested ICAO station does not exist Try EFHF");
return; }
weatherIcon.file = GeoNames.getIcon(weather);
-
+
label1.set_text("Temperature is " + weather.weatherObservation.temperature + " degrees.");
if (weather.weatherObservation.weatherCondition !== "n/a"){
label2.set_text("Looks like there is " + weather.weatherObservation.weatherCondition + " in the sky.");
diff --git a/platform-demos/C/weatherAutotools.js.page b/platform-demos/C/weatherAutotools.js.page
index 5961f8e..d55fd8c 100644
--- a/platform-demos/C/weatherAutotools.js.page
+++ b/platform-demos/C/weatherAutotools.js.page
@@ -17,25 +17,25 @@
<title>Autotools and Icons</title>
<synopsis>
<p>In this part of the guide well construct the autotools and custom icons needed for weather application to be a seamless part of your desktop. To write and run all the code examples yourself, you need an editor to write code in, Terminal and GNOME 3 or higher installed into your computer. In this guide we we'll go through the following parts:</p>
-
+
<list>
<item><p><link xref="#autotools"> Autotools</link></p></item>
<item><p><link xref="#icons">Custom icons for your application</link></p></item>
- </list>
+ </list>
</synopsis>
-
+
<section id ="autotools">
<title>Autotools and necessary files</title>
- <p>Having more than one file in your folder makes using autotools a bit tricky. You need the .desktop file, autogen.sh, Makefile.am, configure.ac and as a new file: myapp.sh.in file. Hacking the autotools file is a complicated field. More information can be found in many different sources, <link href="http://en.wikipedia.org/wiki/GNU_build_system";>the wikipedia article</link> provides a good overwiev on the subject.
- </p>
+ <p>Having more than one file in your folder makes using autotools a bit tricky. You need the .desktop file, autogen.sh, Makefile.am, configure.ac and as a new file: myapp.sh.in file. Hacking the autotools file is a complicated field. More information can be found in many different sources, <link href="http://en.wikipedia.org/wiki/GNU_build_system";>the wikipedia article</link> provides a good overwiev on the subject.
+ </p>
<list>
<item><p>weatherapp.desktop</p></item>
<item><p>weatherapp.sh.in</p></item>
<item><p>Makefile.am</p></item>
<item><p>configure.ac</p></item>
- <item><p>autogen.sh</p></item>
+ <item><p>autogen.sh</p></item>
</list>
<p>weatherapp.desktop</p>
<code mime="text/.desktop" style="numbered"><![CDATA[
@@ -71,7 +71,7 @@ EXTRA_DIST= \
CLEANFILES =
-# The desktop files
+# The desktop files
desktopdir = $(datadir)/applications
desktop_DATA =weatherapp.desktop
@@ -112,7 +112,7 @@ private_icons = \
weather-showers-scattered.svg \
weather-snow.svg \
$(NULL)
-
+
install-icons:
for icon in $(private_icons); do \
mkdir -p $(DESTDIR)$(pkgdatadir)/icons/; \
@@ -144,7 +144,7 @@ autoreconf --force --install]]></code>
<p>When thinking about custom icons a good rule of thumb is: do you expect to see that icon used elsewhere or is it private to your app? If the first (e.g. the icons in the desktop file that are shown by the shell) then you need /usr/share/hicolor, otherwise (e.g. the weather icons of your app) /usr/share/$application/bla/bla</p>
<p>Using autotools you have to make some changes to your .desktop and Makefile.am files. In the desktop file you change the Icon's name Icon=weather-icon. In the Makefile.am file you add these two lines to the end of your application #the application icon</p>
<p>appicondir=$(datadir)/icons/hicolor/scalable/apps</p>
- <p>appicon_DATA=weather-icon.svg</p>
+ <p>appicon_DATA=weather-icon.svg</p>
</section>
</page>
diff --git a/platform-demos/C/weatherGeonames.js.page b/platform-demos/C/weatherGeonames.js.page
index e96d278..7ecf277 100644
--- a/platform-demos/C/weatherGeonames.js.page
+++ b/platform-demos/C/weatherGeonames.js.page
@@ -17,15 +17,15 @@
<title>Local library geoNames</title>
<synopsis>
<p>In this part of the guide well construct the local library geoNames using asynchronous calls. Weather information in this example is fetched from geonames.org and the application is using the <link href= "http://en.wikipedia.org/wiki/List_of_airports_by_ICAO_code:_E";>ICAO codes </link> to place your weather request. To write and run all the code examples yourself, you need an editor to write code in, Terminal and GNOME 3 or higher installed into your computer. In this guide we we'll go through the following parts:</p>
-
+
<list>
<item><p> <link xref="#geonamesimports">Local library for getting the weather</link></p></item>
<item><p> <link xref="#geonamesfunction">Creating function geoNames</link></p></item>
<item><p> <link xref="#geonamesmethods">Methods for geoNames</link></p></item>
<item><p> <link xref="#geonames.js">geonames.js </link></p></item>
- </list>
+ </list>
</synopsis>
-
+
<section id="geonamesimports">
<title>Local library for getting the weather</title>
<p>For this we need a new file that will be our local library.</p>
@@ -36,7 +36,7 @@ Soup.Session.prototype.add_feature.call(_httpSession, new Soup.ProxyResolverDefa
]]></code>
<p>In the first lines we'll import and initialize the libraries we need to use in this local library. Soup handles all the requests we have to make with http.</p>
</section>
-
+
<section id="geonamesfunction">
<title>Creating function GeoNames</title>
<code mime="text/javascript" style="numbered"><![CDATA[
@@ -44,13 +44,13 @@ function GeoNames(station) {
this.station = station;
}
-GeoNames.prototype = {
-
+GeoNames.prototype = {
+
}
]]></code>
<p>Here we create the function GeoNames that will handle getting weather for us. JavaScript allows us to create functions that have little inside at first and later expand them. This will be done inside the GeoNames.prototype curly braces{}</p>
</section>
-
+
<section id="geonamesmethods">
<title>Methods for GeoNames</title>
<code mime="text/javascript" style="numbered"><![CDATA[
@@ -65,8 +65,8 @@ getWeather: function(callback) {
var weather = JSON.parse(weatherJSON);
callback(null, weather);
});
-},
-
+},
+
getIcon: function(weather){
switch (weather.weatherObservation.weatherCondition){
case "drizzle":
@@ -75,9 +75,9 @@ getIcon: function(weather){
return "weather-showers-scattered.svg";
case "rain":
return "weather-showers.svg";
- case "light snow":
+ case "light snow":
case "snow grains":
- return "weather-snow.svg";
+ return "weather-snow.svg";
}
switch (weather.weatherObservation.clouds){
case "few clouds":
@@ -94,7 +94,7 @@ getIcon: function(weather){
]]></code>
<p>The first method for GeoNames is getWeather and the second getIcon. In getWeather we make a http request with soup, handle errors and then parse the information from the request to form we can use it. In getIcon we simply compare the results we got from getWeather to the switch we have in order to get the icon matching current weather. Now that we have our local library ready, it's time to make use of it.</p>
</section>
-
+
<section id ="geonames.js">
<title>geonames.js</title>
@@ -108,7 +108,7 @@ function GeoNames(station) {
this.station = station;
}
-GeoNames.prototype = {
+GeoNames.prototype = {
getWeather: function(callback) {
var request = Soup.Message.new('GET', 'http://api.geonames.org/weatherIcaoJSON?ICAO=' + this.station + '&username=demo');
_httpSession.queue_message(request, function(_httpSession, message) {
@@ -120,8 +120,8 @@ GeoNames.prototype = {
var weather = JSON.parse(weatherJSON);
callback(null, weather);
});
- },
-
+ },
+
getIcon: function(weather){
switch (weather.weatherObservation.weatherCondition){
case "drizzle":
@@ -130,9 +130,9 @@ GeoNames.prototype = {
return "weather-showers-scattered.svg";
case "rain":
return "weather-showers.svg";
- case "light snow":
+ case "light snow":
case "snow grains":
- return "weather-snow.svg";
+ return "weather-snow.svg";
}
switch (weather.weatherObservation.clouds){
case "few clouds":
diff --git a/platform-demos/C/widget.c.page b/platform-demos/C/widget.c.page
index 0fede3b..9a6354d 100644
--- a/platform-demos/C/widget.c.page
+++ b/platform-demos/C/widget.c.page
@@ -17,7 +17,7 @@
<title>Generic widget</title>
<media type="image" mime="image/png" src="media/widget.png"/>
<p>More specific description of this particular example.</p>
-
+
<code mime="text/x-csrc" style="numbered"><![CDATA[
]]></code>
<p>
diff --git a/platform-demos/C/widget.js.page b/platform-demos/C/widget.js.page
index 6cddc21..0c418bd 100644
--- a/platform-demos/C/widget.js.page
+++ b/platform-demos/C/widget.js.page
@@ -17,7 +17,7 @@
<title>Generic widget</title>
<media type="image" mime="image/png" src="media/widget.png"/>
<p>More specific description of this particular example.</p>
-
+
<code mime="text/javascript" style="numbered"><![CDATA[
]]></code>
<p>
diff --git a/platform-demos/C/widget.py.page b/platform-demos/C/widget.py.page
index 8f67ab8..229292c 100644
--- a/platform-demos/C/widget.py.page
+++ b/platform-demos/C/widget.py.page
@@ -17,7 +17,7 @@
<title>Generic widget</title>
<media type="image" mime="image/png" src="media/widget.png"/>
<p>More specific description of this particular example.</p>
-
+
<code mime="text/x-python" style="numbered"><![CDATA[
]]></code>
<p>
diff --git a/platform-demos/C/widget.vala.page b/platform-demos/C/widget.vala.page
index 1f98c2e..ef9c45e 100644
--- a/platform-demos/C/widget.vala.page
+++ b/platform-demos/C/widget.vala.page
@@ -17,7 +17,7 @@
<title>Generic widget</title>
<media type="image" mime="image/png" src="media/widget.png"/>
<p>More specific description of this particular example.</p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
]]></code>
<p>
diff --git a/platform-demos/C/window.js.page b/platform-demos/C/window.js.page
index 485118b..ddd61be 100644
--- a/platform-demos/C/window.js.page
+++ b/platform-demos/C/window.js.page
@@ -17,7 +17,7 @@
<title>Window</title>
<media type="image" mime="image/png" src="media/window.png"/>
<p>A plain window, without other widgets added to it.</p>
-
+
<code mime="text/javascript" style="numbered"><![CDATA[
]]>#!/usr/bin/gjs
diff --git a/platform-demos/C/window.vala.page b/platform-demos/C/window.vala.page
index a7b3c71..d137951 100644
--- a/platform-demos/C/window.vala.page
+++ b/platform-demos/C/window.vala.page
@@ -17,7 +17,7 @@
<title>Window</title>
<media type="image" mime="image/png" src="media/window.png"/>
<p>A toplevel window with destroy signal hooked up.</p>
-
+
<code mime="text/x-vala" style="numbered"><![CDATA[
int main (string[] args) {
@@ -57,7 +57,7 @@ int main (string[] args) {
<item><p>The enum <link href="http://references.valadoc.org/#!api=gtk+-3.0/Gtk.WindowPosition";>Gtk.WindowPosition</link></p></item>
- <item><p>The method <link href="http://www.valadoc.org/#!api=gtk+-3.0/Gtk.Window.set_default_size";>set_default_size</link></p></item>
+ <item><p>The method <link href="http://www.valadoc.org/#!api=gtk+-3.0/Gtk.Window.set_default_size";>set_default_size</link></p></item>
<item><p><link href="http://valadoc.org/#!api=gtk+-3.0/Gtk.Container.border_width";>border_width</link></p></item>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
