GNOME.org
 

[gnome-devel-docs] tutorials python: menubar

commit 0561011b9ee882f9335647fbcba9db4a131bda36
Author: Marta Maria Casetti <mmcasetti gmail com>
Date:   Thu Aug 2 10:40:43 2012 +0100

    tutorials python: menubar

 platform-demos/C/menubar.py.page    |  182 +++++++++++++++++++++++++++++++++++
 platform-demos/C/samples/menubar.py |  159 ++++++++++++++++++++++++++++++
 platform-demos/Makefile.am          |    4 +-
 3 files changed, 344 insertions(+), 1 deletions(-)
---
diff --git a/platform-demos/C/menubar.py.page b/platform-demos/C/menubar.py.page
new file mode 100644
index 0000000..a4a2bba
--- /dev/null
+++ b/platform-demos/C/menubar.py.page
@@ -0,0 +1,182 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<page xmlns="http://projectmallard.org/1.0/";
+      xmlns:xi="http://www.w3.org/2001/XInclude";
+      type="guide" style="task"
+      id="menubar.py">
+  <info>
+  <link type="guide" xref="beginner.py#menu-combo-toolbar"/>
+  <link type="seealso" xref="aboutdialog.py"/>
+  <link type="seealso" xref="gmenu.py"/>
+    <revision version="0.1" date="2012-08-01" status="stub"/>
+
+    <credit type="author copyright">
+      <name>Tiffany Antopolski</name>
+      <email>tiffany antopolski gmail com</email>
+      <years>2012</years>
+    </credit>
+    <credit type="author coyright">
+      <name>Marta Maria Casetti</name>
+      <email>mmcasetti gmail com</email>
+      <years>2012</years>
+    </credit>
+
+    <desc>A widget which holds GtkMenuItem widgets</desc>
+  </info>
+
+  <title>MenuBar</title>
+  <media type="image" mime="image/png" src="media/menubar.png"/>
+  <p>A MenuBar created using XML and GtkBuilder.</p>
+
+  <links type="section"/>
+
+  <section id="xml"> <title>Create a MenuBar using XML</title>
+   <p>To create the menubar using XML:</p>
+   <steps>
+     <item><p>Create <file>menubar.ui</file> using your favorite text editor.</p></item>
+     <item><p>Enter the following line at the top of the file:</p>
+           <code mime="text"><![CDATA[
+<?xml version="1.0"? encoding="UTF-8"?>]]></code>
+     </item>
+    <item><p>We want to create the interface which will contain our menubar and it's submenus.  Our menubar will contain <gui>File</gui>, <gui>Edit</gui>, <gui>Choices</gui> and <gui>Help</gui> submenus. We add the following XML code to the file:</p>
+    <code mime="text"><xi:include href="samples/menubar_basis.ui" parse="text"><xi:fallback/></xi:include></code>
+     </item>
+     <item><p>Now we will create the .py file and use GtkBuilder to import the <file>menubar.ui</file> we just created.</p></item>
+   </steps>
+   </section>
+
+   <section id="basis"> <title>Add the MenuBar to the window using GtkBuilder</title>
+<code mime="text/x-python"><xi:include href="samples/menubar_basis.py" parse="text"><xi:fallback/></xi:include></code>
+<p>
+Now run the python application. It should look like the picture at the top of this page.</p>
+</section>
+
+<section id="xml2"> <title>Add items to the menus</title>
+<p>We start off by adding 2 menuitems to the <gui>File</gui> menu: <gui>New</gui> and <gui>Quit</gui>.  We do this by adding a <code>section</code> to the the <code>File</code> submenu with these items. The <file>menubar.ui</file> should look like this  (lines 6 to 13 inclusive comprise the newly added section):</p>
+      <code mime="text" style="numbered"><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<interface>
+  <menu id="menubar">
+    <submenu>
+      <attribute name="label">File</attribute>
+      <section>
+        <item>
+          <attribute name="label">New</attribute>
+        </item>
+        <item>
+          <attribute name ="label">Quit</attribute>
+        </item>
+      </section>
+    </submenu>
+    <submenu>
+      <attribute name="label">Edit</attribute>
+    </submenu>
+    <submenu>
+      <attribute name="label">Choices</attribute>
+    </submenu>
+    <submenu>
+      <attribute name="label">Help</attribute>
+    </submenu>
+  </menu>
+</interface>]]></code>
+
+  <p>Following this pattern, you can now add a <code>Copy</code> and a <code>Paste</code> item to the <code>Edit</code> submenu, and an <code>About</code> item to the <code>Help</code> submenu.</p>
+
+  </section>
+
+  <section id="actions">
+    <title>Setup actions</title>
+
+    <p>We now create the actions for "New" and "Quit" connected to a callback function in the Python file; for instance we create "new" as:</p>
+    <code>
+new_action = Gio.SimpleAction.new("new", None)
+new_action.connect("activate", self.new_callback)</code>
+
+    <p>And we create the callback function of "new" as</p>
+    <code>
+def new_callback(self, action, parameter):
+    print "You clicked \"New\""</code>
+
+    <p>Now, in the XML file, we we connect the menu items to the actions in the XML file by adding the "action" attribute:</p>
+    <code><![CDATA[
+<item>
+  <attribute name="label">New</attribute>
+  <attribute name="action">app.new</attribute>
+</item>]]></code>
+
+    <p>Note that for an action that is relative to the application, we use the prefix <code>app.</code>; for actions that are relative to the window we use the prefix <code>win.</code>.</p>
+
+    <p>Finally, in the Python file, we add the action to the application or to the window - so for instance <code>app.new</code> will be added to the application in the method <code>do_startup(self)</code> as</p>
+    <code>
+self.add_action(new_action)</code>
+
+  </section>
+
+  <section id="win-app"><title>Actions: Application or Window?</title>
+    <p>Above, we created the "new" and "open" actions as part of the MyApplication class. Actions which control the application itself, such as "quit" should be created similarly.</p>
+
+    <p>Some actions, such as "copy" and "paste" deal with the window, not the application. Window actions should be created as part of the window class.</p>
+
+    <p>The complete example files contain both application actions and window applications.  The window actions are the ones usually included in the <link xref="gmenu.py">application menu</link> also.  It is not good practice to include window actions in the applcation menu. For demonstration purposes, the complete example files which follow include XML in the UI file which creates the application menu which includes a "New" and "Open" item, and these are hooked up to the same actions as the menubar items of the same name.</p>
+  </section>
+
+  <section id="choices">
+    <title>Choices submenu and items with state</title>
+    <media type="image" mime="image/png" src="media/menubar_choices.png"/>
+    <p>Lines 30 to 80 inclusive of the <link xref="menubar.py#xml-code" /> demonstrate the XML code used to create the UI for <gui>Choices</gui> menu.</p>
+
+    <p>The actions created so far are stateless, that is they do not retain or depend on a state given by the action itself. The actions we need to create for the Choices submenu, on the other hand, are stateful. An example of creation of a stateful action is:</p>
+    <code>
+shape_action = Gio.SimpleAction.new_stateful("shape", GLib.VariantType.new('s'), GLib.Variant.new_string('line'))</code>
+
+    <p>where the variables of the method are: name, parameter type (in this case, a string), initial state (in this case, 'line')</p>
+
+    <p>After creating the stateful SimpleAction we connect it to the callback function and we add it to the window (or the application, if it is the case), as before:</p>
+
+    <code>
+shape_action.connect("activate", self.shape_callback)
+self.add_action(shape_action)</code>
+
+  </section>
+
+  <section id="xml-code">
+    <title>Complete XML UI file for this example</title>
+    <code mime="text" style="numbered"><xi:include href="samples/menubar.ui" parse="text"><xi:fallback/></xi:include></code>
+  </section>
+
+  <section id="python-code">
+    <title>Complete Python file for this example</title>
+    <code mime="text/x-python" style="numbered"><xi:include href="samples/menubar.py" parse="text"><xi:fallback/></xi:include></code>
+  </section>
+
+  <section id="mnemonics-and-accelerators"><title>Mnemonics and Accelerators</title>
+    <p>Labels may contain mnemonics. Mnemonics are underlined characters in the label, used for keyboard navigation. Mnemonics are created by placing an underscore before the mnemonic character.  For example "_File" instead of just "File" in the menubar.ui label attribute.</p>
+   <p>The mnemonics are visible when you press the <key>Alt</key> key.  Pressing <keyseq><key>Alt</key><key>F</key></keyseq> will open the <gui>File</gui> menu.</p>
+
+    <p>Accelerators  can be explicitly added in the UI definitions.  For example, it is common to be able to quit an application by pressing <keyseq><key>Ctrl</key><key>Q</key></keyseq> or to save a file by pressing <keyseq><key>Ctrl</key><key>S</key></keyseq>.  To add an accelerator to the UI definition, you simply need add an "accel" attribute to the item.</p>
+<p><code mime="text"><![CDATA[<attribute name="accel">&lt;Primary&gt;q</attribute>]]></code> will create the <keyseq><key>Ctrl</key><key>Q</key></keyseq> sequence when added to the <code>Quit</code> label item.  Here, "Primary" refers to the <key>Ctrl</key> key on a PC or the <key>â</key> key on a Mac.</p>
+
+  <code mime="text"><![CDATA[
+<item>
+  <attribute name="label">_Quit</attribute>
+  <attribute name="action">app.quit</attribute>
+  <attribute name="accel">&lt;Primary&gt;q</attribute>
+</item>]]></code>
+  </section>
+
+  <section id="translatable"><title>Translatable strings</title>
+   <p>
+   Since GNOME applications are being translated into <link href="http://l10n.gnome.org/languages/";>many languages</link>, it is important that the strings in your application are translable.  To make a label translatable, simple set <code>translatable="yes"</code>:
+   </p>
+   <p>
+     <code mime="text"><![CDATA[<attribute name="label" translatable="yes">Quit</attribute>]]></code>
+  </p>
+  </section>
+  <section id="references">
+    <title>API References</title>
+    <p>In this sample we used the following:</p>
+    <list>
+      <item><p><link href="http://developer.gnome.org/gio/unstable/GSimpleAction.html";>GSimpleAction</link></p></item>
+      <item><p><link href="http://developer.gnome.org/gtk3/unstable/GtkBuilder.html";>GtkBuilder</link></p></item>
+    </list>
+  </section>
+</page>
diff --git a/platform-demos/C/samples/menubar.py b/platform-demos/C/samples/menubar.py
new file mode 100644
index 0000000..ae63cc4
--- /dev/null
+++ b/platform-demos/C/samples/menubar.py
@@ -0,0 +1,159 @@
+from gi.repository import Gtk
+from gi.repository import GLib
+from gi.repository import Gio
+import sys
+
+class MyWindow(Gtk.ApplicationWindow):
+    def __init__(self, app):
+        Gtk.Window.__init__(self, title="MenuBar Example", application=app)
+        self.set_default_size(200, 200)
+
+        # action without a state created (name, parameter type)
+        copy_action = Gio.SimpleAction.new("copy", None)
+        # connected with the callback function
+        copy_action.connect("activate", self.copy_callback)
+        # added to the window
+        self.add_action(copy_action)
+
+        # action without a state created (name, parameter type)
+        paste_action = Gio.SimpleAction.new("paste", None)
+        # connected with the callback function
+        paste_action.connect("activate", self.paste_callback)
+        # added to the window
+        self.add_action(paste_action)
+
+        # action with a state created (name, parameter type, initial state)
+        shape_action = Gio.SimpleAction.new_stateful("shape", GLib.VariantType.new('s'), GLib.Variant.new_string('line'))
+        # connected to the callback function
+        shape_action.connect("activate", self.shape_callback)
+        # added to the window
+        self.add_action(shape_action)
+
+        # action with a state created
+        about_action = Gio.SimpleAction.new("about", None)
+        # action connected to the callback function
+        about_action.connect("activate", self.about_callback)
+        # action added to the application
+        self.add_action(about_action)
+
+    # callback function for copy_action
+    def copy_callback(self, action, parameter):
+        print "\"Copy\" activated"
+
+    # callback function for paste_action
+    def paste_callback(self, action, parameter):
+        print "\"Paste\" activated"
+
+    # callback function for shape_action
+    def shape_callback(self, action, parameter):
+		print "Shape is set to", parameter.get_string()
+		# Note that we set the state of the action!
+		action.set_state(parameter)
+
+    # callback function for about (see the AboutDialog example)
+    def about_callback(self, action, parameter):
+        # a  Gtk.AboutDialog
+        aboutdialog = Gtk.AboutDialog()
+
+        # lists of authors and documenters (will be used later)
+        authors = ["GNOME Documentation Team"]
+        documenters = ["GNOME Documentation Team"]
+
+        # we fill in the aboutdialog
+        aboutdialog.set_program_name("MenuBar Example")
+        aboutdialog.set_copyright("Copyright \xc2\xa9 2012 GNOME Documentation Team")
+        aboutdialog.set_authors(authors)
+        aboutdialog.set_documenters(documenters)
+        aboutdialog.set_website("http://developer.gnome.org";)
+        aboutdialog.set_website_label("GNOME Developer Website")
+
+        # to close the aboutdialog when "close" is clicked we connect the
+        # "response" signal to on_close
+        aboutdialog.connect("response", self.on_close)
+        # show the aboutdialog
+        aboutdialog.show()
+
+    # a callback function to destroy the aboutdialog
+    def on_close(self, action, parameter):
+        action.destroy()
+
+class MyApplication(Gtk.Application):
+    def __init__(self):
+        Gtk.Application.__init__(self)
+
+    def do_activate(self):
+        win = MyWindow(self)
+        win.show_all()
+
+    def do_startup(self):
+        # FIRST THING TO DO: do_startup()
+        Gtk.Application.do_startup(self)
+
+        # action without a state created
+        new_action = Gio.SimpleAction.new("new", None)
+        # action connected to the callback function
+        new_action.connect("activate", self.new_callback)
+        # action added to the application
+        self.add_action(new_action)
+
+        # action without a state created
+        quit_action = Gio.SimpleAction.new("quit", None)
+        # action connected to the callback function
+        quit_action.connect("activate", self.quit_callback)
+        # action added to the application
+        self.add_action(quit_action)
+
+        # action with a state created
+        state_action = Gio.SimpleAction.new_stateful("state",  GLib.VariantType.new('s'), GLib.Variant.new_string('off'))
+        # action connected to the callback function
+        state_action.connect("activate", self.state_callback)
+        # action added to the application
+        self.add_action(state_action)
+
+        # action with a state created
+        awesome_action = Gio.SimpleAction.new_stateful("awesome", None, GLib.Variant.new_boolean(False))
+        # action connected to the callback function
+        awesome_action.connect("activate", self.awesome_callback)
+        # action added to the application
+        self.add_action(awesome_action)
+
+        # a builder to add the UI designed with Glade to the grid:
+        builder = Gtk.Builder()
+        # get the file (if it is there)
+        try:
+            builder.add_from_file("menubar.ui")
+        except:
+            print "file not found"
+            sys.exit()
+
+        # we use the method Gtk.Application.set_menubar(menubar) to add the menubar
+        # and the menu to the application (Note: NOT the window!)
+        self.set_menubar(builder.get_object("menubar"))
+        self.set_app_menu(builder.get_object("appmenu"))
+
+    # callback function for new
+    def new_callback(self, action, parameter):
+        print "You clicked \"New\""
+
+    # callback function for quit
+    def quit_callback(self, action, parameter):
+        print "You clicked \"Quit\""
+        sys.exit()
+
+    # callback function for state
+    def state_callback(self, action, parameter):
+        print "State is set to", parameter.get_string()
+        action.set_state(parameter)
+
+    # callback function for awesome
+    def awesome_callback(self, action, parameter):
+        action.set_state(GLib.Variant.new_boolean(not action.get_state()))
+        if action.get_state().get_boolean() is True:
+            print "You checked \"Awesome\""
+        else:
+            print "You unchecked \"Awesome\""
+
+
+app = MyApplication()
+exit_status = app.run(sys.argv)
+sys.exit(exit_status)
diff --git a/platform-demos/Makefile.am b/platform-demos/Makefile.am
index 6c4e720..00e8d7b 100644
--- a/platform-demos/Makefile.am
+++ b/platform-demos/Makefile.am
@@ -78,8 +78,9 @@ demo_sources = \
 	samples/linkbutton.vala			\
 	samples/menubutton.js			\
 	samples/menubutton.vala			\
-	samples/menubar.vala			\
+	samples/menubar.py			\
 	samples/menubar.ui			\
+	samples/menubar.vala			\
 	samples/menubar_basis.vala		\
 	samples/menubar_basis.ui		\
 	samples/messagedialog.js		\
@@ -297,6 +298,7 @@ DOC_PAGES =				\
 	linkbutton.py.page		\
 	linkbutton.vala.page		\
 	magic-mirror.vala.page		\
+	menubar.py.page		\
 	menubar.vala.page		\
 	menubutton.js.page		\
 	menubutton.vala.page		\
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]