xmlns:its="http://www.w3.org/2005/11/its"

      xmlns:xi="http://www.w3.org/2001/XInclude"

      type="guide" style="task"

      id="menubar.py">

  <info>

  <title type="text">MenuBar (Python)</title>

  <link type="guide" xref="beginner.py#menu-combo-toolbar"/>

  <link type="seealso" xref="gmenu.py"/>

    <link type="next" xref="colorbutton.py"/>

    <revision version="0.1" date="2012-08-01" status="stub"/>

    <credit type="author copyright">

      <name>Tiffany Antopolski</name>

      <email its:translate="no">tiffany.antopolski@gmail.com</email>

      <years>2012</years>

    </credit>

    <credit type="author copyright">

      <name>Marta Maria Casetti</name>

      <email its:translate="no">mmcasetti@gmail.com</email>

      <years>2012</years>

    </credit>

    <desc>A widget which holds GtkMenuItem widgets</desc>

  </info>

  <title>MenuBar created using XML and GtkBuilder</title>

  <media type="image" mime="image/png" src="media/menubar.png"/>

  
A MenuBar created using XML and GtkBuilder.

  <links type="section"/>

  <section id="xml"> <title>Create a MenuBar using XML</title>

   
To create the menubar using XML:

   <steps>

     <item>
Create <file>menubar.ui</file> using your favorite text editor.
</item>

     <item>
Enter the following line at the top of the file:

]]>

     </item>

    <item>
We want to create the interface which will contain our menubar and its 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:

    <xi:include href="samples/menubar_basis.ui" parse="text"><xi:fallback/></xi:include>

     </item>

     <item>
Now we will create the .py file and use GtkBuilder to import the <file>menubar.ui</file> we just created.
</item>

   </steps>

   </section>

   <section id="basis"> <title>Add the MenuBar to the window using GtkBuilder</title>

<xi:include href="samples/menubar_basis.py" parse="text"><xi:fallback/></xi:include>

Now run the python application. It should look like the picture at the top of this page.

</section>

<section id="xml2"> <title>Add items to the menus</title>

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 section to the the File submenu with these items. The <file>menubar.ui</file> should look like this  (lines 6 to 13 inclusive comprise the newly added section):

   <listing>

      <title>menubar.ui</title>

<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>]]>

</listing>

  
Following this pattern, you can now add a Copy and a Paste item to the Edit submenu, and an About item to the Help submenu.

  </section>

  <section id="actions">

    <title>Setup actions</title>

    
We now create the actions for "New" and "Quit" connected to a callback function in the Python file; for instance we create "new" as:

new_action = Gio.SimpleAction.new("new", None)

new_action.connect("activate", self.new_callback)

    
And we create the callback function of "new" as

def new_callback(self, action, parameter):

    print "You clicked \"New\""

    
Now, in the XML file, we connect the menu items to the actions in the XML file by adding the "action" attribute:

<item>

  <attribute name="label">New</attribute>

  <attribute name="action">app.new</attribute>

</item>]]>

    
Note that for an action that is relative to the application, we use the prefix app.; for actions that are relative to the window we use the prefix win..

    
Finally, in the Python file, we add the action to the application or to the window - so for instance app.new will be added to the application in the method do_startup(self) as

self.add_action(new_action)

    
See <link xref="signals-callbacks.py"/> for a more detailed explanation of signals and callbacks.
 

  </section>

  <section id="win-app"><title>Actions: Application or Window?</title>

    
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.

    
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.

    
The complete example files contain both application actions and window actions.  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 application 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.

  </section>

  <section id="choices">

    <title>Choices submenu and items with state</title>

    <media type="image" mime="image/png" src="media/menubar_choices.png"/>

    
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.

    
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:

shape_action = Gio.SimpleAction.new_stateful("shape", GLib.VariantType.new('s'), GLib.Variant.new_string('line'))

    
where the variables of the method are: name, parameter type (in this case, a string - see <link href="http://developer.gnome.org/glib/unstable/glib-GVariantType.html">here</link> for a complete list of character meanings), initial state (in this case, 'line' - in case of a True boolean value it should be Glib.Variant.new_boolean(True), and so on, see <link href="http://developer.gnome.org/glib/unstable/glib-GVariant.html">here</link> for a complete list)

    
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:

shape_action.connect("activate", self.shape_callback)

self.add_action(shape_action)

  </section>

  <section id="xml-code">

    <title>Complete XML UI file for this example</title>

    <xi:include href="samples/menubar.ui" parse="text"><xi:fallback/></xi:include>

  </section>

  <section id="python-code">

    <title>Complete Python file for this example</title>

    <xi:include href="samples/menubar.py" parse="text"><xi:fallback/></xi:include>

  </section>

  <section id="mnemonics-and-accelerators"><title>Mnemonics and Accelerators</title>

    
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.

   
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.

    
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.

<Primary>q</attribute>]]> will create the <keyseq><key>Ctrl</key><key>Q</key></keyseq> sequence when added to the Quit label item.  Here, "Primary" refers to the <key>Ctrl</key> key on a PC or the <key>⌘</key> key on a Mac.

<item>

  <attribute name="label">_Quit</attribute>

  <attribute name="action">app.quit</attribute>

  <attribute name="accel"><Primary>q</attribute>

</item>]]>

  </section>

  <section id="translatable"><title>Translatable strings</title>

   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 translatable.  To make a label translatable, simple set translatable="yes":

     Quit</attribute>]]>

  </section>

  <section id="references">

    <title>API References</title>

    
In this sample we used the following:

    <list>

      <item>
<link href="http://developer.gnome.org/gio/unstable/GSimpleAction.html">GSimpleAction</link>
</item>

      <item>
<link href="http://developer.gnome.org/gtk3/unstable/GtkBuilder.html">GtkBuilder</link>
</item>

    </list>

  </section>

</page>