Editing PyMaemo/UI tutorial/Windows and dialogs

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
{{main|Legacy Maemo 5 Documentation/Graphical UI Tutorial/Windows and dialogs}}
+
= Windows and dialogs =
-
 
+
When creating applications for hand-held devices, you should take into account several issues about usability and device limitations. Screen size is a particularly large restriction; a simple interface is essential.
When creating applications for hand-held devices, you should take into account several issues about usability and device limitations. Screen size is a particularly large restriction; a simple interface is essential.
In contrast with GTK+ applications, Hildon applications display only one window at a time. A typical Hildon application uses several windows representing different views in a tree-like hierarchy.
In contrast with GTK+ applications, Hildon applications display only one window at a time. A typical Hildon application uses several windows representing different views in a tree-like hierarchy.
-
[[PyMaemo/UITutorial/Getting started#Hello World in Hildon|Example 1.2]] has already shown how to use a simple <code>HildonWindow</code> can be used and how it resembles the use of a classical GTK+ window. The tree-like views represent a new concept introduced by Hildon.
+
[[PyMaemo/UITutorial/Getting started#Hello World in Hildon | Example 1.2]] has already shown how to use a simple HildonWindow can be used and how it resembles the use of a classical GTK+ window. The tree-like views represent a new concept introduced by Hildon.
To properly understand what views are, think of an application as a program that allows the user to perform one or more tasks. Each task can be broken down into several main activities.
To properly understand what views are, think of an application as a program that allows the user to perform one or more tasks. Each task can be broken down into several main activities.
Line 17: Line 16:
The view concept is implemented by the widget HildonStackableWindow. This widget allows building a navigable hierarchy of windows with less code.
The view concept is implemented by the widget HildonStackableWindow. This widget allows building a navigable hierarchy of windows with less code.
-
==Stackable windows ==
 
-
The <code>HildonStackableWindow</code> is a GTK+ widget which represents a top-level window in the Hildon framework. Stackable windows can be organized in a hierarchical way.
+
==Stackable windows ==
 +
The HildonStackableWindow is a GTK+ widget which represents a top-level window in the Hildon framework. Stackable windows can be organized in a hierarchical way.
A stack sets the hierarchical relationships between windows. A child window is on top of its parent window. That allows navigation to previous window by removing the topmost window.
A stack sets the hierarchical relationships between windows. A child window is on top of its parent window. That allows navigation to previous window by removing the topmost window.
Line 30: Line 29:
'''Example 2.1. Example of stackable windows'''
'''Example 2.1. Example of stackable windows'''
-
<source lang="python">
+
    # Based on C code from:
-
# Based on C code from:
+
    # "Hildon Tutorial" version 2009-04-28
-
# "Hildon Tutorial" version 2009-04-28
+
    # Example 2.1, "Example of stackable windows"
-
# Example 2.1, "Example of stackable windows"
+
-
 
+
-
import gtk
+
-
import hildon
+
-
 
+
-
def show_new_window(widget):
+
-
    # Create the main window
+
-
    win = hildon.StackableWindow()
+
-
    win.set_title("Subview")
+
-
 
+
-
    # Setting a label in the new window
+
-
    label = gtk.Label("This is a subview")
+
-
 
+
-
    vbox = gtk.VBox(False, 0)
+
-
    vbox.pack_start(label, True, True, 0)
+
-
 
+
-
    win.add(vbox)
+
-
 
+
-
    # This call show the window and also add the window to the stack
+
-
    win.show_all()
+
-
 
+
-
def main():
+
-
    program = hildon.Program.get_instance()
+
      
      
-
     # Create the main window
+
     import gtk
-
    win = hildon.StackableWindow()
+
    import hildon
-
     win.set_title("Main window")
+
   
 +
    def show_new_window(widget):
 +
        # Create the main window
 +
        win = hildon.StackableWindow()
 +
        win.set_title("Subview")
 +
      
 +
        # Setting a label in the new window
 +
        label = gtk.Label("This is a subview")
 +
   
 +
        vbox = gtk.VBox(False, 0)
 +
        vbox.pack_start(label, True, True, 0)
 +
   
 +
        win.add(vbox)
 +
   
 +
        # This call show the window and also add the window to the stack
 +
        win.show_all()
 +
   
 +
    def main():
 +
        program = hildon.Program.get_instance()
 +
       
 +
        # Create the main window
 +
        win = hildon.StackableWindow()
 +
        win.set_title("Main window")
 +
   
 +
        button = gtk.Button("Go to subview")
 +
        win.add(button)
 +
   
 +
        button.connect("clicked", show_new_window)
 +
   
 +
        win.connect("destroy", gtk.main_quit, None)
 +
   
 +
        # This call show the window and also add the window to the stack
 +
        win.show_all()
 +
        gtk.main()
 +
   
 +
    if __name__ == "__main__":
 +
        main()
-
    button = gtk.Button("Go to subview")
 
-
    win.add(button)
 
-
    button.connect("clicked", show_new_window)
 
-
    win.connect("destroy", gtk.main_quit, None)
 
-
 
-
    # This call show the window and also add the window to the stack
 
-
    win.show_all()
 
-
    gtk.main()
 
-
 
-
if __name__ == "__main__":
 
-
    main()
 
-
</source>
 
The function <code>show_new_window(widget)</code> is set up as a handler for when the signal "clicked" is emitted. This function creates a new stackable window which is added on top of the stack by calling <code>show()</code>.
The function <code>show_new_window(widget)</code> is set up as a handler for when the signal "clicked" is emitted. This function creates a new stackable window which is added on top of the stack by calling <code>show()</code>.
Line 83: Line 83:
In some applications it could be necessary to push and/or pop windows on the stack without destroying them, or even to build and handle extra windows' stacks. Next section explains how to do that.
In some applications it could be necessary to push and/or pop windows on the stack without destroying them, or even to build and handle extra windows' stacks. Next section explains how to do that.
-
===Advanced stack handling===
+
==Advanced stack handling ==
-
The object which represents a stack of windows in the Hildon framework is the <code>HildonWindowStack</code>. This object provides functions to push and/or pop windows on the stack, functions to access the topmost window or retrieve the current size of the stack are provided as well. Usual operations
+
The object which represents a stack of windows in the Hildon framework is the HildonWindowStack. This object provides functions to push and/or pop windows on the stack, functions to access the topmost window or retrieve the current size of the stack are provided as well. Usual operations
To access the default stack, use the function <code>hildon.WindowStack.get_default()</code>. To access the stack that contains a particular window, use <code>HildonStackableWindow.get_stack()</code>.
To access the default stack, use the function <code>hildon.WindowStack.get_default()</code>. To access the stack that contains a particular window, use <code>HildonStackableWindow.get_stack()</code>.
-
<source lang="python">
+
 
-
hildon.WindowStack.get_default()
+
    hildon.WindowStack.get_default()
-
</source>
+
 
The following functions are available to push and/or pop windows on a stack:
The following functions are available to push and/or pop windows on a stack:
-
<source lang="python">
+
 
-
class HildonWindowStack(...):
+
    class HildonWindowStack(...):
-
    def push(stackablewindow, ...)
+
        def push(stackablewindow, ...)
-
    def push_list(windows_list)
+
        def push_list(windows_list)
-
    def push_1(stackablewindow)
+
        def push_1(stackablewindow)
-
    def pop(number_of_windows):
+
        def pop(number_of_windows):
-
        return list_of_popped_windows
+
            return list_of_popped_windows
-
    def pop_1():
+
        def pop_1():
-
        return stackablewindow
+
            return stackablewindow
-
    def pop_and_push(nwindows, stackablewindow, ...):
+
        def pop_and_push(nwindows, stackablewindow, ...):
-
        return list_of_popped_windows
+
            return list_of_popped_windows
-
    def pop_and_push_list(nwindows, windows_list):
+
        def pop_and_push_list(nwindows, windows_list):
-
        return list_of_popped_windows
+
            return list_of_popped_windows
-
</source>
+
 
The example shows how to get the default stack and push a newly created window on the stack. (Note that you also can do the same in a single stack by calling <code>show()</code>).
The example shows how to get the default stack and push a newly created window on the stack. (Note that you also can do the same in a single stack by calling <code>show()</code>).
'''Example 2.2. Pushing a new window into a stack'''
'''Example 2.2. Pushing a new window into a stack'''
-
<source lang="python">
 
-
import hildon
 
-
win = hildon.StackableWindow()
+
    import hildon
-
stack = hildon.WindowStack.get_default()
+
   
-
stack.push_1(win)
+
    win = hildon.StackableWindow()
-
</source>
+
    stack = hildon.WindowStack.get_default()
 +
    stack.push_1(win)
 +
 
 +
 
The push functions also displays the window. <code>show()</code> is not needed after a push operation.
The push functions also displays the window. <code>show()</code> is not needed after a push operation.
Line 122: Line 123:
'''Example 2.3. Pushing a list of windows into a stack'''
'''Example 2.3. Pushing a list of windows into a stack'''
-
<source lang="python">
 
-
import hildon
 
-
window = hildon.StackableWindow()
+
    import hildon
-
window.show_all()
+
-
stack = window.get_stack()
+
      
      
-
win_list = []
+
    window = hildon.StackableWindow()
-
for i in range(10):
+
    window.show_all()
-
    parent = hildon.StackableWindow()
+
    stack = window.get_stack()
-
    parent.set_title('Window %d' % i)
+
       
-
    win_list.append(parent)
+
    win_list = []
 +
    for i in range(10):
 +
        parent = hildon.StackableWindow()
 +
        parent.set_title('Window %d' % i)
 +
        win_list.append(parent)
 +
   
 +
    stack.push_list(win_list)
-
stack.push_list(win_list)
 
-
</source>
 
Similar functions exist for the pop operation. The example uses <code>hildon.WindowStack.pop_list()</code> to pop N windows from the default stack and stores them in the list of arguments. Notice that <code>hildon.StackableWindow.size()</code> is used to check the size of the stack.
Similar functions exist for the pop operation. The example uses <code>hildon.WindowStack.pop_list()</code> to pop N windows from the default stack and stores them in the list of arguments. Notice that <code>hildon.StackableWindow.size()</code> is used to check the size of the stack.
'''Example 2.4. Popping a number of windows from a stack into a list'''
'''Example 2.4. Popping a number of windows from a stack into a list'''
-
<source lang="python">
 
-
import hildon
 
-
stack = hildon.StackableWindow.get_default()
+
    import hildon
-
nwindows = 10
+
   
-
win_list = None
+
    stack = hildon.StackableWindow.get_default()
 +
    nwindows = 10
 +
    win_list = None
 +
   
 +
    if stack.size() > nwindows:
 +
        win_list = stack.pop(nwindows)
 +
 
 +
-
if stack.size() > nwindows:
+
HildonWindowStack object also provides more advanced functions to perform both pop and push operations at once such as, for example, <code>hildon.WindowStack.pop_and_push()</code> or <code>hildon.WindowStack.pop_and_push_list()</code>. These functions do everything in a single transition, so the user only sees the last pushed window.
-
    win_list = stack.pop(nwindows)
+
-
</source>
+
-
<code>HildonWindowStack</code> object also provides more advanced functions to perform both pop and push operations at once such as, for example, <code>hildon.WindowStack.pop_and_push()</code> or <code>hildon.WindowStack.pop_and_push_list()</code>. These functions do everything in a single transition, so the user only sees the last pushed window.
+
When you perform push/pop operations, consider two things:
When you perform push/pop operations, consider two things:
Line 162: Line 165:
Regarding the second one, operation push has no effect on windows which are already on a stack.
Regarding the second one, operation push has no effect on windows which are already on a stack.
-
====Multiple Stacks====
+
'''Multiple Stacks'''
Most applications do not need more than the default stack. Although you can use multiple stacks in one application, note that this increases the complexity of the UI, which is not desirable.
Most applications do not need more than the default stack. Although you can use multiple stacks in one application, note that this increases the complexity of the UI, which is not desirable.
Line 170: Line 173:
Once a new stack is created, use the functions explained in the previous section to pop and/or push windows on the stack.
Once a new stack is created, use the functions explained in the previous section to pop and/or push windows on the stack.
-
==Dialogs==
+
==Dialogs ==
Dialog boxes are a convenient way to prompt the user for a small amount of input, for example to display a message, ask a question, or anything else that does not require extensive effort on the user's part.
Dialog boxes are a convenient way to prompt the user for a small amount of input, for example to display a message, ask a question, or anything else that does not require extensive effort on the user's part.
-
Hildon provides specialized widgets to cover the most common dialog's use cases: <code>HildonNote</code> and <code>HildonBanner</code>.
+
Hildon provides specialized widgets to cover the most common dialog's use cases: HildonNote and HildonBanner.
-
<code>HildonNote</code> is useful to ask users a question and <code>HildonBanner</code> is used to show textual information which automatically disappear after a certain period of time without user interaction. For more information on these widgets, see [[PyMaemo/UI tutorial/Controls#Notification widgets|Notification widgets]].
+
HildonNote is useful to ask users a question and HildonBanner is used to show textual information which automatically disappear after a certain period of time without user interaction. For more information on these widgets, see [[PyMaemo/UITutorial/Controls#Notification_widgets |Notification widgets]] .
-
Besides those widgets, Hildon provides also specialized <code>GtkDialog</code>s designed to cover different use cases: <code>HildonPickerDialog</code> and <code>HildonWizardDialog</code>.
+
Besides those widgets, Hildon provides also specialized GtkDialogs designed to cover different use cases: HildonPickerDialog and HildonWizardDialog.
-
The widget <code>HildonPickerDialog</code> is used along with <code>HildonPickerButton</code> and <code>HildonTouchSelector</code> to give a way to make data selections. [[PyMaemo/UITutorial/Data_selection|Data Selection]] explains the use of such widgets.
+
The widget HildonPickerDialog is used along with HildonPickerButton and HildonTouchSelector to give a way to make data selections. [[PyMaemo/UITutorial/Data_selection|Data Selection]] explains the use of such widgets.
-
To create a guided process which helps users accomplish complex tasks step by step, Hildon provides the <code>HildonWizardDialog</code> widget.
+
To create a guided process which helps users accomplish complex tasks step by step, Hildon provides the HildonWizardDialog widget.
===HildonWizardDialog===
===HildonWizardDialog===
-
<code>HildonWizardDialog</code> is a widget that allows one to create a guided process. The dialog has three standard buttons, previous, next and finish, and contains several pages. Users can close the dialog by tapping the dimmed area outside the dialog's window.
+
HildonWizardDialog is a widget that allows one to create a guided process. The dialog has three standard buttons, previous, next and finish, and contains several pages. Users can close the dialog by tapping the dimmed area outside the dialog's window.
A good example of a guided process which can be implemented with this widget is the setup of a new e-mail account in an e-mail client. Users have to fill several entries through several steps to accomplish the setup of the new account. The process of installing an application is another example of the uses of this widget.
A good example of a guided process which can be implemented with this widget is the setup of a new e-mail account in an e-mail client. Users have to fill several entries through several steps to accomplish the setup of the new account. The process of installing an application is another example of the uses of this widget.
-
This widget uses a <code>GtkNotebook</code> that contains the actual wizard pages. The notebook widget is pointed by the property "wizard-notebook" of the wizard. You need to create the notebook as well as the pages that are displayed. For more information on <code>GtkNotebook</code>, see the GTK+ Reference Manual.
+
This widget uses a GtkNotebook that contains the actual wizard pages. The notebook widget is pointed by the property "wizard-notebook" of the wizard. You need to create the notebook as well as the pages that are displayed. For more information on GtkNotebook, see the GTK+ Reference Manual.
To create a new wizard dialog, call:
To create a new wizard dialog, call:
-
<source lang="python">
+
 
     hildon.WizardDialog(parent_window, wizard_name, gtk.Notebook)
     hildon.WizardDialog(parent_window, wizard_name, gtk.Notebook)
-
</source>
+
 
The parent window is usually the current visible view. The wizard name is displayed as title in the wizard dialog.
The parent window is usually the current visible view. The wizard name is displayed as title in the wizard dialog.
Usually, you want to validate user input to decide whether it should move to the next step or not. To do that, set a user function by using:
Usually, you want to validate user input to decide whether it should move to the next step or not. To do that, set a user function by using:
-
<source lang="python">
+
 
     hildon.WizardDialog.set_forward_page_func(page_func, data, destroy_notify)
     hildon.WizardDialog.set_forward_page_func(page_func, data, destroy_notify)
-
</source>
+
 
The function above sets the function "page_func" to be used to decide whether the user can go to the next page when pressing the forward button. The function must have the following signature:
The function above sets the function "page_func" to be used to decide whether the user can go to the next page when pressing the forward button. The function must have the following signature:
-
<source lang="python">
+
 
-
def some_page_func(notebook, current_page_number, user_data)
+
    def some_page_func(notebook, current_page_number, user_data)
-
</source>
+
 
Here, an example of using a HildonWizardDialog
Here, an example of using a HildonWizardDialog
Line 211: Line 214:
'''Example 2.5. Example of a Hildon wizard dialog'''
'''Example 2.5. Example of a Hildon wizard dialog'''
-
<source lang="python">
 
-
# Based on C code from:
 
-
# "Hildon Tutorial" version 2009-04-28
 
-
# Example 2.5, "Example of a Hildon wizard dialog"
 
-
import sys
+
    # Based on C code from:
-
 
+
    # "Hildon Tutorial" version 2009-04-28
-
import gtk
+
    # Example 2.5, "Example of a Hildon wizard dialog"
-
import hildon
+
   
-
 
+
    import sys
-
def on_page_switch(notebook, page, num, dialog):
+
   
-
    print >>sys.stderr, "Page %d" % num
+
    import gtk
-
    return True
+
    import hildon
-
 
+
   
-
def some_page_func(nb, current, userdata):
+
    def on_page_switch(notebook, page, num, dialog):
-
    # Validate data only for the third page.
+
        print >>sys.stderr, "Page %d" % num
-
    if current == 2:
+
-
        entry = nb.get_nth_page(current)
+
-
        return len(entry.get_text()) != 0
+
-
    else:
+
         return True
         return True
 +
   
 +
    def some_page_func(nb, current, userdata):
 +
        # Validate data only for the third page.
 +
        if current == 2:
 +
            entry = nb.get_nth_page(current)
 +
            return len(entry.get_text()) != 0
 +
        else:
 +
            return True
 +
   
 +
    def main():
 +
        # Create a notebook
 +
        notebook = gtk.Notebook()
 +
   
 +
        # Create widgets to palce into the notebook's pages
 +
        label_1 = gtk.Label("Page 1")
 +
        label_2 = gtk.Label("Page 2")
 +
   
 +
        entry_3 = hildon.Entry(gtk.HILDON_SIZE_AUTO)
 +
        entry_3.set_placeholder("Write something to continue")
 +
   
 +
        label_4 = gtk.Label("Page 4")
 +
   
 +
        # Append pages
 +
        notebook.append_page(label_1, None)
 +
        notebook.append_page(label_2, None)
 +
        notebook.append_page(entry_3, None)
 +
        notebook.append_page(label_4, None)
 +
   
 +
        # Create wizard dialog
 +
        dialog = hildon.WizardDialog(None, "Wizard", notebook)
 +
   
 +
        # Set a handler for "switch-page" signal
 +
        notebook.connect("switch-page", on_page_switch, dialog)
 +
   
 +
        # Set a function to decide if user can go to next page
 +
        dialog.set_forward_page_func(some_page_func)
 +
   
 +
        dialog.show_all()
 +
        dialog.run()
 +
   
 +
    if __name__ == "__main__":
 +
        main()
-
def main():
 
-
    # Create a notebook
 
-
    notebook = gtk.Notebook()
 
-
 
-
    # Create widgets to palce into the notebook's pages
 
-
    label_1 = gtk.Label("Page 1")
 
-
    label_2 = gtk.Label("Page 2")
 
-
 
-
    entry_3 = hildon.Entry(gtk.HILDON_SIZE_AUTO)
 
-
    entry_3.set_placeholder("Write something to continue")
 
-
 
-
    label_4 = gtk.Label("Page 4")
 
-
 
-
    # Append pages
 
-
    notebook.append_page(label_1, None)
 
-
    notebook.append_page(label_2, None)
 
-
    notebook.append_page(entry_3, None)
 
-
    notebook.append_page(label_4, None)
 
-
 
-
    # Create wizard dialog
 
-
    dialog = hildon.WizardDialog(None, "Wizard", notebook)
 
-
 
-
    # Set a handler for "switch-page" signal
 
-
    notebook.connect("switch-page", on_page_switch, dialog)
 
-
 
-
    # Set a function to decide if user can go to next page
 
-
    dialog.set_forward_page_func(some_page_func)
 
-
 
-
    dialog.show_all()
 
-
    dialog.run()
 
-
if __name__ == "__main__":
+
Apart from how to create and use a wizard dialog, this example also sets up a handler to catch the signal "switch-page" from the notepad. This signal is emitted by the widget GtkNotebook when the user or a function changes the current page.
-
    main()
+
-
</source>
+
-
Apart from how to create and use a wizard dialog, this example also sets up a handler to catch the signal "switch-page" from the notepad. This signal is emitted by the widget <code>GtkNotebook</code> when the user or a function changes the current page.
+
===Using GtkDialogs in Hildon applications===
===Using GtkDialogs in Hildon applications===
 +
In general, you can use GtkDialog much like you use it in a GTK+ application, but consider the following:
-
In general, you can use <code>GtkDialog</code> much like you use it in a GTK+ application, but consider the following:
+
* In Hildon applications, buttons "cancel", "reject" and "close" are allowed. However, buttons which emit the signal "response" with gtk.RESPONSE_CANCEL, gtk.RESPONSE_REJECT or gtk.RESPONSE_CLOSE as the response's identifier are not displayed. Therefore, if you need to deal with the action of closing a GtkDialog in a Hildon application, be aware of this detail and handle the gtk.RESPONSE_DELETE_EVENT response identifier properly.
-
 
+
* Another detail to take care of is that GtkDialogs can work in two modalities in a Hildon application: task-model or system-model. A dialog is task-modal if it is transient for the main window. That is the case when the function <code>gtk.Window.set_transient_for()</code> is used or the dialog was created by calling gtk.Dialog() specifying a parent window. Otherwise, the dialog is system-modal.
-
* In Hildon applications, buttons "cancel", "reject" and "close" are allowed. However, buttons which emit the signal "response" with <code>gtk.RESPONSE_CANCEL</code>, <code>gtk.RESPONSE_REJECT</code> or <code>gtk.RESPONSE_CLOSE</code> as the response's identifier are not displayed. Therefore, if you need to deal with the action of closing a <code>GtkDialog</code> in a Hildon application, be aware of this detail and handle the <code>gtk.RESPONSE_DELETE_EVENT</code> response identifier properly.
+
-
* Another detail to take care of is that <code>GtkDialog</code>s can work in two modalities in a Hildon application: task-model or system-model. A dialog is task-modal if it is transient for the main window. That is the case when the function <code>gtk.Window.set_transient_for()</code> is used or the dialog was created by calling <code>gtk.Dialog()</code> specifying a parent window. Otherwise, the dialog is system-modal.
+
If the dialog is task-modal, the Platform UI (Task button and Status area) are visible on top and can be used normally to switch between tasks.
If the dialog is task-modal, the Platform UI (Task button and Status area) are visible on top and can be used normally to switch between tasks.
Line 283: Line 286:
'''Example 2.6. Application modal dialog example'''
'''Example 2.6. Application modal dialog example'''
-
<source lang="python">
 
-
# Based on C code from:
 
-
# "Hildon Tutorial" version 2009-04-28
 
-
# Example 2.6, "Application modal dialog example"
 
-
import gtk
+
    # Based on C code from:
-
import hildon
+
     # "Hildon Tutorial" version 2009-04-28
-
 
+
    # Example 2.6, "Application modal dialog example"
-
def main():
+
   
-
     win = hildon.StackableWindow()
+
     import gtk
-
 
+
    import hildon
-
     win.show()
+
      
      
-
     dialog = gtk.Dialog()
+
     def main():
-
 
+
        win = hildon.StackableWindow()
-
     dialog.set_transient_for(win)
+
   
-
 
+
        win.show()
-
     dialog.set_title("Hello!")
+
       
-
 
+
        dialog = gtk.Dialog()
-
     dialog.show_all()
+
      
-
 
+
        dialog.set_transient_for(win)
-
     dialog.run()
+
      
-
 
+
        dialog.set_title("Hello!")
-
if __name__ == "__main__":
+
      
-
    main()
+
        dialog.show_all()
-
</source>
+
      
-
 
+
        dialog.run()
-
[[Category:Python]]
+
   
 +
    if __name__ == "__main__":
 +
        main()

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://wiki.maemo.org/PyMaemo/UI_tutorial/Windows_and_dialogs"