Documentation/Maemo 5 Developer Guide/Application Development/Writing Desktop Widgets - Revision history

amigadave: /* The .desktop File */ desktop file link

2010-09-02T15:07:21Z

The .desktop File: desktop file link

← Older revision		Revision as of 15:07, 2 September 2010
Line 133:		Line 133:
	===The .desktop File===		===The .desktop File===

-	Although other fields can be assigned in a .desktop file, the example bellow shows a simple .desktop file for the "TimeOut" widget. The "Name" field is the widget's name in the list when the user is choosing widgets to add to the desktop. The "X-Path" field should be set to the .so file that was previously generated.	+	Although other fields can be assigned in a [[Desktop file format\|.desktop file]], the example bellow shows a simple .desktop file for the "TimeOut" widget. The "Name" field is the widget's name in the list when the user is choosing widgets to add to the desktop. The "X-Path" field should be set to the .so file that was previously generated.

	Example 1.3. A .desktop file for the TimeOut widget: timeout-widget.desktop		Example 1.3. A .desktop file for the TimeOut widget: timeout-widget.desktop

amigadave: use and


2010-07-20T10:25:48Z
use <source> and <code>
Show changes



amigadave: make pkg-config invocation fit with manpage
2010-04-06T14:44:46Z
make pkg-config invocation fit with manpage

		
		
		
		
		
		
		← Older revision
		Revision as of 14:44, 6 April 2010
		
		Line 271:
Line 271:
 For Status Menu widget, .desktop files should be placed in the directory outputted by the following command:  For Status Menu widget, .desktop files should be placed in the directory outputted by the following command:
  
-   pkg-config libhildondesktop-1 --variable=hildonstatusmenudesktopentrydir +   pkg-config --variable=hildonstatusmenudesktopentrydir libhildondesktop-1
  
 ==Building Widgets==  ==Building Widgets==
 To use a widget, it needs to be built as a shared library. This is done by passing the -shared flag to gcc.  To use a widget, it needs to be built as a shared library. This is done by passing the -shared flag to gcc.
  
-   gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so +   gcc -shared `pkg-config --libs --cflags hildon-1 libhildondesktop-1` widget.c -o lib-widget.so
  
 Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/lib/hildon-desktop"):  Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/lib/hildon-desktop"):
  
-   pkg-config libhildondesktop-1 --variable=hildondesktoplibdir +   pkg-config --variable=hildondesktoplibdir libhildondesktop-1
  
 [[Category:Development]]  [[Category:Development]]
 [[Category:Documentation]]  [[Category:Documentation]]
 [[Category:Fremantle]]  [[Category:Fremantle]]




amigadave: categorise
2010-02-12T12:00:51Z
categorise

		
		
		
		
		
		
		← Older revision
		Revision as of 12:00, 12 February 2010
		
		Line 281:
Line 281:
  
   pkg-config libhildondesktop-1 --variable=hildondesktoplibdir    pkg-config libhildondesktop-1 --variable=hildondesktoplibdir
  + 
  + [[Category:Development]]
  + [[Category:Documentation]]
  + [[Category:Fremantle]]




tapio at 09:28, 12 February 2010
2010-02-12T09:28:23Z


		
		
		
		
		
		
		← Older revision
		Revision as of 09:28, 12 February 2010
		
		Line 1:
Line 1:
 =Writing Desktop Widgets=  =Writing Desktop Widgets=
 The following code examples are used in this chapter:  The following code examples are used in this chapter:
- * [https://garage.maemo.org/svn/maemoexamples/trunk/hildon-timeout-home-widget-example/ hildon-timeout-home-widget-example] + * [https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/hildon-timeout-home-widget-example/ hildon-timeout-home-widget-example]
- * [https://garage.maemo.org/svn/maemoexamples/trunk/hildon-status-menu-widget-example/ hildon-status-menu-widget-example] + * [https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/hildon-status-menu-widget-example/ hildon-status-menu-widget-example]
  
 Desktop widgets are programs designed to provide a certain functionality from the desktop area. These programs are usually limited, in the sense that they are not complex applications, normally representing "small" utilities or an extension of an existing application.  Desktop widgets are programs designed to provide a certain functionality from the desktop area. These programs are usually limited, in the sense that they are not complex applications, normally representing "small" utilities or an extension of an existing application.




208.54.83.28: /* Building Widgets */
2009-12-06T01:04:01Z
Building Widgets

		
		
		
		
		
		
		← Older revision
		Revision as of 01:04, 6 December 2009
		
		Line 278:
Line 278:
   gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so    gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so
  
- Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/share/applications/hildon-desktop"): + Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/lib/hildon-desktop"):
  
   pkg-config libhildondesktop-1 --variable=hildondesktoplibdir    pkg-config libhildondesktop-1 --variable=hildondesktoplibdir




liox_lang_valid: /* Writing Desktop Widgets */
2009-09-25T08:16:46Z
Writing Desktop Widgets

		
		
		
		
		
		
		← Older revision
		Revision as of 08:16, 25 September 2009
		
		Line 8:
Line 8:
 Desktop widgets are written as shared libraries and need also to provide a desktop file that describes them. Depending on their placement, they can be Status Menu widgets or Home Area widgets.  Desktop widgets are written as shared libraries and need also to provide a desktop file that describes them. Depending on their placement, they can be Status Menu widgets or Home Area widgets.
  
- They need to have a .desktop file describing them. The file contents are fields that describe certain properties of the widget. + They must have a .desktop file describing them. The file contents are fields that describe certain properties of the widget.
  
  
Line 16:
Line 16:
 To better show how to write a Home Area widget, consider a widget "TimeOut" that allows the user to choose an action to be performed at a given time.  To better show how to write a Home Area widget, consider a widget "TimeOut" that allows the user to choose an action to be performed at a given time.
  
- Home widgets should inherit from libhildondesktop's HDHomePluginItem. The following example presents a header file for the mentioned widget. + Home widgets must inherit from libhildondesktop's HDHomePluginItem. The following example presents a header file for the mentioned widget.
  
 '''Example 1.1. Header file for TimeOut widget: lib-timeout-home-widget.h'''  '''Example 1.1. Header file for TimeOut widget: lib-timeout-home-widget.h'''
Line 66:
Line 66:
  
  
- The first and more important function is HD_DEFINE_PLUGIN_MODULE. This function receives three parameters to register the object that is supplied by the plug-in. The first argument should be the object type name in Camel case, the second is the type name in lowercase with underscores separating the words. The third is the GType of the object's parent. Apart from this macro, three other functions should be used. The name of the functions should be the name given as second argument to HD_DEFINE_PLUGIN_MODULE with the suffixes _init, _class_init and _class_finalize. + The first and more important function is HD_DEFINE_PLUGIN_MODULE. This function receives three parameters to register the object that is supplied by the plug-in. The first argument is the object type name in Camel case, the second is the type name in lowercase with underscores separating the words. The third is the GType of the object's parent. Apart from this macro, use also three other functions. The name of the functions is the name given as second argument to HD_DEFINE_PLUGIN_MODULE with the suffixes _init, _class_init and _class_finalize.
  
 The following example shows the source code for "TimeOut" widget.  The following example shows the source code for "TimeOut" widget.
Line 128:
Line 128:
  
                               
- As you can see in the example above, the controls used in the widget (build_ui function) should be added to "TimeOutPlugin". In this case, the widget works as a standalone application, but it could just provide a widget to activate a program defined in another header and independent from the widget. + As you can see in the example above, the controls used in the widget (build_ui function) must be added to "TimeOutPlugin". In this case, the widget works as a standalone application, but it can just provide a widget to activate a program defined in another header and independent from the widget.
  
 ===The .desktop File===  ===The .desktop File===
- Although other fields can be assigned in a .desktop file, the example bellow shows a simple .desktop file for the "TimeOut" widget. The "Name" field will be the widget's name in the list when the user is choosing widgets to add to the desktop. The "X-Path" field should be set to the .so file that was previously generated. + Although other fields can be assigned in a .desktop file, the example bellow shows a simple .desktop file for the "TimeOut" widget. The "Name" field is the widget's name in the list when the user is choosing widgets to add to the desktop. The "X-Path" field should be set to the .so file that was previously generated.
  
 Example 1.3. A .desktop file for the TimeOut widget: timeout-widget.desktop  Example 1.3. A .desktop file for the TimeOut widget: timeout-widget.desktop
Line 142:
Line 142:
  
                                       
- For Home Area widget, .desktop files should be placed in the directory outputed by the following command: + For Home Area widget, place .desktop files in the directory outputed by the following command:
  
   pkg-config libhildondesktop-1 --variable=hildonhomedesktopentrydir    pkg-config libhildondesktop-1 --variable=hildonhomedesktopentrydir
  
 ==Status Menu widgets==  ==Status Menu widgets==
- Status Menu widgets are placed in the Status Menu and can be divided into three categories: permanent, conditional and temporary. Permanent widgets are shown all the time. Conditional and temporary widgets are shown when a certain condition is fulfilled. + Status Menu widgets are located in the Status Menu and can be divided into three categories: permanent, conditional and temporary. Permanent widgets are shown all the time. Conditional and temporary widgets are shown when a certain condition is fulfilled.
  
- The way to write a widget for the Status Menu is pretty similar to writing it for the Home Area. The widget should inherit from HDStatusMenuItem. The next examples present a Status Menu widget which only shows a message when clicked. + The way to write a widget for the Status Menu is pretty similar to writing it for the Home Area. The widget inherits from HDStatusMenuItem. The next examples present a Status Menu widget which only shows a message when clicked.
  
 Example 1.4. Header file for Example Status Menu Widget: lib-example-status-menu-widget.h  Example 1.4. Header file for Example Status Menu Widget: lib-example-status-menu-widget.h
Line 256:
Line 256:
                       
 ===The .desktop File===  ===The .desktop File===
- The .desktop file for the Status Menu is analogous to the Home Area one but should also contain the "Category" field where the priority of the widget is set (permanent, conditional or temporary) and the "Icon" field to set the icon's name. If the "Category" key is not set, it is considered as permanent. + The .desktop file for the Status Menu is similar to the Home Area one but also contains the "Category" field where the priority of the widget is set (permanent, conditional or temporary) and the "Icon" field to set the icon's name. If the "Category" key is not set, it is considered as permanent.
  
 Example 1.6. A .desktop file for the Status Menu example widget: lib-example-widget.desktop  Example 1.6. A .desktop file for the Status Menu example widget: lib-example-widget.desktop
Line 278:
Line 278:
   gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so    gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so
  
- Status Menu and Home Area widgets binaries should be placed in the same directory, so, assign distinguishable names to them. For example, "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files should be copied to is given by the following command (which normally outputs "/usr/share/applications/hildon-desktop"): + Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/share/applications/hildon-desktop"):
  
   pkg-config libhildondesktop-1 --variable=hildondesktoplibdir    pkg-config libhildondesktop-1 --variable=hildondesktoplibdir




tatiana: Status Menu widget .desktop dir
2009-09-04T13:40:29Z
Status Menu widget .desktop dir

		
		
		
		
		
		
		← Older revision
		Revision as of 13:40, 4 September 2009
		
		Line 269:
Line 269:
  
                                       
- For Home Area widget, .desktop files should be placed in the directory outputed by the following command: + For Status Menu widget, .desktop files should be placed in the directory outputted by the following command:
  
-   pkg-config libhildondesktop-1 --variable=homedesktopentrydir +   pkg-config libhildondesktop-1 --variable=hildonstatusmenudesktopentrydir
  
 ==Building Widgets==  ==Building Widgets==




tatiana: /* The .desktop File */
2009-09-04T13:33:34Z
The .desktop File

		
		
		
		
		
		
		← Older revision
		Revision as of 13:33, 4 September 2009
		
		Line 144:
Line 144:
 For Home Area widget, .desktop files should be placed in the directory outputed by the following command:  For Home Area widget, .desktop files should be placed in the directory outputed by the following command:
  
-   pkg-config libhildondesktop-1 --variable=hildonhomedesktopentrydir --variable=homedesktopentrydir +   pkg-config libhildondesktop-1 --variable=hildonhomedesktopentrydir
  
 ==Status Menu widgets==  ==Status Menu widgets==




tatiana: /* Status Menu widgets */
2009-09-04T13:23:59Z
Status Menu widgets

		
		
		
		
		
		
		← Older revision
		Revision as of 13:23, 4 September 2009
		
		Line 209:
Line 209:
   #include <hildon/hildon.h>    #include <hildon/hildon.h>
         
-   #include "lib-example-status-menu-applet.h" +   #include "lib-example-status-menu-widget.h"
         
   #define EXAMPLE_STATUS_PLUGIN_GET_PRIVATE(obj) (G_TYPE_INSTANCE_GET_PRIVATE (obj,   \    #define EXAMPLE_STATUS_PLUGIN_GET_PRIVATE(obj) (G_TYPE_INSTANCE_GET_PRIVATE (obj,   \
Line 256:
Line 256:
                       
 ===The .desktop File===  ===The .desktop File===
- The .desktop file for the Status Menu is analogous to the Home Area one but should also contain the "Category" field where the priority of the applet is set (permanent, conditional or temporary) and the "Icon" field to set the icon's name. If the "Category" key is not set, it is considered as permanent. + The .desktop file for the Status Menu is analogous to the Home Area one but should also contain the "Category" field where the priority of the widget is set (permanent, conditional or temporary) and the "Icon" field to set the icon's name. If the "Category" key is not set, it is considered as permanent.
  
 Example 1.6. A .desktop file for the Status Menu example widget: lib-example-widget.desktop  Example 1.6. A .desktop file for the Status Menu example widget: lib-example-widget.desktop

← Older revision		Revision as of 14:44, 6 April 2010
Line 271:		Line 271:
	For Status Menu widget, .desktop files should be placed in the directory outputted by the following command:		For Status Menu widget, .desktop files should be placed in the directory outputted by the following command:

-	pkg-config ~~libhildondesktop-1~~ --variable=hildonstatusmenudesktopentrydir	+	pkg-config --variable=hildonstatusmenudesktopentrydir libhildondesktop-1

	==Building Widgets==		==Building Widgets==
	To use a widget, it needs to be built as a shared library. This is done by passing the -shared flag to gcc.		To use a widget, it needs to be built as a shared library. This is done by passing the -shared flag to gcc.

-	gcc -shared `pkg-config ~~hildon-1 libhildondesktop-1~~ --libs --cflags` widget.c -o lib-widget.so	+	gcc -shared `pkg-config --libs --cflags hildon-1 libhildondesktop-1` widget.c -o lib-widget.so

	Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/lib/hildon-desktop"):		Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/lib/hildon-desktop"):

-	pkg-config ~~libhildondesktop-1~~ --variable=hildondesktoplibdir	+	pkg-config --variable=hildondesktoplibdir libhildondesktop-1

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

← Older revision		Revision as of 12:00, 12 February 2010
Line 281:		Line 281:

	pkg-config libhildondesktop-1 --variable=hildondesktoplibdir		pkg-config libhildondesktop-1 --variable=hildondesktoplibdir
		+
		+	[[Category:Development]]
		+	[[Category:Documentation]]
		+	[[Category:Fremantle]]

← Older revision		Revision as of 09:28, 12 February 2010
Line 1:		Line 1:
	=Writing Desktop Widgets=		=Writing Desktop Widgets=
	The following code examples are used in this chapter:		The following code examples are used in this chapter:
-	* [https://~~garage~~.maemo.org/svn/maemoexamples/~~trunk~~/hildon-timeout-home-widget-example/ hildon-timeout-home-widget-example]	+	* [https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/hildon-timeout-home-widget-example/ hildon-timeout-home-widget-example]
-	* [https://~~garage~~.maemo.org/svn/maemoexamples/~~trunk~~/hildon-status-menu-widget-example/ hildon-status-menu-widget-example]	+	* [https://vcs.maemo.org/svn/maemoexamples/tags/maemo_5.0/hildon-status-menu-widget-example/ hildon-status-menu-widget-example]

	Desktop widgets are programs designed to provide a certain functionality from the desktop area. These programs are usually limited, in the sense that they are not complex applications, normally representing "small" utilities or an extension of an existing application.		Desktop widgets are programs designed to provide a certain functionality from the desktop area. These programs are usually limited, in the sense that they are not complex applications, normally representing "small" utilities or an extension of an existing application.

← Older revision		Revision as of 01:04, 6 December 2009
Line 278:		Line 278:
	gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so		gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so

-	Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/~~share/applications~~/hildon-desktop"):	+	Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/lib/hildon-desktop"):

	pkg-config libhildondesktop-1 --variable=hildondesktoplibdir		pkg-config libhildondesktop-1 --variable=hildondesktoplibdir

← Older revision		Revision as of 08:16, 25 September 2009
Line 8:		Line 8:
	Desktop widgets are written as shared libraries and need also to provide a desktop file that describes them. Depending on their placement, they can be Status Menu widgets or Home Area widgets.		Desktop widgets are written as shared libraries and need also to provide a desktop file that describes them. Depending on their placement, they can be Status Menu widgets or Home Area widgets.

-	They ~~need to~~ have a .desktop file describing them. The file contents are fields that describe certain properties of the widget.	+	They must have a .desktop file describing them. The file contents are fields that describe certain properties of the widget.


Line 16:		Line 16:
	To better show how to write a Home Area widget, consider a widget "TimeOut" that allows the user to choose an action to be performed at a given time.		To better show how to write a Home Area widget, consider a widget "TimeOut" that allows the user to choose an action to be performed at a given time.

-	Home widgets ~~should~~ inherit from libhildondesktop's HDHomePluginItem. The following example presents a header file for the mentioned widget.	+	Home widgets must inherit from libhildondesktop's HDHomePluginItem. The following example presents a header file for the mentioned widget.

	'''Example 1.1. Header file for TimeOut widget: lib-timeout-home-widget.h'''		'''Example 1.1. Header file for TimeOut widget: lib-timeout-home-widget.h'''
Line 66:		Line 66:


-	The first and more important function is HD_DEFINE_PLUGIN_MODULE. This function receives three parameters to register the object that is supplied by the plug-in. The first argument ~~should be~~ the object type name in Camel case, the second is the type name in lowercase with underscores separating the words. The third is the GType of the object's parent. Apart from this macro, three other functions ~~should be used~~. The name of the functions ~~should be~~ the name given as second argument to HD_DEFINE_PLUGIN_MODULE with the suffixes _init, _class_init and _class_finalize.	+	The first and more important function is HD_DEFINE_PLUGIN_MODULE. This function receives three parameters to register the object that is supplied by the plug-in. The first argument is the object type name in Camel case, the second is the type name in lowercase with underscores separating the words. The third is the GType of the object's parent. Apart from this macro, use also three other functions. The name of the functions is the name given as second argument to HD_DEFINE_PLUGIN_MODULE with the suffixes _init, _class_init and _class_finalize.

	The following example shows the source code for "TimeOut" widget.		The following example shows the source code for "TimeOut" widget.
Line 128:		Line 128:


-	As you can see in the example above, the controls used in the widget (build_ui function) ~~should~~ be added to "TimeOutPlugin". In this case, the widget works as a standalone application, but it ~~could~~ just provide a widget to activate a program defined in another header and independent from the widget.	+	As you can see in the example above, the controls used in the widget (build_ui function) must be added to "TimeOutPlugin". In this case, the widget works as a standalone application, but it can just provide a widget to activate a program defined in another header and independent from the widget.

	===The .desktop File===		===The .desktop File===
-	Although other fields can be assigned in a .desktop file, the example bellow shows a simple .desktop file for the "TimeOut" widget. The "Name" field ~~will be~~ the widget's name in the list when the user is choosing widgets to add to the desktop. The "X-Path" field should be set to the .so file that was previously generated.	+	Although other fields can be assigned in a .desktop file, the example bellow shows a simple .desktop file for the "TimeOut" widget. The "Name" field is the widget's name in the list when the user is choosing widgets to add to the desktop. The "X-Path" field should be set to the .so file that was previously generated.

	Example 1.3. A .desktop file for the TimeOut widget: timeout-widget.desktop		Example 1.3. A .desktop file for the TimeOut widget: timeout-widget.desktop
Line 142:		Line 142:


-	For Home Area widget, .desktop files ~~should be placed~~ in the directory outputed by the following command:	+	For Home Area widget, place .desktop files in the directory outputed by the following command:

	pkg-config libhildondesktop-1 --variable=hildonhomedesktopentrydir		pkg-config libhildondesktop-1 --variable=hildonhomedesktopentrydir

	==Status Menu widgets==		==Status Menu widgets==
-	Status Menu widgets are ~~placed~~ in the Status Menu and can be divided into three categories: permanent, conditional and temporary. Permanent widgets are shown all the time. Conditional and temporary widgets are shown when a certain condition is fulfilled.	+	Status Menu widgets are located in the Status Menu and can be divided into three categories: permanent, conditional and temporary. Permanent widgets are shown all the time. Conditional and temporary widgets are shown when a certain condition is fulfilled.

-	The way to write a widget for the Status Menu is pretty similar to writing it for the Home Area. The widget ~~should inherit~~ from HDStatusMenuItem. The next examples present a Status Menu widget which only shows a message when clicked.	+	The way to write a widget for the Status Menu is pretty similar to writing it for the Home Area. The widget inherits from HDStatusMenuItem. The next examples present a Status Menu widget which only shows a message when clicked.

	Example 1.4. Header file for Example Status Menu Widget: lib-example-status-menu-widget.h		Example 1.4. Header file for Example Status Menu Widget: lib-example-status-menu-widget.h
Line 256:		Line 256:

	===The .desktop File===		===The .desktop File===
-	The .desktop file for the Status Menu is ~~analogous~~ to the Home Area one but ~~should~~ also ~~contain~~ the "Category" field where the priority of the widget is set (permanent, conditional or temporary) and the "Icon" field to set the icon's name. If the "Category" key is not set, it is considered as permanent.	+	The .desktop file for the Status Menu is similar to the Home Area one but also contains the "Category" field where the priority of the widget is set (permanent, conditional or temporary) and the "Icon" field to set the icon's name. If the "Category" key is not set, it is considered as permanent.

	Example 1.6. A .desktop file for the Status Menu example widget: lib-example-widget.desktop		Example 1.6. A .desktop file for the Status Menu example widget: lib-example-widget.desktop
Line 278:		Line 278:
	gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so		gcc -shared `pkg-config hildon-1 libhildondesktop-1 --libs --cflags` widget.c -o lib-widget.so

-	Status Menu and Home Area widgets binaries ~~should be placed~~ in the same directory, so, assign distinguishable names to them~~. For example~~, "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files ~~should be~~ copied to is given by the following command (which normally outputs "/usr/share/applications/hildon-desktop"):	+	Status Menu and Home Area widgets binaries are located in the same directory, so assign distinguishable names to them, such as "lib-example-home-widget.so" and "lib-example-status-menu-widget.so" for the Home Area and Status Menu widgets, respectively. The directory where the binary files are copied to is given by the following command (which normally outputs "/usr/share/applications/hildon-desktop"):

	pkg-config libhildondesktop-1 --variable=hildondesktoplibdir		pkg-config libhildondesktop-1 --variable=hildondesktoplibdir

← Older revision		Revision as of 13:40, 4 September 2009
Line 269:		Line 269:


-	For ~~Home Area~~ widget, .desktop files should be placed in the directory ~~outputed~~ by the following command:	+	For Status Menu widget, .desktop files should be placed in the directory outputted by the following command:

-	pkg-config libhildondesktop-1 --variable=~~homedesktopentrydir~~	+	pkg-config libhildondesktop-1 --variable=hildonstatusmenudesktopentrydir

	==Building Widgets==		==Building Widgets==

← Older revision		Revision as of 13:33, 4 September 2009
Line 144:		Line 144:
	For Home Area widget, .desktop files should be placed in the directory outputed by the following command:		For Home Area widget, .desktop files should be placed in the directory outputed by the following command:

-	pkg-config libhildondesktop-1 --variable=hildonhomedesktopentrydir ~~--variable=homedesktopentrydir~~	+	pkg-config libhildondesktop-1 --variable=hildonhomedesktopentrydir

	==Status Menu widgets==		==Status Menu widgets==

← Older revision		Revision as of 13:23, 4 September 2009
Line 209:		Line 209:
	#include <hildon/hildon.h>		#include <hildon/hildon.h>

-	#include "lib-example-status-menu-~~applet~~.h"	+	#include "lib-example-status-menu-widget.h"

	#define EXAMPLE_STATUS_PLUGIN_GET_PRIVATE(obj) (G_TYPE_INSTANCE_GET_PRIVATE (obj, \		#define EXAMPLE_STATUS_PLUGIN_GET_PRIVATE(obj) (G_TYPE_INSTANCE_GET_PRIVATE (obj, \
Line 256:		Line 256:

	===The .desktop File===		===The .desktop File===
-	The .desktop file for the Status Menu is analogous to the Home Area one but should also contain the "Category" field where the priority of the ~~applet~~ is set (permanent, conditional or temporary) and the "Icon" field to set the icon's name. If the "Category" key is not set, it is considered as permanent.	+	The .desktop file for the Status Menu is analogous to the Home Area one but should also contain the "Category" field where the priority of the widget is set (permanent, conditional or temporary) and the "Icon" field to set the icon's name. If the "Category" key is not set, it is considered as permanent.

	Example 1.6. A .desktop file for the Status Menu example widget: lib-example-widget.desktop		Example 1.6. A .desktop file for the Status Menu example widget: lib-example-widget.desktop