Documentation/Maemo 5 Developer Guide/Porting Software/Migration - Revision history

amigadave: reformat images, add FORCETOC

amigadave — Wed, 18 Aug 2010 09:31:48 GMT

reformat images, add __FORCETOC__

← Older revision		Revision as of 09:31, 18 August 2010
Line 1:		Line 1:
	Because Hildon 2.2 is a big step up from previous versions, many approaches in the development of your program's graphical user interface may need to be migrated to this new interface type.		Because Hildon 2.2 is a big step up from previous versions, many approaches in the development of your program's graphical user interface may need to be migrated to this new interface type.
		+
		+	__FORCETOC__

	== Menus ==		== Menus ==
Line 17:		Line 19:
	'''Example 10.1. Menu example'''		'''Example 10.1. Menu example'''

-	<~~div class="graybox"~~>	+	<pre>
-		+	File
-	File	+	\ New
-	\ New	+	\ Open
-	\ Open	+	\ Save
-	\ Save	+	\ Save As
-	\ Save As	+	\ Quit
-	\ Quit	+	Edit
-	Edit	+	\ Copy
-	\ Copy	+	\ Paste
-	\ Paste	+	\ Cut
-	\ Cut	+	\ Indent Type
-	\ Indent Type	+	\ Tabs
-	\ Tabs	+	\ Spaces
-	\ Spaces	+	\ Preferences
-	\ Preferences	+	View
-	View	+	\ Zoom In
-	\ Zoom In	+	\ Zoom Out
-	\ Zoom Out	+	\ Normal Size
-	\ Normal Size	+	\ Highlight
-	\ Highlight	+	\ C
-	\ C	+	\ Python
-	\ Python	+	\ JAVA
-	\ JAVA	+	Help
-	Help	+	\ Contents
-	\ Contents	+	\ About
-	\ About	+	</pre>
-		+
-	</~~div~~>	+

	Guidelines:		Guidelines:
Line 63:		Line 63:
	The following example shows the implementation of the menu following the above decisions. The first figure below shows the final result of the app menu. The other showd the dialog activated by the menu command "Settings".		The following example shows the implementation of the menu following the above decisions. The first figure below shows the final result of the app menu. The other showd the dialog activated by the menu command "Settings".

-	[[Image:example-migrating-menu1.png\|~~400px~~]]	+	[[Image:example-migrating-menu1.png\|frame\|center\|alt=Screenshot of a HildonAppMenu\|HildonAppMenu example]]


-	[[Image:example-migrating-menu-view.png\|~~400px~~]]	+	[[Image:example-migrating-menu-view.png\|frame\|center\|alt=Screenshot of the settings dialog\|Settings dialog example]]


Line 204:		Line 204:
	Consider a dialog that includes, among other widgets, a frame labeled "Proxy Preferences" and three radio buttons: "None", "Auto" and "Manual", displayed vertically like Figure 10.1 "Three radio buttons" shows. The following example shows how such task could be accomplished using a picker button. The frame label becomes the picker button's title and the three radio buttons' labels become the choices in the picker's touch selector. The screenshot below shows the resulting graphical user interface.		Consider a dialog that includes, among other widgets, a frame labeled "Proxy Preferences" and three radio buttons: "None", "Auto" and "Manual", displayed vertically like Figure 10.1 "Three radio buttons" shows. The following example shows how such task could be accomplished using a picker button. The frame label becomes the picker button's title and the three radio buttons' labels become the choices in the picker's touch selector. The screenshot below shows the resulting graphical user interface.

-	[[Image:choices.png\|~~Image choices~~\|~~400px~~]]	+	[[Image:choices.png\|frame\|center\|alt=Screenshot of a picker button dialog\|Example of choices in a picker button]]

	'''Example 10.3. Migrating choice widgets'''		'''Example 10.3. Migrating choice widgets'''
Line 241:		Line 241:
	==Notebooks ==		==Notebooks ==

-	Because the use of notebooks is not advised in Hildon, the way to migrate a Maemo 4 dialog with notebook to Maemo 5, is to simply put all the items inside a single pannable dialog.	+	Because the use of notebooks is not advised in Hildon, the way to migrate a Maemo 4 dialog with a notebook to Maemo 5, is to simply put all the items inside a single pannable dialog.

	[[Category:Development]]		[[Category:Development]]
	[[Category:Documentation]]		[[Category:Documentation]]
	[[Category:Fremantle]]		[[Category:Fremantle]]

amigadave: use and


amigadave — Wed, 11 Aug 2010 15:40:51 GMT
use <source> and <code>
Show changes



amigadave: categorise
amigadave — Fri, 12 Feb 2010 12:47:28 GMT
categorise

		
		
		
		
		
		
		← Older revision
		Revision as of 12:47, 12 February 2010
		
		Line 241:
Line 241:
 ==Notebooks ==  ==Notebooks ==
 Because the use of notebooks is not advised in Hildon, the way to migrate a Maemo 4 dialog with notebook to Maemo 5, is to simply put all the items inside a single pannable dialog.  Because the use of notebooks is not advised in Hildon, the way to migrate a Maemo 4 dialog with notebook to Maemo 5, is to simply put all the items inside a single pannable dialog.
  + 
  + [[Category:Development]]
  + [[Category:Documentation]]
  + [[Category:Fremantle]]




tatiana: /* Migration */
tatiana — Fri, 04 Sep 2009 13:49:07 GMT
Migration

		
		
		
		
		
		
		← Older revision
		Revision as of 13:49, 4 September 2009
		
		Line 1:
Line 1:
- =Migration = + =Migration to Hildon 2.2=
 Because Hildon 2.2 is a big step up from previous versions, many approaches in the development of your program's graphical user interface may need to be migrated to this new interface type.  Because Hildon 2.2 is a big step up from previous versions, many approaches in the development of your program's graphical user interface may need to be migrated to this new interface type.
  




tatiana: Migrating a menu example: deprecated `hildon_stackable_window_set_main_menu' replaced to `hildon_window_set_app_menu'
tatiana — Tue, 01 Sep 2009 12:32:56 GMT
Migrating a menu example: deprecated `hildon_stackable_window_set_main_menu' replaced to `hildon_window_set_app_menu'

		
		
		
		
		
		
		← Older revision
		Revision as of 12:32, 1 September 2009
		
		Line 181:
Line 181:
         
      HildonAppMenu *menu = build_menu (window);       HildonAppMenu *menu = build_menu (window);
-      hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window),     menu); +      hildon_window_set_app_menu (HILDON_WINDOW (window),     menu);
         
      GtkWidget *contents = gtk_label_new ("This example shows how an app menu could be "\       GtkWidget *contents = gtk_label_new ("This example shows how an app menu could be "\




tatiana: Migrating a menu: minor syntax fixes, example is compilable now
tatiana — Tue, 01 Sep 2009 12:28:56 GMT
Migrating a menu: minor syntax fixes, example is compilable now

		
		
		
		
		
		
		← Older revision
		Revision as of 12:28, 1 September 2009
		
		Line 183:
Line 183:
      hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window),     menu);       hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window),     menu);
         
-      GtkWidget *contents = gtk_label_new ("This example shows how an app menu could be " +      GtkWidget *contents = gtk_label_new ("This example shows how an app menu could be "\
-                                           "migrated.\nMenu item callbacks " +                                           "migrated.\nMenu item callbacks "\
                                           "are not fully implemented.");                                            "are not fully implemented.");
      gtk_container_add (GTK_CONTAINER (window), contents);       gtk_container_add (GTK_CONTAINER (window), contents);




bijjal: Documentation/Maemo 5 Developer Guide/Application Development/Migration moved to Documentation/Maemo 5 Developer Guide/Porting Software/Migration
bijjal — Wed, 26 Aug 2009 07:47:08 GMT
Documentation/Maemo 5 Developer Guide/Application Development/Migration moved to Documentation/Maemo 5 Developer Guide/Porting Software/Migration

		
		
		
		
		
		
		← Older revision
		Revision as of 07:47, 26 August 2009
		
		



msoini: /* Menus */
msoini — Fri, 07 Aug 2009 12:35:57 GMT
Menus

		
		
		
		
		
		
		← Older revision
		Revision as of 12:35, 7 August 2009
		
		Line 59:
Line 59:
 ** NOTE: the document should be automatically saved (and re-opened) whenever the application is closed (or re-opened). There is no need to show any confirmation notes for this process.  ** NOTE: the document should be automatically saved (and re-opened) whenever the application is closed (or re-opened). There is no need to show any confirmation notes for this process.
 * Edit menu commands: remove "Cut/Copy/Paste", those should be used with keyboard shortcuts. Put all the rest inside "Preferences" dialog and rename it to "Settings"  * Edit menu commands: remove "Cut/Copy/Paste", those should be used with keyboard shortcuts. Put all the rest inside "Preferences" dialog and rename it to "Settings"
- * View menu commands: "Zoom" in a text editor is not very useful so remove it. Put "Highlight mode" in to "Settings". + * View menu commands: "Zoom" in a text editor is not very useful so remove it (for changing the font size, simply HW +/- keys would be enough). Put "Highlight mode" in to "Settings".
 * Help menu commands: Remove help. It's not part of the Hildon 2.2 UI Style.  * Help menu commands: Remove help. It's not part of the Hildon 2.2 UI Style.
  




msoini: /* Notebooks */
msoini — Fri, 07 Aug 2009 12:32:23 GMT
Notebooks
Show changes


msoini: /* Menus */
msoini — Fri, 07 Aug 2009 12:28:13 GMT
Menus

		
		
		
		
		
		
		← Older revision
		Revision as of 12:28, 7 August 2009
		
		Line 79:
Line 79:
   {    {
      /* Code to set show settings dialog... */       /* Code to set show settings dialog... */
-   +     g_assert(data);
-      GtkWidget *window = widget ? gtk_widget_get_ancestor (GTK_WIDGET(widget), GTK_TYPE_WINDOW) : NULL; +     GtkDialog *dialog = GTK_DIALOG(
-      GtkDialog *dialog = GTK_DIALOG( + 
         gtk_dialog_new_with_buttons("Settings",          gtk_dialog_new_with_buttons("Settings",
-                                     GTK_WINDOW(window), +                                     GTK_WINDOW(data),
                                     GTK_DIALOG_MODAL | GTK_DIALOG_DESTROY_WITH_PARENT,                                      GTK_DIALOG_MODAL | GTK_DIALOG_DESTROY_WITH_PARENT,
                                     dgettext("hildon-libs", "wdgt_bd_save"),                                      dgettext("hildon-libs", "wdgt_bd_save"),
Line 139:
Line 138:
         
   static HildonAppMenu *    static HildonAppMenu *
-   build_menu (void) +   build_menu (GtkWidget *window)
   {    {
      HildonSizeType button_size = HILDON_SIZE_FINGER_HEIGHT | HILDON_SIZE_AUTO_WIDTH;       HildonSizeType button_size = HILDON_SIZE_FINGER_HEIGHT | HILDON_SIZE_AUTO_WIDTH;
Line 164:
Line 163:
      gtk_button_set_label (button, "Settings");       gtk_button_set_label (button, "Settings");
      g_signal_connect (G_OBJECT (button), "clicked",       g_signal_connect (G_OBJECT (button), "clicked",
-                        G_CALLBACK (menu_settings_cb), NULL); +                        G_CALLBACK (menu_settings_cb), window);
      hildon_app_menu_append (menu, GTK_BUTTON (button));       hildon_app_menu_append (menu, GTK_BUTTON (button));
         
Line 181:
Line 180:
      gtk_window_set_title (GTK_WINDOW (window), "Editor");       gtk_window_set_title (GTK_WINDOW (window), "Editor");
         
-      HildonAppMenu *menu = build_menu (); +      HildonAppMenu *menu = build_menu (window);
      hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window),     menu);       hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window),     menu);

← Older revision		Revision as of 12:47, 12 February 2010
Line 241:		Line 241:
	==Notebooks ==		==Notebooks ==
	Because the use of notebooks is not advised in Hildon, the way to migrate a Maemo 4 dialog with notebook to Maemo 5, is to simply put all the items inside a single pannable dialog.		Because the use of notebooks is not advised in Hildon, the way to migrate a Maemo 4 dialog with notebook to Maemo 5, is to simply put all the items inside a single pannable dialog.
		+
		+	[[Category:Development]]
		+	[[Category:Documentation]]
		+	[[Category:Fremantle]]

← Older revision		Revision as of 13:49, 4 September 2009
Line 1:		Line 1:
-	=Migration =	+	=Migration to Hildon 2.2=
	Because Hildon 2.2 is a big step up from previous versions, many approaches in the development of your program's graphical user interface may need to be migrated to this new interface type.		Because Hildon 2.2 is a big step up from previous versions, many approaches in the development of your program's graphical user interface may need to be migrated to this new interface type.

← Older revision		Revision as of 12:32, 1 September 2009
Line 181:		Line 181:

	HildonAppMenu *menu = build_menu (window);		HildonAppMenu *menu = build_menu (window);
-	~~hildon_stackable_window_set_main_menu~~ (~~HILDON_STACKABLE_WINDOW~~ (window), menu);	+	hildon_window_set_app_menu (HILDON_WINDOW (window), menu);

	GtkWidget *contents = gtk_label_new ("This example shows how an app menu could be "\		GtkWidget *contents = gtk_label_new ("This example shows how an app menu could be "\

← Older revision		Revision as of 12:28, 1 September 2009
Line 183:		Line 183:
	hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window), menu);		hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window), menu);

-	GtkWidget *contents = gtk_label_new ("This example shows how an app menu could be "	+	GtkWidget *contents = gtk_label_new ("This example shows how an app menu could be "\
-	"migrated.\nMenu item callbacks "	+	"migrated.\nMenu item callbacks "\
	"are not fully implemented.");		"are not fully implemented.");
	gtk_container_add (GTK_CONTAINER (window), contents);		gtk_container_add (GTK_CONTAINER (window), contents);

← Older revision		Revision as of 12:35, 7 August 2009
Line 59:		Line 59:
	** NOTE: the document should be automatically saved (and re-opened) whenever the application is closed (or re-opened). There is no need to show any confirmation notes for this process.		** NOTE: the document should be automatically saved (and re-opened) whenever the application is closed (or re-opened). There is no need to show any confirmation notes for this process.
	* Edit menu commands: remove "Cut/Copy/Paste", those should be used with keyboard shortcuts. Put all the rest inside "Preferences" dialog and rename it to "Settings"		* Edit menu commands: remove "Cut/Copy/Paste", those should be used with keyboard shortcuts. Put all the rest inside "Preferences" dialog and rename it to "Settings"
-	* View menu commands: "Zoom" in a text editor is not very useful so remove it. Put "Highlight mode" in to "Settings".	+	* View menu commands: "Zoom" in a text editor is not very useful so remove it (for changing the font size, simply HW +/- keys would be enough). Put "Highlight mode" in to "Settings".
	* Help menu commands: Remove help. It's not part of the Hildon 2.2 UI Style.		* Help menu commands: Remove help. It's not part of the Hildon 2.2 UI Style.

← Older revision		Revision as of 12:28, 7 August 2009
Line 79:		Line 79:
	{		{
	/* Code to set show settings dialog... */		/* Code to set show settings dialog... */
-		+	g_assert(data);
-	~~GtkWidget *window = widget ? gtk_widget_get_ancestor~~ (~~GTK_WIDGET(widget), GTK_TYPE_WINDOW~~) ~~: NULL~~;	+	GtkDialog *dialog = GTK_DIALOG(
-	GtkDialog *dialog = GTK_DIALOG(	+
	gtk_dialog_new_with_buttons("Settings",		gtk_dialog_new_with_buttons("Settings",
-	GTK_WINDOW(~~window~~),	+	GTK_WINDOW(data),
	GTK_DIALOG_MODAL \| GTK_DIALOG_DESTROY_WITH_PARENT,		GTK_DIALOG_MODAL \| GTK_DIALOG_DESTROY_WITH_PARENT,
	dgettext("hildon-libs", "wdgt_bd_save"),		dgettext("hildon-libs", "wdgt_bd_save"),
Line 139:		Line 138:

	static HildonAppMenu *		static HildonAppMenu *
-	build_menu (~~void~~)	+	build_menu (GtkWidget *window)
	{		{
	HildonSizeType button_size = HILDON_SIZE_FINGER_HEIGHT \| HILDON_SIZE_AUTO_WIDTH;		HildonSizeType button_size = HILDON_SIZE_FINGER_HEIGHT \| HILDON_SIZE_AUTO_WIDTH;
Line 164:		Line 163:
	gtk_button_set_label (button, "Settings");		gtk_button_set_label (button, "Settings");
	g_signal_connect (G_OBJECT (button), "clicked",		g_signal_connect (G_OBJECT (button), "clicked",
-	G_CALLBACK (menu_settings_cb), ~~NULL~~);	+	G_CALLBACK (menu_settings_cb), window);
	hildon_app_menu_append (menu, GTK_BUTTON (button));		hildon_app_menu_append (menu, GTK_BUTTON (button));

Line 181:		Line 180:
	gtk_window_set_title (GTK_WINDOW (window), "Editor");		gtk_window_set_title (GTK_WINDOW (window), "Editor");

-	HildonAppMenu *menu = build_menu ();	+	HildonAppMenu *menu = build_menu (window);
	hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window), menu);		hildon_stackable_window_set_main_menu (HILDON_STACKABLE_WINDOW (window), menu);

Documentation/Maemo 5 Developer Guide/Porting Software/Migration - Revision history

amigadave: reformat images, add __FORCETOC__

amigadave: use and

amigadave: categorise

tatiana: /* Migration */

tatiana: Migrating a menu example: deprecated `hildon_stackable_window_set_main_menu' replaced to `hildon_window_set_app_menu'

tatiana: Migrating a menu: minor syntax fixes, example is compilable now

bijjal: Documentation/Maemo 5 Developer Guide/Application Development/Migration moved to Documentation/Maemo 5 Developer Guide/Porting Software/Migration

msoini: /* Menus */

msoini: /* Notebooks */

msoini: /* Menus */

amigadave: reformat images, add FORCETOC