2 * @page Examples Examples
4 * Here is a page with Elementary examples.
6 * @ref bg_01_example_page
8 * @ref bg_02_example_page
10 * @ref bg_03_example_page
12 * @ref actionslider_example_page
14 * @ref transit_example_01_explained
16 * @ref transit_example_02_explained
18 * @ref general_functions_example_page
20 * @ref calendar_example_01
22 * @ref calendar_example_02
24 * @ref calendar_example_03
26 * @ref calendar_example_04
28 * @ref calendar_example_05
30 * @ref calendar_example_06
32 * @ref spinner_example
40 * @ref datetime_example
42 * @ref dayselector_example
52 * @ref diskselector_example_01
54 * @ref diskselector_example_02
56 * @ref list_example_01
58 * @ref list_example_02
60 * @ref list_example_03
62 * @ref toolbar_example_01
64 * @ref toolbar_example_02
66 * @ref toolbar_example_03
68 * @ref segment_control_example
70 * @ref flipselector_example
72 * @ref fileselector_example
74 * @ref fileselector_button_example
76 * @ref fileselector_entry_example
78 * @ref index_example_01
80 * @ref index_example_02
82 * @ref gengrid_example
84 * @ref genlist_example_01
86 * @ref genlist_example_02
88 * @ref genlist_example_03
90 * @ref genlist_example_04
92 * @ref genlist_example_05
94 * @ref thumb_example_01
96 * @ref progressbar_example
98 * @ref slideshow_example
114 * @page bg_01_example_page elm_bg - Plain color background.
115 * @dontinclude bg_example_01.c
117 * The full code for this example can be found at @ref bg_example_01_c,
118 * in the function @c test_bg_plain. It's part of the @c elementar_test
119 * suite, and thus has the code for the three examples referenced by this
122 * This first example just sets a default background with a plain color. The
123 * first part consists of creating an Elementary window. It's the common
124 * piece of code that you'll see everywhere in Elementary: @skip elm_main
127 * Now we really create our background object, using the window object as
132 * Then we set the size hints of the background object so that it will use
133 * all space available for it, and then add it as a resize object to the
134 * window, making it visible in the end:
136 * @skip size_hint_weight_set
137 * @until resize_object_add
139 * See @ref evas_object_size_hint_weight_set and elm_win_resize_object_add()
140 * for more detailed info about these functions.
142 * The end of the example is quite simple, just setting the minimum and
143 * maximum size of the background, so the Elementary window knows that it
144 * has to have at least the minimum size. The background also won't scale to
145 * a size above its maximum. Then we resize the window and show it in the
148 * @skip set size hints
151 * And here we finish our very simple background object usage example.
155 * @page bg_02_example_page elm_bg - Image background.
156 * @dontinclude bg_example_02.c
158 * The full code for this example can be found at @ref bg_example_02_c,
159 * in the function @c test_bg_image. It's part of the @c elementar_test
160 * suite, and thus has the code for the three examples referenced by this
163 * This is the second example, and shows how to use the Elementary
164 * background object to set an image as background of your application.
166 * We start this example exactly in the same way as the previous one, even
167 * when creating the background object:
172 * Now it's the different part.
174 * Our background will have an image, that will be displayed over the
175 * background color. Before loading the image, we set the load size of the
176 * image. The load size is a hint about the size that we want the image
177 * displayed in the screen. It's not the exact size that the image will have,
178 * but usually a bit bigger. The background object can still be scaled to a
179 * size bigger than the one set here. Setting the image load size to
180 * something smaller than its real size will reduce the memory used to keep
181 * the pixmap representation of the image, and the time to load it. Here we
182 * set the load size to 20x20 pixels, but the image is loaded with a size
183 * bigger than that (since it's just a hint):
185 * @skipline load_size_set
187 * And set our background image to be centered, instead of stretched or
188 * scaled, so the effect of the elm_bg_load_size_set() can be easily
191 * @skipline option_set
193 * We need a filename to set, so we get one from the previous installed
194 * images in the @c PACKAGE_DATA_DIR, and write its full path to a buffer.
195 * Then we use this buffer to set the filename in the background object:
200 * Notice that the third argument of the elm_bg_file_set() function is @c
201 * NULL, since we are setting an image to this background. This function
202 * also supports setting an edje group as background, in which case the @c
203 * group parameter wouldn't be @c NULL, but be the name of the group
206 * Finally, we can set the size hints, add the background as a resize
207 * object, and resize the window, exactly the same thing we do in the @ref
208 * bg_01_example_page example:
213 * And this is the end of this example.
215 * This example will look like this:
217 * @image html screenshots/bg_01.png
218 * @image latex screenshots/bg_01.eps width=\textwidth
222 * @page bg_03_example_page elm_bg - Background properties.
223 * @dontinclude bg_example_03.c
225 * The full code for this example can be found at @ref bg_example_03_c, in the
226 * function @c test_bg_options, with the callbacks @c _cb_overlay_changed, @c
227 * _cb_color_changed and @c _cb_radio_changed defined in the beginning of the
228 * file. It's part of the @c elementar_test suite, and thus has the code for
229 * the three examples referenced by this documentation.
231 * This example will show the properties available for the background object,
232 * and will use of some more widgets to set them.
234 * In order to do this, we will set some callbacks for these widgets. The
235 * first is for the radio buttons that will be used to choose the option
236 * passed as argument to elm_bg_option_set():
238 * @skip _cb_radio_changed
241 * The next callback will be used when setting the overlay (using
242 * elm_object_content_set()):
244 * @skip _cb_overlay_changed
248 * And the last one, used to set the color (with elm_bg_color_set()):
250 * @skip _cb_color_changed
253 * We will get back to what these functions do soon. If you want to know more
254 * about how to set these callbacks and what these widgets are, look for:
255 * @li elm_radio_add()
256 * @li elm_check_add()
257 * @li elm_spinner_add()
259 * Now going to the main function, @c test_bg_options, we have the common
260 * code with the other examples:
265 * We add a plain background to this window, so it will have the default
266 * background color behind everything:
268 * @skip bg = elm_bg_add
269 * @until evas_object_show(bg)
271 * Then we add a vertical box (elm_box_add()) that will hold the background
272 * object that we are going to play with, as well as a horizontal box that
276 * @until evas_object_show
278 * Now we add the background object that is going to be of use for our
279 * example. It is an image background, as used in @ref bg_02_example_page ,
280 * so the code should be familiar:
283 * @until evas_object_show
285 * Notice the call to elm_box_pack_end(): it will pack the background object
286 * in the end of the Elementary box declared above. Just refer to that
287 * documentation for more info.
289 * Since this Elementary background is already an image background, we are
290 * going to play with its other properties. We will change its option
291 * (CENTER, SCALE, STRETCH, TILE), its color (RGB), and add an overlay to it.
292 * For all of these properties, we are going to add widgets that will
295 * First, lets add the horizontal box that will hold these widgets:
299 * For now, just consider this @c hbox as a rectangle that will contain the
300 * widgets, and will distribute them horizontally inside its content. Then we
301 * add radio buttons that will allow us to choose the property to use with
305 * @until evas_object_show
307 * Again, I won't give details about the use of these widgets, just look for
308 * their documentation if necessary. It's enough to know for now that we are
309 * packing them in the @c hbox, setting a label for them, and the most
310 * important parts: setting its value to @c ELM_BG_OPTION_CENTER and its
311 * callback to @c _cb_radio_changed (the function defined in the beginning of
312 * this example). We do this for the next 3 radio buttons added after this
313 * one, each of them with a different value.
315 * Now taking a look at the code of the callback @c _cb_radio_changed again,
316 * it will call elm_bg_option_set() with the value set from the checked radio
317 * button, thus setting the option for this background. The background is
318 * passed as argument to the @p data parameter of this callback, and is
319 * referenced here as @c o_bg.
321 * Later we set the default value for this radio button:
323 * @skipline elm_radio_value_set
325 * Then we add a checkbox for the elm_object_content_set() function for the bg:
328 * @until evas_object_show
330 * Now look at the code of the @c _cb_overlay_changed again. If the checkbox
331 * state is checked, an overlay will be added to the background. It's done by
332 * creating an Edje object, and setting it with elm_object_content_set() to the
333 * background object. For information about what are and how to set Edje
334 * object, look at the Edje documentation.
336 * Finally we add a spinner object (elm_spinner_add()) to be used to select
337 * the color of our background. In its callback it's possible to see the call
338 * to elm_bg_color_set(), which will change the color of this background.
339 * This color is used by the background to fill areas where the image doesn't
340 * cover (in this case, where we have an image background). The spinner is
341 * also packed into the @c hbox :
343 * @skip elm_spinner_add
344 * @until evas_object_show
346 * Then we just have to pack the @c hbox inside the @c box, set some size
347 * hints, and show our window:
352 * Now to see this code in action, open elementary_test, and go to the "Bg
353 * Options" test. It should demonstrate what was implemented here.
357 * @page actionslider_example_page Actionslider usage
358 * @dontinclude actionslider_example_01.c
360 * For this example we are going to assume knowledge of evas smart callbacks
361 * and some basic evas object functions. Elementary is not meant to be used
362 * without evas, if you're not yet familiar with evas it probably is worth
365 * And now to the example, when using Elementary we start by including
369 * Next we define some callbacks, they all share the same signature because
370 * they are all to be used with evas_object_smart_callback_add().
371 * The first one just prints the selected label(in two different ways):
374 * This next callback is a little more interesting, it makes the selected
375 * label magnetic(except if it's the center label):
378 * This callback enables or disables the magnetic propertty of the center
382 * And finally a callback to stop the main loop when the window is closed:
385 * To be able to create our actionsliders we need to do some setup, but this
386 * isn't really relevant here, so if you want to know about that go @ref
389 * With all that boring stuff out of the way we can proceed to creating some
391 * All actionsliders are created the same way:
392 * @skipline actionslider_add
393 * Next we must choose where the indicator starts, and for this one we choose
394 * the right, and set the right as magnetic:
395 * @skipline indicator_pos_set
396 * @until magnet_pos_set
398 * We then set the labels for the left and right, passing NULL as an argument
399 * to any of the labels makes that position have no label.
402 * Furthermore we mark both left and right as enabled positions, if we didn't
403 * do this all three positions would be enabled:
406 * Having the the enabled positions we now add a smart callback to change
407 * which position is magnetic, so that only the last selected position is
411 * And finally we set our printing callback and show the actionslider:
415 * For our next actionslider we are going to do much as we did for the
416 * previous except we are going to have the center as the magnet(and not
418 * @skipline actionslider_add
419 * @skipline indicator_pos_set
422 * And another actionslider, in this one the indicator starts on the left.
423 * It has labels only in the center and right, and both bositions are
424 * magnetic. Because the left doesn't have a label and is not magnetic once
425 * the indicator leaves it can't return:
426 * @skipline actionslider_add
427 * @skipline indicator_pos_set
429 * @note The greyed out area is a @ref Styles "style".
431 * And now an actionslider with a label in the indicator, and whose magnet
432 * properties change based on what was last selected:
433 * @skipline actionslider_add
434 * @skipline indicator_pos_set
436 * @note The greyed out area is a @ref Styles "style".
438 * We are almost done, this next one is just an actionslider with all
439 * positions magnetized and having every possible label:
440 * @skipline actionslider_add
441 * @skipline indicator_pos_set
444 * And for our last actionslider we have one that turns the magnetic property
446 * @skipline actionslider_add
447 * @skipline indicator_pos_set
450 * The example will look like this:
452 * @image html screenshots/actionslider_01.png
453 * @image latex screenshots/actionslider_01.eps width=\textwidth
455 * See the full source code @ref actionslider_example_01 "here"
459 * @page transit_example_03_c elm_transit - Combined effects and options.
461 * This example shows how to apply the following transition effects:
469 * It allows you to apply more than one effect at once, and also allows to
470 * set properties like event_enabled, auto_reverse, repeat_times and
473 * @include transit_example_03.c
477 * @page transit_example_04_c elm_transit - Combined effects over two objects.
479 * This example shows how to apply the transition effects:
484 * over two objects. This kind of transition effect is used to make one
485 * object disappear and another one appear on its place.
487 * You can mix more than one effect of this type on the same objects, and the
488 * transition will apply both.
490 * @include transit_example_04.c
494 * @page transit_example_01_explained elm_transit - Basic transit usage.
495 * @dontinclude transit_example_01.c
497 * The full code for this example can be found at @ref transit_example_01_c.
499 * This example shows the simplest way of creating a transition and applying
500 * it to an object. Similarly to every other elementary example, we create a
501 * window, set its title, size, autodel property, and setup a callback to
502 * exit the program when finished:
505 * @until evas_object_resize
507 * We also add a resizable white background to use behind our animation:
510 * @until evas_object_show
512 * And then we add a button that we will use to demonstrate the effects of
516 * @until evas_object_show(win)
518 * Notice that we are not adding the button with elm_win_resize_object_add()
519 * because we don't want the window to control the size of the button. We
520 * will use the transition to change the button size, so it could conflict
521 * with something else trying to control that size.
523 * Now, the simplest code possible to create the resize animation:
528 * As you can see, this code is very easy to understand. First, we create the
529 * transition itself with elm_transit_add(). Then we add the button to this
530 * transition with elm_transit_object_add(), which means that the transition
531 * will operate over this button. The effect that we want now is changing the
532 * object size from 100x50 to 300x150, and can be achieved by adding the
533 * resize effect with elm_transit_effect_resizing_add().
535 * Finally, we set the transition time to 5 seconds and start the transition
536 * with elm_transit_go(). If we wanted more effects applied to this
537 * button, we could add them to the same transition. See the
538 * @ref transit_example_03_c to watch many transitions being applied to an
543 * @page transit_example_02_explained elm_transit - Chained transitions.
544 * @dontinclude transit_example_02.c
546 * The full code for this example can be found at @ref transit_example_02_c.
548 * This example shows how to implement a chain of transitions. This chain is
549 * used to start a transition just after another transition ended. Similarly
550 * to every other elementary example, we create a window, set its title,
551 * size, autodel property, and setup a callback to exit the program when
555 * @until evas_object_resize
557 * We also add a resizable white background to use behind our animation:
560 * @until evas_object_show
562 * This example will have a chain of 4 transitions, each of them applied to
563 * one button. Thus we create 4 different buttons:
566 * @until evas_object_show(bt4)
568 * Now we create a simple translation transition that will be started as soon
569 * as the program loads. It will be our first transition, and the other
570 * transitions will be started just after this transition ends:
575 * The code displayed until now has nothing different from what you have
576 * already seen in @ref transit_example_01_explained, but now comes the new
577 * part: instead of creating a second transition that will start later using
578 * a timer, we create the it normally, and use
579 * elm_transit_chain_transit_add() instead of elm_transit_go. Since we are
580 * adding it in a chain after the first transition, it will start as soon as
581 * the first transition ends:
584 * @until transit_chain_transit_add
586 * Finally we add the 2 other transitions to the chain, and run our program.
587 * It will make one transition start after the other finish, and there is the
592 * @page general_functions_example_page General (top-level) functions example
593 * @dontinclude general_funcs_example.c
595 * As told in their documentation blocks, the
596 * elm_app_compile_*_dir_set() family of functions have to be called
597 * before elm_app_info_set():
598 * @skip tell elm about
599 * @until elm_app_info_set
601 * We are here setting the fallback paths to the compiling time target
602 * paths, naturally. If you're building the example out of the
603 * project's build system, we're assuming they are the canonical ones.
605 * After the program starts, elm_app_info_set() will actually run and
606 * then you'll see an intrincasy: Elementary does the prefix lookup @b
607 * twice. This is so because of the quicklaunch infrastructure in
608 * Elementary (@ref Start), which will register a predefined prefix
609 * for possible users of the launch schema. We're not hooking into a
610 * quick launch, so this first call can't be avoided.
612 * If you ran this example from your "bindir" installation
613 * directiory, no output will emerge from these both attempts -- it
614 * will find the "magic" file there registered and set the prefixes
615 * silently. Otherwise, you could get something like:
617 WARNING: Could not determine its installed prefix for 'ELM'
618 so am falling back on the compiled in default:
620 implied by the following:
623 datadir = usr/share/elementary
624 localedir = usr/share/locale
625 Try setting the following environment variables:
626 ELM_PREFIX - points to the base prefix of install
627 or the next 4 variables
628 ELM_BIN_DIR - provide a specific binary directory
629 ELM_LIB_DIR - provide a specific library directory
630 ELM_DATA_DIR - provide a specific data directory
631 ELM_LOCALE_DIR - provide a specific locale directory
633 * if you also didn't change those environment variables (remember
634 * they are also a valid way of communicating your prefix to the
635 * binary) - this is the scenario where it fallbacks to the paths set
638 * Then, you can check the prefixes set on the standard output:
639 * @skip prefix was set to
640 * @until locale directory is
643 * @skip by using this policy
644 * @until elm_win_autodel_set
645 * we demonstrate the use of Elementary policies. The policy defining
646 * under which circunstances our application should quit automatically
647 * is set to when its last window is closed (this one has just one
648 * window, though). This will save us from having to set a callback
649 * ourselves on the window, like done in @ref bg_example_01_c "this"
650 * example. Note that we need to tell the window to delete itself's
651 * object on a request to destroy the canvas coming, with
652 * elm_win_autodel_set().
654 * What follows is some boilerplate code, creating a frame with a @b
655 * button, our object of interest, and, below, widgets to change the
656 * button's behavior and exemplify the group of functions in question.
658 * @dontinclude general_funcs_example.c
659 * We enabled the focus highlight object for this window, so that you
660 * can keep track of the current focused object better:
661 * @skip elm_win_focus_highlight_enabled_set
662 * @until evas_object_show
663 * Use the tab key to navigate through the focus chain.
665 * @dontinclude general_funcs_example.c
666 * While creating the button, we exemplify how to use Elementary's
667 * finger size information to scale our UI:
668 * @skip fprintf(stdout, "Elementary
669 * @until evas_object_show
671 * @dontinclude general_funcs_example.c
672 * The first checkbox's callback is:
675 * When unsetting the checkbox, we disable the button, which will get a new
676 * decoration (greyed out) and stop receiving events. The focus chain
677 * will also ignore it.
679 * Following, there are 2 more buttons whose actions are focus/unfocus
680 * the top button, respectively:
681 * @skip focus callback
684 * @skip unfocus callback
686 * Note the situations in which they won't take effect:
687 * - the button is not allowed to get focus or
688 * - the button is disabled
690 * The first restriction above you'll get by a second checkbox, whose
692 * @skip focus allow callback
694 * Note that the button will still get mouse events, though.
696 * Next, there's a slider controlling the button's scale:
697 * @skip scaling callback
700 * Experiment with it, so you understand the effect better. If you
701 * change its value, it will mess with the button's original size,
704 * The full code for this example can be found
705 * @ref general_functions_example_c "here".
709 * @page theme_example_01 Theme - Using extensions
711 * @dontinclude theme_example_01.c
713 * Using extensions is extremely easy, discarding the part where you have to
714 * write the theme for them.
716 * In the following example we'll be creating two buttons, one to load or
717 * unload our extension theme and one to cycle around three possible styles,
718 * one of which we created.
720 * After including our one and only header we'll jump to the callback for
721 * the buttons. First one takes care of loading or unloading our extension
722 * file, relative to the default theme set (thus the @c NULL in the
723 * functions first parameter).
724 * @skipline Elementary.h
730 * The second button, as we said before, will just switch around different
731 * styles. In this case we have three of them. The first one is our custom
732 * style, named after something very unlikely to find in the default theme.
733 * The other two styles are the standard and one more, anchor, which exists
734 * in the default and is similar to the default, except the button vanishes
735 * when the mouse is not over it.
740 * So what happens if the style switches to our custom one when the
741 * extension is loaded? Elementary falls back to the default for the
744 * And the main function, simply enough, will create the window, set the
745 * buttons and their callbacks, and just to begin with our button styled
746 * we're also loading our extension at the beginning.
750 * In this case we wanted to easily remove extensions, but all adding an
751 * extension does is tell Elementary where else it should look for themes
752 * when it can't find them in the default theme. Another way to do this
753 * is to set the theme search order using elm_theme_set(), but this requires
754 * that the developer is careful not to override any user configuration.
755 * That can be helped by adding our theme to the end of whatver is already
756 * set, like in the following snippet.
759 * snprintf(buf, sizeof(buf), "%s:./theme_example.edj", elme_theme_get(NULL);
760 * elm_theme_set(NULL, buf);
763 * If we were using overlays instead of extensions, the same thing applies,
764 * but the custom theme must be added to the front of the search path.
766 * In the end, we should be looking at something like this:
768 * @image html screenshots/theme_example_01.png
769 * @image latex screenshots/theme_example_01.eps width=\textwidth
771 * That's all. Boringly simple, and the full code in one piece can be found
772 * @ref theme_example_01.c "here".
774 * And the code for our extension is @ref theme_example.edc "here".
776 * @example theme_example_01.c
777 * @example theme_example.edc
781 * @page theme_example_02 Theme - Using overlays
783 * @dontinclude theme_example_02.c
785 * Overlays are like extensions in that you tell Elementary that some other
786 * theme contains the styles you need for your program. The difference is that
787 * they will be look in first, so they can override the default style of any
790 * There's not much to say about them that hasn't been said in our previous
791 * example about @ref theme_example_01 "extensions", so going quickly through
792 * the code we have a function to load or unload the theme, which will be
793 * called when we click any button.
794 * @skipline Elementary.h
798 * And the main function, creating the window and adding some buttons to it.
799 * We load our theme as an overlay and nothing else. Notice there's no style
800 * set for any button there, which means they should be using the default
805 * That's pretty much it. The full code is @ref theme_example_02.c "here" and
806 * the definition of the theme is the same as before, and can be found in
807 * @ref theme_example.edc "here".
809 * @example theme_example_02.c
813 * @page button_example_01 Button - Complete example
815 * @dontinclude button_example_01.c
817 * A button is simple, you click on it and something happens. That said,
818 * we'll go through an example to show in detail the button API less
821 * In the end, we'll be presented with something that looks like this:
823 * @image html screenshots/button_01.png
824 * @image latex screenshots/button_01.eps width=\textwidth
826 * The full code of the example is @ref button_example_01.c "here" and we
827 * will follow here with a rundown of it.
830 * @until Elementary.h
834 * We have several buttons to set different times for the autorepeat timeouts
835 * of the buttons that use it and a few more that we keep track of in our
836 * data struct. The mid button doesn't do much, just moves around according
837 * to what other buttons the user presses. Then four more buttons to move the
838 * central one, and we're also keeping track of the icon set in the middle
839 * button, since when this one moves, we change the icon, and when movement
840 * is finished (by releasing one of the four arrow buttons), we set back the
845 * Keeping any of those four buttons pressed will trigger their autorepeat
846 * callback, where we move the button doing some size hint magic. To
847 * understand how that works better, refer to the @ref Box documentation.
848 * Also, the first time the function is called, we change the icon in the
849 * middle button, using elm_object_content_unset() first to keep the reference
850 * to the previous one, so we don't need to recreate it when we are done
854 * @until size_hint_align_set
857 * One more callback for the option buttons, that just sets the timeouts for
858 * the different autorepeat options.
865 * And the main function, which does some setting up of the buttons in boxes
866 * to make things work. Here we'll go through some snippets only.
868 * For the option buttons, it's just the button with its label and callback.
869 * @skip elm_button_add
870 * @until smart_callback_add
872 * For the ones that move the central button, we have no labels. There are
873 * icons instead, and the autorepeat option is toggled.
875 * @skip elm_button_add
876 * @until data.cursors.up
878 * And just to show the mid button, which doesn't have anything special.
879 * @skip data.cursors.left
880 * @skip elm_button_add
885 * @example button_example_01.c
889 * @page bubble_01_example_page elm_bubble - Simple use.
890 * @dontinclude bubble_example_01.c
892 * This example shows a bubble with all fields set(label, info, content and
893 * icon) and the selected corner changing when the bubble is clicked. To be
894 * able use a bubble we need to do some setup and create a window, for this
895 * example we are going to ignore that part of the code since it isn't
896 * relevant to the bubble.
898 * To have the selected corner change in a clockwise motion we are going to
899 * use the following callback:
904 * Here we are creating an elm_label that is going to be used as the content
906 * @skipline elm_label
908 * @note You could use any evas_object for this, we are using an elm_label
911 * Despite it's name the bubble's icon doesn't have to be an icon, it can be
912 * any evas_object. For this example we are going to make the icon a simple
916 * And finally we have the actual bubble creation and the setting of it's
917 * label, info and content:
920 * @note Because we didn't set a corner, the default("top_left") will be
923 * Now that we have our bubble all that is left is connecting the "clicked"
924 * signals to our callback:
925 * @line smart_callback
927 * This last bubble we created was very complete, so it's pertinent to show
928 * that most of that stuff is optional a bubble can be created with nothing
933 * Our example will look like this:
935 * @image html screenshots/bubble_example_01.png
936 * @image latex screenshots/bubble_example_01.eps width=\textwidth
938 * See the full source code @ref bubble_example_01.c here.
939 * @example bubble_example_01.c
943 * @page box_example_01 Box - Basic API
945 * @dontinclude button_example_01.c
947 * As a special guest tonight, we have the @ref button_example_01 "simple
948 * button example". There are plenty of boxes in it, and to make the cursor
949 * buttons that moved a central one around when pressed, we had to use a
950 * variety of values for their hints.
952 * To start, let's take a look at the handling of the central button when
953 * we were moving it around. To achieve this effect without falling back to
954 * a complete manual positioning of the @c Evas_Object in our canvas, we just
955 * put it in a box and played with its alignment within it, as seen in the
956 * following snippet of the callback for the pressed buttons.
957 * @skip evas_object_size_hint_align_get
958 * @until evas_object_size_hint_align_set
960 * Not much to it. We get the current alignment of the object and change it
961 * by just a little, depending on which button was pressed, then set it
962 * again, making sure we stay within the 0.0-1.0 range so the button moves
963 * inside the space it has, instead of disappearing under the other objects.
965 * But as useful as an example as that may have been, the usual case with boxes
966 * is to set everything at the moment they are created, like we did for
967 * everything else in our main function.
969 * The entire layout of our program is made with boxes. We have one set as the
970 * resize object for the window, which means it will always be resized with
971 * the window. The weight hints set to @c EVAS_HINT_EXPAND will tell the
972 * window that the box can grow past it's minimum size, which allows resizing
976 * @until evas_object_show
978 * Two more boxes, set to horizontal, hold the buttons to change the autorepeat
979 * configuration used by the buttons. We create each to take over all the
980 * available space horizontally, but we don't want them to grow vertically,
981 * so we keep that axis of the weight with 0.0. Then it gets packed in the
984 * @until evas_object_show
986 * The buttons in each of those boxes have nothing special, they are just packed
987 * in with their default values and the box will use their minimum size, as set
988 * by Elementary itself based on the label, icon, finger size and theme.
990 * But the buttons used to move the central one have a special disposition.
991 * The top one first, is placed right into the main box like our other smaller
992 * boxes. Set to expand horizontally and not vertically, and in this case we
993 * also tell it to fill that space, so it gets resized to take the entire
994 * width of the window.
996 * @skip elm_button_add
997 * @until evas_object_show
999 * The bottom one will be the same, but for the other two we need to use a
1000 * second box set to take as much space as we have, so we can place our side
1001 * buttons in place and have the big empty space where the central button will
1004 * @until evas_object_show
1006 * Then the buttons will have their hints inverted to the other top and bottom
1007 * ones, to expand and fill vertically and keep their minimum size horizontally.
1008 * @skip elm_button_add
1009 * @until evas_object_show
1011 * The central button takes every thing else. It will ask to be expanded in
1012 * both directions, but without filling its cell. Changing its alignment by
1013 * pressing the buttons will make it move around.
1014 * @skip elm_button_add
1015 * @until evas_object_show
1017 * To end, the rightmost button is packed in the smaller box after the central
1018 * one, and back to the main box we have the bottom button at the end.
1022 * @page box_example_02 Box - Layout transitions
1024 * @dontinclude box_example_02.c
1026 * Setting a customized layout for a box is simple once you have the layout
1027 * function, which is just like the layout function for @c Evas_Box. The new
1028 * and fancier thing we can do with Elementary is animate the transition from
1029 * one layout to the next. We'll see now how to do that through a simple
1030 * example, while also taking a look at some of the API that was left
1031 * untouched in our @ref box_example_01 "previous example".
1033 * @image html screenshots/box_example_02.png
1034 * @image latex screenshots/box_example_02.eps width=\textwidth
1036 * @skipline Elementary.h
1038 * Our application data consists of a list of layout functions, given by
1039 * @c transitions. We'll be animating through them throughout the entire run.
1040 * The box with the stuff to move around and the last layout that was set to
1041 * make things easier in the code.
1043 * @until Transitions_Data
1045 * The box starts with three buttons, clicking on any of them will take it
1046 * out of the box without deleting the object. There are also two more buttons
1047 * outside, one to add an object to the box and the other to clear it.
1048 * This is all to show how you can interact with the items in the box, add
1049 * things and even remove them, while the transitions occur.
1051 * One of the callback we'll be using creates a new button, asks the box for
1052 * the list of its children and if it's not empty, we add the new object after
1053 * the first one, otherwise just place at the end as it will not make any
1059 * The clear button is even simpler. Everything in the box will be deleted,
1060 * leaving it empty and ready to fill it up with more stuff.
1064 * And a little function to remove buttons from the box without deleting them.
1065 * This one is set for the @c clicked callback of the original buttons,
1066 * unpacking them when clicked and placing it somewhere in the screen where
1067 * they will not disturb. Once we do this, the box no longer has any control
1068 * of it, so it will be left untouched until the program ends.
1072 * If we wanted, we could just call @c evas_object_del() on the object to
1073 * destroy it. In this case, no unpack is really necessary, as the box would
1074 * be notified of a child being deleted and adjust its calculations accordingly.
1076 * The core of the program is the following function. It takes whatever
1077 * function is first on our list of layouts and together with the
1078 * @c last_layout, it creates an ::Elm_Box_Transition to use with
1079 * elm_box_layout_transition(). In here, we tell it to start from whatever
1080 * layout we last set, end with the one that was at the top of the list and
1081 * when everything is finished, call us back so we can create another
1082 * transition. Finally, move the new layout to the end of the list so we
1083 * can continue running through them until the program ends.
1087 * The main function doesn't have antyhing special. Creation of box, initial
1088 * buttons and some callback setting. The only part worth mentioning is the
1089 * initialization of our application data.
1091 * @until evas_object_box_layout_stack
1093 * We have a simple static variable, set the box, the first layout we are
1094 * using as last and create the list with the different functions to go
1097 * And in the end, we set the first layout and call the same function we went
1098 * through before to start the run of transitions.
1099 * @until _test_box_transition_change
1101 * For the full code, follow @ref box_example_02.c "here".
1103 * @example box_example_02.c
1107 * @page calendar_example_01 Calendar - Simple creation.
1108 * @dontinclude calendar_example_01.c
1110 * As a first example, let's just display a calendar in our window,
1111 * explaining all steps required to do so.
1113 * First you should declare objects we intend to use:
1114 * @skipline Evas_Object
1116 * Then a window is created, a title is set and its set to be autodeleted.
1117 * More details can be found on windows examples:
1118 * @until elm_win_autodel
1120 * Next a simple background is placed on our windows. More details on
1121 * @ref bg_01_example_page :
1122 * @until evas_object_show(bg)
1124 * Now, the exciting part, let's add the calendar with elm_calendar_add(),
1125 * passing our window object as parent.
1126 * @until evas_object_show(cal);
1128 * To conclude our example, we should show the window and run elm mainloop:
1131 * Our example will look like this:
1133 * @image html screenshots/calendar_example_01.png
1134 * @image latex screenshots/calendar_example_01.eps width=\textwidth
1136 * See the full source code @ref calendar_example_01.c here.
1137 * @example calendar_example_01.c
1141 * @page calendar_example_02 Calendar - Layout strings formatting.
1142 * @dontinclude calendar_example_02.c
1144 * In this simple example, we'll explain how to format the label displaying
1145 * month and year, and also set weekday names.
1147 * To format month and year label, we need to create a callback function
1148 * to create a string given the selected time, declared under a
1149 * <tt> struct tm </tt>.
1151 * <tt> struct tm </tt>, declared on @c time.h, is a structure composed by
1153 * @li tm_sec seconds [0,59]
1154 * @li tm_min minutes [0,59]
1155 * @li tm_hour hour [0,23]
1156 * @li tm_mday day of month [1,31]
1157 * @li tm_mon month of year [0,11]
1158 * @li tm_year years since 1900
1159 * @li tm_wday day of week [0,6] (Sunday = 0)
1160 * @li tm_yday day of year [0,365]
1161 * @li tm_isdst daylight savings flag
1162 * @note glib version has 2 additional fields.
1164 * For our function, only stuff that matters are tm_mon and tm_year.
1165 * But we don't need to access it directly, since there are nice functions
1166 * to format date and time, as @c strftime.
1167 * We will get abbreviated month (%b) and year (%y) (check strftime manpage
1168 * for more) in our example:
1169 * @skipline static char
1172 * We need to alloc the string to be returned, and calendar widget will
1173 * free it when it's not needed, what is done by @c strdup.
1174 * So let's register our callback to calendar object:
1175 * @skipline elm_calendar_format_function_set
1177 * To set weekday names, we should declare them as an array of strings:
1178 * @dontinclude calendar_example_02.c
1179 * @skipline weekdays
1182 * And finally set them to calendar:
1183 * skipline weekdays_names_set
1185 * Our example will look like this:
1187 * @image html screenshots/calendar_example_02.png
1188 * @image latex screenshots/calendar_example_02.eps width=\textwidth
1190 * See the full source code @ref calendar_example_02.c here.
1191 * @example calendar_example_02.c
1195 * @page calendar_example_03 Calendar - Years restrictions.
1196 * @dontinclude calendar_example_03.c
1198 * This example explains how to set max and min year to be displayed
1199 * by a calendar object. This means that user won't be able to
1200 * see or select a date before and after selected years.
1201 * By default, limits are 1902 and maximun value will depends
1202 * on platform architecture (year 2037 for 32 bits); You can
1203 * read more about time functions on @c ctime manpage.
1205 * Straigh to the point, to set it is enough to call
1206 * elm_calendar_min_max_year_set(). First value is minimun year, second
1207 * is maximum. If first value is negative, it won't apply limit for min
1208 * year, if the second one is negative, won't apply for max year.
1209 * Setting both to negative value will clear limits (default state):
1210 * @skipline elm_calendar_min_max_year_set
1212 * Our example will look like this:
1214 * @image html screenshots/calendar_example_03.png
1215 * @image latex screenshots/calendar_example_03.eps width=\textwidth
1217 * See the full source code @ref calendar_example_03.c here.
1218 * @example calendar_example_03.c
1222 * @page calendar_example_04 Calendar - Days selection.
1223 * @dontinclude calendar_example_04.c
1225 * It's possible to disable date selection and to select a date
1226 * from your program, and that's what we'll see on this example.
1228 * If isn't required that users could select a day on calendar,
1229 * only interacting going through months, disabling days selection
1230 * could be a good idea to avoid confusion. For that:
1231 * @skipline elm_calendar_day_selection_disabled_set
1233 * Also, regarding days selection, you could be interested to set a
1234 * date to be highlighted on calendar from your code, maybe when
1235 * a specific event happens, or after calendar creation. Let's select
1236 * two days from current day:
1237 * @dontinclude calendar_example_04.c
1238 * @skipline SECS_DAY
1239 * @skipline current_time
1240 * @until elm_calendar_selected_time_set
1242 * Our example will look like this:
1244 * @image html screenshots/calendar_example_04.png
1245 * @image latex screenshots/calendar_example_04.eps width=\textwidth
1247 * See the full source code @ref calendar_example_04.c here.
1248 * @example calendar_example_04.c
1252 * @page calendar_example_05 Calendar - Signal callback and getters.
1253 * @dontinclude calendar_example_05.c
1255 * Most of setters explained on previous examples have associated getters.
1256 * That's the subject of this example. We'll add a callback to display
1257 * all calendar information every time user interacts with the calendar.
1259 * Let's check our callback function:
1260 * @skipline static void
1261 * @until double interval;
1263 * To get selected day, we need to call elm_calendar_selected_time_get(),
1264 * but to assure nothing wrong happened, we must check for function return.
1265 * It'll return @c EINA_FALSE if fail. Otherwise we can use time set to
1266 * our structure @p stime.
1267 * @skipline elm_calendar_selected_time_get
1270 * Next we'll get information from calendar and place on declared vars:
1271 * @skipline interval
1272 * @until elm_calendar_weekdays_names_get
1274 * The only tricky part is that last line gets an array of strings
1275 * (char arrays), one for each weekday.
1277 * Then we can simple print that to stdin:
1281 * <tt> struct tm </tt> is declared on @c time.h. You can check @c ctime
1282 * manpage to read about it.
1284 * To register this callback, that will be called every time user selects
1285 * a day or goes to next or previous month, just add a callback for signal
1287 * @skipline evas_object_smart_callback_add
1289 * Our example will look like this:
1291 * @image html screenshots/calendar_example_05.png
1292 * @image latex screenshots/calendar_example_05.eps width=\textwidth
1294 * See the full source code @ref calendar_example_05.c here.
1295 * @example calendar_example_05.c
1299 * @page calendar_example_06 Calendar - Calendar marks.
1300 * @dontinclude calendar_example_06.c
1302 * On this example marks management will be explained. Functions
1303 * elm_calendar_mark_add(), elm_calendar_mark_del() and
1304 * elm_calendar_marks_clear() will be covered.
1306 * To add a mark, will be required to choose three things:
1308 * @li mark date, or start date if it will be repeated
1309 * @li mark periodicity
1311 * Style defines the kind of mark will be displayed over marked day,
1312 * on caledar. Default theme supports @b holiday and @b checked.
1313 * If more is required, is possible to set a new theme to calendar
1314 * widget using elm_object_style_set(), and use
1315 * the signal that will be used by such marks.
1317 * Date is a <tt> struct tm </tt>, as defined by @c time.h. More can
1318 * be read on @c ctime manpage.
1319 * If a date relative from current is required, this struct can be set
1321 * @skipline current_time
1322 * @until localtime_r
1324 * Or if it's an absolute date, you can just declare the struct like:
1325 * @dontinclude calendar_example_06.c
1327 * @until christmas.tm_mon
1329 * Periodicity is how frequently the mark will be displayed over the
1330 * calendar. Can be a unique mark (that don't repeat), or it can repeat
1331 * daily, weekly, monthly or annually. It's enumerated by
1332 * @c Elm_Calendar_Mark_Repeat_Type.
1334 * So let's add some marks to our calendar. We will add christmas holiday,
1335 * set Sundays as holidays, and check current day and day after that.
1336 * @dontinclude calendar_example_06.c
1338 * @until christmas.tm_mon
1339 * @skipline current_time
1340 * @until ELM_CALENDAR_WEEKLY
1342 * We kept the return of first mark add, because we don't really won't it
1343 * to be checked, so let's remove it:
1344 * @skipline elm_calendar_mark_del
1346 * After all marks are added and removed, is required to draw them:
1347 * @skipline elm_calendar_marks_draw
1349 * Finally, to clear all marks, let's set a callback for our button:
1350 * @skipline elm_button_add
1351 * @until evas_object_show(bt);
1353 * This callback will receive our calendar object, and should clear it:
1354 * @dontinclude calendar_example_06.c
1357 * @note Remember to draw marks after clear the calendar.
1359 * Our example will look like this:
1361 * @image html screenshots/calendar_example_06.png
1362 * @image latex screenshots/calendar_example_06.eps width=\textwidth
1364 * See the full source code @ref calendar_example_06.c here.
1365 * @example calendar_example_06.c
1369 * @page spinner_example Spinner widget example
1371 * This code places seven Elementary spinner widgets on a window, each of
1372 * them exemplifying a part of the widget's API.
1374 * The first of them is the default spinner:
1375 * @dontinclude spinner_example.c
1376 * @skipline elm_spinner_add
1377 * @until evas_object_show
1378 * As you see, the defaults for a spinner are:
1380 * @li min value set to 0
1381 * @li max value set to 100
1382 * @li step value set to 1
1383 * @li label format set to "%0.f"
1385 * If another format is required, see the second spinner. It will put a text
1386 * before and after the value, and also format value to display two decimals:
1387 * @skipline format_set
1389 * The third one will use a customized step, define new minimum and maximum
1390 * values and enable wrap, so when value reaches minimum it jumps to maximum,
1391 * or jumps to minimum after maximum value is reached. Format is set to display
1393 * @skipline elm_spinner_add
1394 * @until evas_object_show
1396 * The fourth uses @c vertical style, so instead of left and right arrows,
1397 * top and bottom are displayed. Also the change interval is reduced, so
1398 * user can change value faster.
1400 * @skipline interval
1402 * In the fifth the user won't be allowed to set value directly, i.e., will
1403 * be obligate change value only using arrows:
1404 * @skipline editable
1406 * The sixth widget will receive a lot of special values, so
1407 * instead of reading numeric values, user will see labels for each one.
1408 * Also direct edition is disabled, otherwise users would see the numeric
1409 * value on edition mode. User will be able to select a month in this widget:
1410 * @skipline elm_spinner_add
1411 * @until evas_object_show
1413 * Finally the last widget will exemplify how to listen to widget's signals,
1414 * <tt> changed </tt> and <tt> delay,changed </tt>. First we need to
1415 * implement callback functions that will simply print spinner's value:
1416 * @dontinclude spinner_example.c
1423 * The first callback function should be called everytime value changes,
1424 * the second one only after user stops to increment or decrement. Try
1425 * to keep arrows pressed and check the difference.
1426 * @skip smart_callback
1427 * @skipline smart_callback
1428 * @skipline smart_callback
1430 * See the full @ref spinner_example.c "example", whose window should
1431 * look like this picture:
1433 * @image html screenshots/spinner_example.png
1434 * @image latex screenshots/spinner_example.eps width=\textwidth
1436 * See the full @ref spinner_example.c "source code" for this example.
1438 * @example spinner_example.c
1442 * @page slider_example Slider widget example
1444 * This code places seven Elementary slider widgets on a window, each of
1445 * them exemplifying a part of the widget's API.
1447 * The first of them is the default slider:
1448 * @dontinclude slider_example.c
1449 * @skipline elm_slider_add
1450 * @until evas_object_show
1452 * As you see, the defaults for a slider are:
1455 * @li no values (on indicator or unit labels)
1457 * Actually it's pretty useless this way. So let's learn how to improve it.
1459 * If some decoration is required, a label can be set, and icon before and
1460 * after the bar as well. On the second slider will add a @c home icon
1461 * and a @c folder icon at @c end.
1462 * @skipline text_set
1465 * If the bar size need to be changed, it can be done with span set function,
1466 * that doesn't accounts other widget's parts size. Also the bar can starts
1467 * with a not default value (0.0), as we done on third slider:
1468 * @skipline value_set
1469 * @skipline span_size_set
1471 * So far, users won't be able to see the slider value. If it's required,
1472 * it can be displayed in two different areas, units label or above
1475 * Let's place a units label on our widget, and also let's set minimum and
1476 * maximum value (uses 0.0 and 1.0 by default):
1477 * @skipline unit_format_set
1478 * @skipline min_max_set
1480 * If above the indicator is the place to display the value, just set it.
1481 * Also, is possible to invert a bar, as you can see:
1482 * @skipline indicator_format_set
1483 * @skipline inverted_set
1485 * But if you require to use a function a bit more customized to show the value,
1486 * is possible to registry a callback function that will be called
1487 * to display unit or indicator label. Only the value will be passed to this
1488 * function, that should return a string.
1489 * In this case, a function to free this string will be required.
1491 * Let's exemplify with indicator label on our sixth slider:
1492 * @dontinclude slider_example.c
1503 * Setting callback functions:
1504 * @skipline indicator_format_function_set
1505 * @skipline _indicator_free
1507 * Also, a slider can be displayed vertically:
1508 * @dontinclude slider_example.c
1509 * @skipline elm_slider_horizontal_set
1511 * Finally the last widget will exemplify how to listen to widget's signals,
1512 * <tt> changed </tt> and <tt> delay,changed </tt>. First we need to
1513 * implement callback functions that will simply print slider's value:
1514 * @dontinclude slider_example.c
1521 * The first callback function should be called everytime value changes,
1522 * the second one only after user stops to increment or decrement. Try
1523 * to keep arrows pressed and check the difference.
1524 * @skip smart_callback
1525 * @skipline smart_callback
1526 * @skipline smart_callback
1528 * See the full @ref slider_example.c "example", whose window should
1529 * look like this picture:
1531 * @image html screenshots/slider_example.png
1532 * @image latex screenshots/slider_example.eps width=\textwidth
1534 * See the full @ref slider_example.c "source code" for this example.
1536 * @example slider_example.c
1540 * @page panes_example Panes widget example
1542 * This code places two Elementary panes widgets on a window, one of them
1543 * displayed vertically and the other horizontally, to exemplify
1544 * a part of the widget's API. Also, all the signals emitted by this
1545 * widget will be covered.
1547 * Let's start adding a panes to our window:
1548 * @dontinclude panes_example.c
1549 * @skipline elm_panes_add
1550 * @until evas_object_show
1552 * Now we will set a content (a simple button) to the left side of our
1554 * @skipline elm_button_add
1555 * @until content_left_set
1557 * The content of the right side will be something a bit more elaborated, we'll
1558 * place another panes, displayed vertically (it's displayed horizontally
1560 * @skipline elm_panes_add
1561 * @until content_right_set
1563 * When populating a panes displayed vertically, remember that left content
1564 * will be placed at top, and right content will place at bottom. Next
1565 * we will add two buttons to exemplify that:
1566 * @skipline elm_button_add
1567 * @until content_right_set
1569 * Panes widgets emits 4 different signals, depending on users interaction
1570 * with the draggable bar. We'll add a callback function for each of them.
1572 * <tt> "clicked" signal </tt>:
1574 * Callback function that just print "Clicked" to stdin:
1575 * @dontinclude panes_example.c
1582 * @skipline static void
1585 * Also, add callback function to the panes:
1586 * @skipline "clicked"
1588 * <tt> "press" signal </tt>:
1590 * Callback function that just print "Pressed" to stdin:
1591 * @dontinclude panes_example.c
1594 * @skipline static void
1597 * Also, add callback function to the panes:
1600 * Now, let's try to make our callback functions a bit more useful:
1602 * <tt> "unpress" signal </tt>:
1604 * Suppose we want to know the size proportion of left content after
1605 * user drags the bar. We need to listen for @c unpress signal, and
1606 * get this size from our panes widget. It's done on the following
1608 * @dontinclude panes_example.c
1613 * @skipline static void
1616 * Adding the callback function to the panes:
1617 * @skipline "unpress"
1619 * <tt> "clicked,double" signal </tt>:
1621 * Now, a interesting feature that could be addded to panes widget.
1622 * Hide a content when user double click the draggable bar. It's done
1623 * using a variable to store size and content left size getter and setter
1624 * on the following function:
1625 * @dontinclude panes_example.c
1626 * @skipline static double
1633 * @skipline static void
1638 * Adding the callback function to the panes:
1639 * @skipline "clicked,double"
1642 * See the full @ref panes_example.c "example", whose window should
1643 * look like this picture:
1645 * @image html screenshots/panes_example.png
1646 * @image latex screenshots/panes_example.eps width=\textwidth
1648 * @example panes_example.c
1652 * @page clock_example Clock widget example
1654 * This code places five Elementary clock widgets on a window, each of
1655 * them exemplifying a part of the widget's API.
1657 * The first of them is the pristine clock:
1658 * @dontinclude clock_example.c
1660 * @until evas_object_show
1661 * As you see, the defaults for a clock are:
1663 * - no seconds shown
1665 * For am/pm time, see the second clock:
1666 * @dontinclude clock_example.c
1668 * @until evas_object_show
1670 * The third one will show the seconds digits, which will flip in
1671 * synchrony with system time. Note, besides, that the time itself is
1672 * @b different from the system's -- it was customly set with
1673 * elm_clock_time_set():
1674 * @dontinclude clock_example.c
1675 * @skip with seconds
1676 * @until evas_object_show
1678 * In both fourth and fifth ones, we turn on the <b>edition
1679 * mode</b>. See how you can change each of the sheets on it, and be
1680 * sure to try holding the mouse pressed over one of the sheet
1681 * arrows. The forth one also starts with a custom time set:
1682 * @dontinclude clock_example.c
1684 * @until evas_object_show
1686 * The fifth, besides editable, has only the time @b units editable,
1687 * for hours, minutes and seconds. This exemplifies
1688 * elm_clock_edit_mode_set():
1689 * @dontinclude clock_example.c
1691 * @until evas_object_show
1693 * See the full @ref clock_example.c "example", whose window should
1694 * look like this picture:
1696 * @image html screenshots/clock_example.png
1697 * @image latex screenshots/clock_example.eps width=\textwidth
1699 * See the full @ref clock_example_c "source code" for this example.
1701 * @example clock_example.c
1705 * @page datetime_example Datetime widget example
1707 * This code places three Elementary Datetime widgets on a window, each of
1708 * them exemplifying the widget's different usage.
1710 * The first of them is <b>"only Date display"</b>:
1711 * @dontinclude datetime_example.c
1713 * @until evas_object_show
1715 * For <b>"only Time display"</b>, see the second datetime:
1716 * @dontinclude datetime_example.c
1718 * @until evas_object_show
1720 * The third one will display datetime shows both <b>Date and Time</b>, corresponding format will be
1721 * taken from system @b locale. Note, besides, that the strings are different
1722 * for different language settings.
1724 * <b>Datetime format</b> can be programmatically set by using
1725 * elm_datetime_format_set():
1726 * @dontinclude datetime_example.c
1727 * @skip DATE and TIME
1728 * @until evas_object_show
1729 * The default format of any locale consists:
1733 * - Hour Field(12hr/24hr format)
1735 * - AM/PM (if exists).
1737 * This is how the example program's window looks like with the datetime widget
1738 * showing only date, only time and both date & time:
1740 * @image html screenshots/datetime_example.png
1741 * @image latex screenshots/datetime_example.eps width=\textwidth
1743 * See the full @ref datetime_example_c "source code" for
1746 * @example datetime_example.c
1750 * @page dayselector_example Dayselector widget example
1752 * This code places two Elementary dayselector widgets on a window, each of
1753 * them exemplifying the different widget styles.
1755 * The first of them is the dayselector in default style:
1756 * @dontinclude dayselector_example.c
1757 * @skip weekdays starting from Sunday
1758 * @until evas_object_show
1760 * As you see, the default style displays the weekdays starting from Sunday.
1762 * One can select/unselect a day just by clicking on the day object.
1763 * The selection toggles once it is being pressed.
1766 * For showing weekdays starting from Monday, see the second dayselector:
1767 * @dontinclude dayselector_example.c
1768 * @skip weekdays starting from Monday
1769 * @until evas_object_show
1772 * The following code exemplifies the selection APIs of Dayselector:
1773 * @dontinclude dayselector_example.c
1774 * @skip Callback function
1775 * @until End of clicked callback
1778 * See the full @ref dayselector_example.c "example", whose window should
1779 * look like this picture:
1781 * @image html screenshots/dayselector_example.png
1782 * @image latex screenshots/dayselector_example.eps width=\textwidth
1784 * See the full @ref dayselector_example_c "source code" for this example.
1786 * @example dayselector_example.c
1790 * @page mapbuf_example Mapbuf Widget Example
1792 * This code places a Elementary mapbuf widget on a window,
1793 * to exemplify part of the widget's API.
1795 * First we'll add an window with a background and a vertical box to
1796 * pack our interface elements:
1797 * @dontinclude mapbuf_example.c
1801 * Next we'll simply add the mapbuf widget to the box:
1802 * @skipline mapbuf_add
1805 * But mapbuf is a container widget, it won't do anything alone. So let's
1806 * create a table full of icons. For that we'll loop to fill each line of each
1807 * column. See @ref tutorial_table_01 "tutorial_table_01"
1808 * if you don't know how to use tables:
1809 * @skipline table_add
1813 * Finally, setting mapbuf content:
1814 * @skipline content_set
1817 * Also, would be good a horizontal box with some controls to change mapbuf
1822 * By default map is disabled. So just setting content isn't enough.
1823 * Alpha and smooth settings will be applied when map is enabled.
1824 * So we'll add a toggle for that. Everytime the map properties
1825 * are changed, map will need to be enabled again. So if you
1826 * want to play a bit with our example, remember to always enable
1827 * map again after concluding your changes.
1828 * @skipline toggle_add
1831 * We have added a callback function to this toggle, so it will enable
1833 * @dontinclude mapbuf_example.c
1839 * Let's add check boxes for alpha blending and smooth rendering:
1840 * @skipline check_add
1844 * By default, mapbuf would enable alpha blending and smooth rendering,
1845 * so we need to check boxes to be consistent with its behavior.
1847 * Callback functions look like the one added to the toggle. This way we
1848 * could enable or disable the both properties:
1849 * @dontinclude mapbuf_example.c
1858 * You'll see that disabling alpha blending will set a black rectangle below
1859 * the icons. That's the reason you only should enable that when you're sure
1860 * the mapbuf content is 100% solid.
1862 * See @ref mapbuf_example.c "mapbuf_example.c", whose window should
1863 * look like this picture:
1865 * @image html screenshots/mapbuf_example.png
1866 * @image latex screenshots/mapbuf_example.eps width=\textwidth
1868 * @example mapbuf_example.c
1872 * @page map_example_01 Map Example - Creation and Zoom
1874 * This code places a Elementary map widget on a window,
1875 * to exemplify part of the widget's API.
1877 * Let's start adding a map to our window:
1878 * @dontinclude map_example_01.c
1879 * @skipline elm_map_add
1880 * @until evas_object_show
1882 * It's enough to display a world map inside our window. But usually you'll
1883 * need to let user interact with the map. We need to place some buttons,
1884 * so the user could control the map. It's done on the followin code.
1885 * If you don't know about boxes, or buttons, check their examples,
1886 * @ref box_example_01 "Box Example 1" and
1887 * @ref button_example_01 "Button Example 1".
1888 * @skipline elm_box_add
1889 * @until _bt_zoom_fill
1891 * We are adding callback functions that will be called when the user clicks
1892 * over these buttons. Let's study such functions, starting from the function
1893 * that will zoom in the map:
1894 * @dontinclude map_example_01.c
1895 * @skipline static void
1898 * First thing done is assure zoom mode is set to manual. It's the default
1899 * mode, but the other buttons will change this, so before setting a new
1900 * zoom value, we need to change the zoom mode.
1902 * Then, we get the current zoom value, increment that, and set the new
1903 * value to the map. If it's bigger than max zoom value allowed, it will
1904 * remain on the maximum allowed, nothing bad will happen. This way we
1905 * don't need to check first if it won't be bigger than max.
1907 * Zoom out function is basically the same thing, but zoom will be decremented
1908 * instead of incremented:
1909 * @skipline static void
1912 * The "X" button, when pressed, will call a function that will
1913 * zoom the map until it fits
1914 * inside the scroll frame with no pixels outside this area:
1915 * @skipline static void
1918 * And the "#" button, will call a function that will zoom until map fills
1919 * scroll, ensuring no pixels are left unfilled:
1920 * @skipline static void
1923 * But we can also set map to show something different from default
1924 * world map, changing the zoom level and region shown. Let's pick a
1925 * wonderful city coordinates, one placed at <tt> 43 20 S, 22 90 W </tt>.
1926 * Since map uses double variables to represent latitude and longitude,
1927 * to represent north or east, we should represent it as positive values,
1928 * and south or west as negative. Also, the value will be represented as
1929 * degree.min. So, for example, our longitude <tt> 43 20 S </tt> will
1931 * by the value <tt> -43.20 </tt>. A zoom set to @c 12 should be enough
1933 * @skipline region_show
1936 * See @ref map_example_01.c "map_example_01.c" for full source,
1937 * whose window should
1938 * look like this picture:
1940 * @image html screenshots/map_example_01.png
1941 * @image latex screenshots/map_example_01.eps width=\textwidth
1943 * @example map_example_01.c
1947 * @page map_example_02 Map Example - Overlay Usage
1949 * This code places a Elementary map widget on a window,
1950 * to exemplify part of the widget's API, related to overlays.
1952 * We'll start this example in the same way
1953 * @ref map_example_01 "Map Example 1". Adding a map with buttons to control
1954 * zoom, so if you didn't read it yet, just do it now.
1955 * @dontinclude map_example_02.c
1956 * @skipline elm_map_add
1959 * Overlays can be placed over the map to represent anything we want. Let's
1960 * say we want to represent some countries and cities with overlays.
1962 * Before we create city or country overlays, let's create class overlays.
1964 * @skipline elm_map_overlay_class_add
1965 * @until elm_map_overlay_icon_set
1966 * These lines create a class overlay which represents cities.
1967 * This class overlay will be used for grouping city overlays.
1968 * Later city overlays in the same class are appended to this class overlay.
1969 * if city overlays are near each other, they will be grouped.
1971 * We can set the icon for the class so that the icon will be displayed
1972 * when city overlays are grouped.
1973 * We can set the zoom required to display the overlays that belongs
1974 * to this class, so if the zoom is less than this value, nothing
1977 * Country class can be created in the same way.
1978 * @skipline elm_map_overlay_class_add
1979 * @until elm_map_overlay_icon_set
1981 * Next we'll create some overlays representing cities and coutries.
1982 * We set the data for the overlay so that can be used later when
1983 * clicked callback is called.
1984 * We'll append them into city class to be grouped.
1985 * We'll append them in a list, to close up them later.
1986 * To create a default overlay, we need to pass the coordinates.
1987 * @skipline elm_map_overlay_add
1988 * @until eina_list_append
1990 * We subscribe a smart callback "overlay,clicked" to create bubble on
1991 * the clicked overlay.
1992 * @dontinclude map_example_02.c
1993 * @skipline "overlay,clicked"
1995 * Finally, on our @c main function, we ask the map to show all the overlays
1996 * with the biggest zoom possible, passing the list of overlays added.
1997 * @skipline elm_map_overlays_show
1999 * We have created a specific structure for this example to store the name
2000 * of the place and a path to a image file to represent it.
2001 * @dontinclude map_example_02.c
2003 * @until Overlay_Data;
2005 * We'll create instances for each place:
2006 * @skipline argentina
2009 * To return an icon, all we need to do is to add a elm_icon and return it:
2010 * @dontinclude map_example_02.c
2011 * @skipline _icon_get(
2014 * For the content, let's return something more elaborate. We will return
2015 * a box with an image representing the place, and the name of this place:
2016 * @skipline _box_get(
2019 * See @ref map_example_02.c "map_example_02.c" for full source,
2020 * whose window should
2021 * look like this picture:
2023 * @image html screenshots/map_example_02.png
2024 * @image latex screenshots/map_example_02.eps width=\textwidth
2026 * @example map_example_02.c
2030 * @page map_example_03 Map Example - Route and Name Usage
2032 * This code places a Elementary map widget on a window,
2033 * to exemplify part of the widget's API, related routes and names.
2035 * In this example, we will suppose we need to set a route for the user
2036 * from his current point (a gps could provide us this information)
2037 * to somewhere else. So we would have coordinates of this
2038 * start point, and would like that he enters the address of his
2039 * destination in a entry, and we'll trace a route on the map.
2041 * We'll start this example in the same way
2042 * @ref map_example_01 "Map Example 1". Adding a map with buttons to control
2043 * zoom, so if you didn't read it yet, just do it now. Actually there is
2044 * a change, that we're aligning buttons to the top, since we wan't a
2045 * vertical control box this time.
2046 * @dontinclude map_example_03.c
2047 * @skipline elm_map_add
2051 * Next we set the box to be vertical and change it's size, weight
2052 * and alignment, so it will occupy the top of the window, from left
2054 * @skipline horizontal_set
2057 * We'll add an entry with a preliminar address, that I know will
2058 * find a coordinate, to examplify names work. But you can try
2059 * lots of addresses. From city or country names to pubs, or whatever
2060 * you want. To try is enough to run the example, type the address and
2061 * press "Route" button. This button will call a function that will
2062 * get the typed address and find the route.
2063 * @skipline entry_add
2067 * The button pass an structure
2068 * instance we make for this example, with all the fields we'll need.
2069 * @dontinclude map_example_03.c
2070 * @skipline _Example_Data
2071 * @until example_data;
2073 * Let's initialize it's fields:
2074 * @skipline example_data.map
2075 * @until example_data.start_lat
2077 * @c map and @c entry are our elementary objects, @c route is set to @c NULL,
2078 * since we don't have one yet, and the coordinates of the start point is set
2079 * (longitude and latitude).
2081 * Also, let's show this start point at the center of the map, and set a zoom
2082 * nice enough to close it:
2083 * @skipline region_show
2086 * These lines were already explained on @ref map_example_02 "Map Example 2".
2088 * Now we'll see the "Route" button callback function:
2089 * @dontinclude map_example_03.c
2092 * @skipline static void
2095 * First we get the address string from our entry. Then we use @c name
2097 * util functions, so we could get coordinates for this address. These
2098 * functions return an #Elm_Map_Name handle for us.
2099 * Function elm_map_name_geo_request() will do this job for us,
2100 * but it's an assyncronous function, since it requires this
2101 * information from the server.
2103 * That's the reason we need to wait for
2104 * <tt> "name,loaded" </tt> signal. We add a callback function for this:
2105 * @dontinclude map_example_03.c
2106 * @skipline static void
2109 * This function will check if a previous route was traced, and if it was,
2110 * it will remove it. Next we'll get destination coordinates from our
2111 * @c name, and use them to add a new route.
2113 * To trace a route we need to know how the user will go through the path.
2114 * Let's suppose he'll be walking, but doesn't like to walk, so we
2115 * need to choose the shortest path intead of the route that would
2116 * made him spend less time. Coordinates of the point from where he will
2117 * start and of the destination point need to be passed as well.
2119 * Finally we'll set a color different from solid red (default), to show
2120 * our route. We set it green.
2122 * See @ref map_example_03.c "map_example_03.c" for full source,
2123 * whose window should
2124 * look like this picture:
2126 * @image html screenshots/map_example_03.png
2127 * @image latex screenshots/map_example_03.eps width=\textwidth
2129 * @example map_example_03.c
2133 * @page diskselector_example_01 Diskselector widget example
2135 * This code places 4 Elementary diskselector widgets on a window, each of
2136 * them exemplifying a part of the widget's API.
2138 * All of them will have weekdays as items, since we won't focus
2139 * on items management on this example. For an example about this subject,
2140 * check @ref diskselector_example_02.
2142 * The first of them is a default diskselector.
2143 * @dontinclude diskselector_example_01.c
2146 * @skipline elm_diskselector_add
2147 * @until evas_object_show
2149 * We are just adding the diskselector, so as you can see, defaults for it are:
2150 * @li Only 3 items visible each time.
2151 * @li Only 3 characters are displayed for labels on side positions.
2152 * @li The first added item remains centeres, i.e., it's the selected item.
2154 * To add items, we are just appending it on a loop, using function
2155 * elm_diskselector_item_append(), that will be better exaplained on
2156 * items management example.
2158 * For a circular diskselector, check the second widget. A circular
2159 * diskselector will display first item after last, and last previous to
2160 * the first one. So, as you can see, @b Sa will appears on left side
2161 * of selected @b Sunday. This property is set with
2162 * elm_diskselector_round_enabled_set().
2164 * Also, we decide to display only 2 character for side labels, instead of 3.
2165 * For this we call elm_diskselector_side_text_max_length_set(). As result,
2166 * we'll see @b Mo displayed instead of @b Mon, when @b Monday is on a
2169 * @skipline elm_diskselector_add
2170 * @until evas_object_show
2172 * But so far, we are only displaying 3 items at once. If more are wanted,
2173 * is enough to call elm_diskselector_display_item_num_set(), as you can
2175 * @skipline elm_diskselector_add
2176 * @until evas_object_show
2178 * @note You can't set less than 3 items to be displayed.
2180 * You can get the number of items in the diskselector by calling
2181 * elm_diskselector_display_item_num_get(), as you can see here:
2182 * @skipline elm_diskselector_add
2184 * Finally, if a bounce effect is required, or you would like to see
2185 * scrollbars, it is possible. But, for default theme, diskselector
2186 * scrollbars will be invisible anyway.
2187 * @skipline elm_diskselector_add
2188 * @until evas_object_show
2190 * See the full @ref diskselector_example_01.c "diskselector_example_01.c"
2191 * code, whose window should look like this picture:
2193 * @image html screenshots/diskselector_example_01.png
2194 * @image latex screenshots/diskselector_example_01.eps width=\textwidth
2196 * @example diskselector_example_01.c
2200 * @page diskselector_example_02 Diskselector - Items management
2202 * This code places a Elementary diskselector widgets on a window,
2203 * along with some buttons trigerring actions on it (though its API).
2204 * It covers most of diskselector item functions.
2206 * On our @c main function, we are adding a default diskselector with
2207 * 3 items. We are only setting their labels (second parameter of function
2208 * elm_diskselector_item_append):
2209 * @dontinclude diskselector_example_02.c
2210 * @skipline elm_diskselector_add
2213 * Next we are adding lots of buttons, each one for a callback function
2214 * that will realize a task covering part of diskselector items API.
2215 * Lets check the first one:
2216 * @skipline elm_button_add
2217 * @until evas_object_show
2219 * We are labeling the button with a task description with
2220 * elm_object_text_set() and setting a callback
2221 * function evas_object_smart_callback_add().
2222 * Each callback function will have the signature:
2223 * <tt> static void _task_cb(void *data, Evas_Object *obj,
2224 * void *event_info)</tt> with the function name varying for each task.
2226 * Now let's cover all of them.
2228 * <b> Appending an item: </b>
2229 * @dontinclude diskselector_example_02.c
2233 * All items are included on diskselector after last one. You @b can't
2236 * The first parameter of elm_diskselector_item_append() is the diskselector
2237 * object, that we are receiving as data on our callback function.
2238 * The second one is a label, the string that will be placed in the center
2239 * of our item. As we don't wan't icons or callback functions, we can
2240 * send NULL as third, fourth and fifth parameters.
2242 * <b> Appending an item with icon: </b>
2243 * @dontinclude diskselector_example_02.c
2244 * @skipline _add_ic_cb
2247 * If an icon is required, you can pass it as third paramenter on our
2248 * elm_diskselector_item_append() function. It will be place on the
2249 * left side of item's label, that will be shifted to right a bit.
2251 * For more details about how to create icons, look for elm_icon examples.
2253 * <b> Appending an item with callback function for selected: </b>
2254 * @dontinclude diskselector_example_02.c
2259 * To set a callback function that will be called every time an item is
2260 * selected, i.e., everytime the diskselector stops with this item in
2261 * center position, just pass the function as fourth paramenter.
2263 * <b> Appending an item with callback function for selected with data: </b>
2264 * @dontinclude diskselector_example_02.c
2265 * @skipline _sel_data_cb
2271 * If the callback function request an extra data, it can be attached to our
2272 * item passing a pointer for data as fifth parameter.
2273 * Our function _sel_data_cb will receive it as <tt> void *data </tt>.
2275 * If you want to free this data, or handle that the way you need when the
2276 * item is deleted, set a callback function for that, with
2277 * elm_object_item_del_cb_set().
2279 * As you can see we check if @c it is not @c NULL after appending it.
2280 * If an error happens, we won't try to set a function for it.
2282 * <b> Deleting an item: </b>
2283 * @dontinclude diskselector_example_02.c
2288 * To delete an item we simple need to call elm_object_item_del() with
2289 * a pointer for such item.
2291 * If you need, you can get selected item with
2292 * elm_diskselector_selected_item_get(), that will return a pointer for it.
2294 * <b> Unselecting an item: </b>
2295 * @dontinclude diskselector_example_02.c
2296 * @skipline _unselect_cb
2299 * To select an item, you should call elm_diskselector_item_selected_set()
2300 * passing @c EINA_TRUE, and to unselect it, @c EINA_FALSE.
2302 * If you unselect the selected item, diskselector will automatically select
2305 * <b> Printing all items: </b>
2306 * @dontinclude diskselector_example_02.c
2307 * @skipline _print_cb
2310 * <b> Clearing the diskselector: </b>
2311 * @dontinclude diskselector_example_02.c
2312 * @skipline _clear_cb
2315 * <b> Selecting the first item: </b>
2316 * @dontinclude diskselector_example_02.c
2317 * @skipline _select_first_cb
2320 * <b> Selecting the last item: </b>
2321 * @dontinclude diskselector_example_02.c
2322 * @skipline _select_last_cb
2325 * <b> Selecting the next item: </b>
2326 * @dontinclude diskselector_example_02.c
2327 * @skipline _select_next_cb
2330 * <b> Selecting the previous item: </b>
2331 * @dontinclude diskselector_example_02.c
2332 * @skipline _select_prev_cb
2335 * See the full @ref diskselector_example_02.c "diskselector_example_02.c"
2336 * code, whose window should look like this picture:
2338 * @image html screenshots/diskselector_example_02.png
2339 * @image latex screenshots/diskselector_example_02.eps width=\textwidth
2341 * @example diskselector_example_02.c
2345 * @page list_example_01 List widget example
2347 * This code places a single Elementary list widgets on a window, just
2348 * to exemplify the more simple and common use case: a list will be created
2349 * and populated with a few items.
2351 * To keep it simple, we won't show how to customize the list, for this check
2352 * @ref list_example_02. Also, we won't focus
2353 * on items management on this example. For an example about this subject,
2354 * check @ref list_example_03.
2356 * To add a list widget.
2357 * @dontinclude list_example_01.c
2358 * @skipline elm_list_add
2360 * We are just adding the list, so as you can see, defaults for it are:
2361 * @li Items are displayed vertically.
2362 * @li Only one item can be selected.
2363 * @li The list doesn't bouce.
2365 * To add items, we are just appending it on a loop, using function
2366 * elm_list_item_append(), that will be better exaplained on
2367 * items management example.
2368 * @dontinclude list_example_01.c
2372 * @skipline elm_list_item_append
2374 * After we just want to show the list. But first we need to start the widget.
2375 * It was done this way to improve widget's performance. So, always remember
2377 * @warning Call elm_list_go before showing the object
2378 * @skipline elm_list_go
2381 * See the full @ref list_example_01.c "list_example_01.c"
2382 * code, whose window should look like this picture:
2384 * @image html screenshots/list_example_01.png
2385 * @image latex screenshots/list_example_01.eps width=\textwidth
2387 * @example list_example_01.c
2391 * @page list_example_02 List widget example
2393 * This code places a single Elementary list widgets on a window,
2394 * exemplifying a part of the widget's API.
2396 * First, we will just create a simple list, as done on @ref list_example_01 :
2397 * @dontinclude list_example_02.c
2400 * @skipline elm_list_add
2401 * @until elm_list_item_append
2403 * Now, let's customize this list a bit. First we will display items
2405 * @skipline horizontal_set
2407 * Then we will choose another list mode. There are four of them, and
2408 * the default #Elm_List_Mode is #ELM_LIST_SCROLL. Let's set compress mode:
2409 * @skipline mode_set
2411 * To enable multiple items selection, we need to enable it, since only one
2412 * selected item is allowed by default:
2413 * @skipline elm_list_multi_select_set
2415 * We are not adding items with callback functions here,
2416 * since we'll explain it better on @ref list_example_03. But if the callback
2417 * need to be called everytime user clicks an item, even if already selected,
2418 * it's required to enable this behavior:
2419 * @skipline elm_list_always_select_mode_set
2421 * Finally, if a bounce effect is required, or you would like to see
2422 * scrollbars, it is possible. But, for default theme, list
2423 * scrollbars will be invisible anyway.
2424 * @skipline bounce_set
2425 * @until SCROLLER_POLICY_ON
2427 * See the full @ref list_example_02.c "list_example_02.c"
2428 * code, whose window should look like this picture:
2430 * @image html screenshots/list_example_02.png
2431 * @image latex screenshots/list_example_02.eps width=\textwidth
2433 * @example list_example_02.c
2437 * @page list_example_03 List - Items management
2439 * This code places a Elementary list widgets on a window,
2440 * along with some buttons trigerring actions on it (though its API).
2441 * It covers most of elm_list_item functions.
2443 * On our @c main function, we are adding a default list with
2444 * 3 items. We are only setting their labels (second parameter of function
2445 * elm_list_item_append):
2446 * @dontinclude list_example_03.c
2447 * @skipline elm_list_add
2450 * Next we are adding lots of buttons, each one for a callback function
2451 * that will realize a task covering part of list items API.
2452 * Lets check the first one:
2453 * @skipline elm_button_add
2454 * @until evas_object_show
2456 * We are labeling the button with a task description with
2457 * elm_object_text_set() and setting a callback
2458 * function evas_object_smart_callback_add().
2459 * Each callback function will have the signature:
2460 * <tt> static void _task_cb(void *data, Evas_Object *obj,
2461 * void *event_info)</tt> with the function name varying for each task.
2463 * Now let's cover all of them.
2465 * <b> Prepending an item: </b>
2466 * @dontinclude list_example_03.c
2467 * @skipline _prepend_cb
2470 * The item will be placed on the begining of the list,
2471 * i.e. it will be the first one.
2473 * The first parameter of elm_list_item_prepend() is the list
2474 * object, that we are receiving as data on our callback function.
2475 * The second one is a label, the string that will be placed in the center
2476 * of our item. As we don't wan't icons or callback functions, we can
2477 * send NULL as third, fourth, fifth and sixth parameters.
2479 * <b> Appending an item: </b>
2480 * @dontinclude list_example_03.c
2484 * Items included with append will be inserted inserted after the last one.
2486 * <b> Appending an item with icon: </b>
2487 * @dontinclude list_example_03.c
2488 * @skipline _add_ic_cb
2491 * If an icon is required, you can pass it as third paramenter on our
2492 * elm_list_item_append() function. It will be place on the
2493 * left side of item's label. If an icon is wanted on the right side,
2494 * it should be passed as fourth parameter.
2496 * For more details about how to create icons, look for elm_icon examples
2497 * @ref tutorial_icon.
2499 * <b> Appending an item with callback function for selected: </b>
2500 * @dontinclude list_example_03.c
2505 * To set a callback function that will be called every time an item is
2506 * selected, i.e., everytime the list stops with this item in
2507 * center position, just pass the function as fifth paramenter.
2509 * <b> Appending an item with callback function for selected with data: </b>
2510 * @dontinclude list_example_03.c
2511 * @skipline _sel_data_cb
2517 * If the callback function request an extra data, it can be attached to our
2518 * item passing a pointer for data as sixth parameter.
2519 * Our function _sel_data_cb will receive it as <tt> void *data </tt>.
2521 * If you want to free this data, or handle that the way you need when the
2522 * item is deleted, set a callback function for that, with
2523 * elm_object_item_del_cb_set().
2525 * As you can see we check if @c it is not @c NULL after appending it.
2526 * If an error happens, we won't try to set a function for it.
2528 * <b> Deleting an item: </b>
2529 * @dontinclude list_example_03.c
2530 * @skipline _del_cb(
2533 * To delete an item we simple need to call elm_object_item_del() with
2534 * a pointer for such item.
2536 * If you need, you can get selected item with
2537 * elm_list_selected_item_get(), that will return a pointer for it.
2539 * <b> Unselecting an item: </b>
2540 * @dontinclude list_example_03.c
2541 * @skipline _unselect_cb
2544 * To select an item, you should call elm_list_item_selected_set()
2545 * passing @c EINA_TRUE, and to unselect it, @c EINA_FALSE.
2547 * <b> Printing all items: </b>
2548 * @dontinclude list_example_03.c
2549 * @skipline _print_cb
2552 * <b> Clearing the list: </b>
2553 * @dontinclude list_example_03.c
2554 * @skipline _clear_cb
2557 * <b> Selecting the next item: </b>
2558 * @dontinclude list_example_03.c
2559 * @skipline _select_next_cb
2562 * <b> Inserting after an item: </b>
2563 * @dontinclude list_example_03.c
2564 * @skipline _insert_after_cb
2567 * <b> Selecting the previous item: </b>
2568 * @dontinclude list_example_03.c
2569 * @skipline _select_prev_cb
2572 * <b> Inserting before an item: </b>
2573 * @dontinclude list_example_03.c
2574 * @skipline _insert_before_cb
2577 * If a separator is required, just set an item as such:
2578 * @dontinclude list_example_03.c
2579 * @skipline _set_separator_cb
2582 * Also an item can be disabled, and the user won't be allowed to (un)select it:
2583 * @dontinclude list_example_03.c
2584 * @skipline _disable_cb
2587 * See the full @ref list_example_03.c "list_example_03.c"
2588 * code, whose window should look like this picture:
2590 * @image html screenshots/list_example_03.png
2591 * @image latex screenshots/list_example_03.eps width=\textwidth
2593 * @example list_example_03.c
2597 * @page toolbar_example_01 Toolbar Example - Simple Items
2599 * This code places a Elementary toolbar widget on a window,
2600 * to exemplify part of the widget's API.
2602 * Let's start adding a button to our window, that will have its text
2603 * modified depending on which item is selected. It's used just to exemplify
2604 * how to change a window content from the toolbar.
2605 * @dontinclude toolbar_example_01.c
2606 * @skipline elm_button_add
2607 * @until evas_object_show
2609 * Also, we'll need a toolbar widget, obviously:
2610 * @skipline elm_toolbar_add
2611 * @until evas_object_show
2613 * When appending an item is possible to set an icon, label, and a callback
2614 * function that will receive passed data.
2615 * @skipline _item_append
2618 * It's possible to disable items, so the user can't select then. We will
2619 * disable the third item:
2620 * @skipline _item_append
2623 * Our callbacks will just set button's label:
2624 * @dontinclude toolbar_example_01.c
2632 * By default, toolbars would display items homogeneously, so item with
2633 * long labels, like the third, will make all of them occupy a lot of space.
2634 * To avoid that, we can disable it:
2635 * @dontinclude toolbar_example_01.c
2636 * @skipline homogeneous
2638 * Another default behavior, is to add an menu item if we have more items
2639 * that would fit on toolbar size. To simply enable scroll, without menus,
2640 * it's required to change toolbar's shrink mode:
2641 * @dontinclude toolbar_example_01.c
2644 * See @ref toolbar_example_01.c "toolbar_example_01.c", whose window should
2645 * look like this picture:
2647 * @image html screenshots/toolbar_example_01.png
2648 * @image latex screenshots/toolbar_example_01.eps width=\textwidth
2650 * @example toolbar_example_01.c
2654 * @page toolbar_example_02 Toolbar Example - Items with States
2656 * This code places a Elementary toolbar widget on a window,
2657 * to exemplify part of the widget's API.
2659 * Toolbar widgets has support to items with states. Each state
2660 * can have it's own label, icon, and callback function.
2662 * Let's start populating a toolbar with some regular items.
2663 * If you don't know how to do that, see
2664 * @ref toolbar_example_01 "Toolbar Example 1".
2665 * @dontinclude toolbar_example_02.c
2666 * @skipline elm_toolbar_add
2669 * The only difference here is that we set shrink mode to #ELM_TOOLBAR_SHRINK_HIDE,
2670 * that won't display items that doesn't fit to the window.
2672 * Now, let's add an item with states. First, add the item just as any other.
2673 * @skipline elm_toolbar_item_append
2674 * @until _item_pressed
2676 * After that states can be added to this item:
2677 * @skipline state_add
2679 * @until _item_pressed
2681 * The both states and the item are using the same callback function,
2682 * that will cycle between states and unselect the item. Unseleting
2683 * is required because it won't call the callback if an user clicks
2684 * over an item already selected:
2685 * @dontinclude toolbar_example_02.c
2691 * On our example, some items are hidden
2692 * because we set the window to be small. But if an item should be displayed
2693 * anyway, is needed to set its priority to be higher than others.
2694 * Any positive value will be enough in our case. Let's force the item
2695 * with multiple states to be displayed.
2696 * @skipline priority
2698 * See @ref toolbar_example_02.c "toolbar_example_02.c", whose window should
2699 * look like this picture:
2701 * @image html screenshots/toolbar_example_02.png
2702 * @image latex screenshots/toolbar_example_02.eps width=\textwidth
2704 * @example toolbar_example_02.c
2708 * @page toolbar_example_03 Toolbar Example - Items with Menus
2710 * Toolbar widgets have support to items with menus. This kind
2711 * of item will display a menu when selected by the user.
2713 * Let's start populating a toolbar with some regular items, the same
2714 * way we started @ref toolbar_example_02 "Toolbar Example 2".
2715 * @dontinclude toolbar_example_03.c
2716 * @skipline elm_toolbar_add
2719 * The only difference is that we'll keep the default shrink mode, that
2720 * adds an item with a menu of hidden items.
2722 * So, a important thing to do is to set a parent for toolbar menus, or they
2723 * will use the toolbar as parent, and its size will be restricted to that.
2724 * @skipline parent_set
2726 * Not only items' menus will respect this parent, but also the own toolbar
2727 * menu, used to show hidden items.
2729 * Next, let's add an item set to display a menu:
2730 * @skipline elm_toolbar_item_append
2733 * Now, to add two options to this item, we can get the menu object and use
2734 * it as a regular elm_menu. See @ref tutorial_menu "Menu example" for more
2735 * about menu widget.
2736 * @skipline _menu_get
2739 * See @ref toolbar_example_03.c "toolbar_example_03.c", whose window should
2740 * look like this picture:
2742 * @image html screenshots/toolbar_example_03.png
2743 * @image latex screenshots/toolbar_example_03.eps width=\textwidth
2745 * @example toolbar_example_03.c
2749 * @page segment_control_example Segment Control Example
2751 * This code places a Elementary segment control widgets on a window,
2752 * to exemplify part of the widget's API.
2754 * Let's start adding a segment control to our window:
2755 * @dontinclude segment_control_example.c
2756 * @skipline elm_segment_control_add
2757 * @until evas_object_show
2759 * Now will add an item only with label:
2760 * @skipline item_add
2762 * Really simple. To add an item with only an icon, the icon needs to be created
2763 * first, them added with this same function:
2764 * @skipline icon_add
2767 * If an item with label and icon is required, it can be done as well. In this
2768 * case, instead of a label (or icon) centered, the item will display an icon
2769 * at left and the label at right:
2770 * @skipline icon_add
2773 * But, if you need to add some items that can have or not a label, but
2774 * want that all of them looks the same way, with icon at left, just add
2775 * an empty string label. It's done on our example to ilustrate that:
2776 * @skipline icon_add
2779 * So far, all the item were added to the last position of the widget,
2780 * but if something different is required, it can be done using another
2781 * insertion function. Let's suppose we want to put an item just before
2786 * There are two ways to delete items. Using the item handle, like:
2787 * @skipline insert_at
2790 * Or using item's index:
2791 * @skipline insert_at
2794 * To set properties of an item already added to the widget, you just need
2795 * to get the item and set icon or label, as the following code shows:
2796 * @skipline item_get
2799 * Finally, it's possible to select an item from the code, and also get
2800 * the selected item. We will select the item at the center of the widget
2801 * and print its position.
2802 * @skipline count_get
2805 * See the full @ref segment_control_example.c "example", whose window should
2806 * look like this picture:
2808 * @image html screenshots/segment_control_example.png
2809 * @image latex screenshots/segment_control_example.eps width=\textwidth
2811 * @example segment_control_example.c
2815 * @page flipselector_example Flip selector widget example
2817 * This code places an Elementary flip selector widget on a window,
2818 * along with two buttons trigerring actions on it (though its API).
2820 * The selector is being populated with the following items:
2821 * @dontinclude flipselector_example.c
2825 * Next, we create it, populating it with those items and registering
2826 * two (smart) callbacks on it:
2827 * @dontinclude flipselector_example.c
2828 * @skip fp = elm_flipselector_add
2829 * @until object_show
2831 * Those two callbacks will take place whenever one of those smart
2832 * events occur, and they will just print something to @c stdout:
2833 * @dontinclude flipselector_example.c
2834 * @skip underflow callback
2835 * @until static void
2836 * Flip the sheets on the widget while looking at the items list, in
2837 * the source code, and you'll get the idea of those events.
2839 * The two buttons below the flip selector will take the actions
2840 * described in their labels:
2841 * @dontinclude flipselector_example.c
2842 * @skip bt = elm_button_add
2843 * @until callback_add(win
2845 * @dontinclude flipselector_example.c
2846 * @skip unselect the item
2849 * Click on them to exercise those flip selector API calls. To
2850 * interact with the other parts of this API, there's a command line
2851 * interface, whose help string can be asked for with the 'h' key:
2852 * @dontinclude flipselector_example.c
2856 * The 'n' and 'p' keys will exemplify elm_flipselector_flip_next()
2857 * and elm_flipselector_flip_prev(), respectively. 'f' and 'l' account
2858 * for elm_flipselector_first_item_get() and
2859 * elm_flipselector_last_item_get(), respectively. Finally, 's' will
2860 * issue elm_flipselector_selected_item_get() on our example flip
2863 * See the full @ref flipselector_example.c "example", whose window should
2864 * look like this picture:
2866 * @image html screenshots/flipselector_example.png
2867 * @image latex screenshots/flipselector_example.eps width=\textwidth
2869 * See the full @ref flipselector_example_c "source code" for this example.
2871 * @example flipselector_example.c
2875 * @page fileselector_example File selector widget example
2877 * This code places two Elementary file selector widgets on a window.
2878 * The one on the left is layouting file system items in a @b list,
2879 * while the the other is layouting them in a @b grid.
2881 * The one having the majority of hooks of interest is on the left,
2882 * which we create as follows:
2883 * @dontinclude fileselector_example.c
2884 * @skip first file selector
2885 * @until object_show
2887 * Note that we enable custom edition of file/directory selection, via
2888 * the text entry it has on its bottom, via
2889 * elm_fileselector_is_save_set(). It starts with the list view, which
2890 * is the default, and we make it not expandable in place
2891 * (elm_fileselector_expandable_set()), so that it replaces its view's
2892 * contents with the current directory's entries each time one
2893 * navigates to a different folder. For both of file selectors we are
2894 * starting to list the contents found in the @c "/tmp" directory
2895 * (elm_fileselector_path_set()).
2897 * Note the code setting it to "grid mode" and observe the differences
2898 * in the file selector's views, in the example. We also hide the
2899 * second file selector's Ok/Cancel buttons -- since it's there just
2900 * to show the grid view (and navigation) -- via
2901 * elm_fileselector_buttons_ok_cancel_set().
2903 * The @c "done" event, which triggers the callback below
2904 * @dontinclude fileselector_example.c
2907 * will be called at the time one clicks the "Ok"/"Cancel" buttons of
2908 * the file selector (on the left). Note that it will print the path
2909 * to the current selection, if any.
2911 * The @c "selected" event, which triggers the callback below
2912 * @dontinclude fileselector_example.c
2913 * @skip bt = 'selected' cb
2915 * takes place when one selects a file (if the file selector is @b not
2916 * under folders-only mode) or when one selects a folder (when in
2917 * folders-only mode). Experiment it by selecting different file
2920 * What comes next is the code creating the three check boxes and two
2921 * buttons below the file selector in the right. They will exercise a
2922 * bunch of functions on the file selector's API, for the instance on
2923 * the left. Experiment with them, specially the buttons, to get the
2924 * difference between elm_fileselector_path_get() and
2925 * elm_fileselector_selected_get().
2927 * Finally, there's the code adding the second file selector, on the
2929 * @dontinclude fileselector_example.c
2930 * @skip second file selector
2931 * @until object_show
2933 * Pay attention to the code setting it to "grid mode" and observe the
2934 * differences in the file selector's views, in the example. We also
2935 * hide the second file selector's Ok/Cancel buttons -- since it's
2936 * there just to show the grid view (and navigation) -- via
2937 * elm_fileselector_buttons_ok_cancel_set().
2939 * See the full @ref fileselector_example.c "example", whose window
2940 * should look like this picture:
2942 * @image html screenshots/fileselector_example.png
2943 * @image latex screenshots/fileselector_example.eps width=\textwidth
2945 * See the full @ref fileselector_example_c "source code" for this example.
2947 * @example fileselector_example.c
2951 * @page fileselector_button_example File selector button widget example
2953 * This code places an Elementary file selector button widget on a
2954 * window, along with some other checkboxes and a text entry. Those
2955 * are there just as knobs on the file selector button's state and to
2956 * display information from it.
2958 * Here's how we instantiate it:
2959 * @dontinclude fileselector_button_example.c
2960 * @skip ic = elm_icon_add
2961 * @until evas_object_show
2963 * Note that we set on it both icon and label decorations. It's set to
2964 * list the contents of the @c "/tmp" directory, too, with
2965 * elm_fileselector_button_path_set(). What follows are checkboxes to
2966 * exercise some of its API funtions:
2967 * @dontinclude fileselector_button_example.c
2968 * @skip ck = elm_check_add
2969 * @until evas_object_show(en)
2971 * The checkboxes will toggle whether the file selector button's
2972 * internal file selector:
2973 * - must have an editable text entry for file names (thus, be in
2974 * "save dialog mode")
2975 * - is to be raised as an "inner window" (note it's the default
2976 * behavior) or as a dedicated window
2977 * - is to populate its view with folders only
2978 * - is to expand its folders, in its view, <b>in place</b>, and not
2979 * repainting it entirely just with the contents of a sole
2982 * The entry labeled @c "Last selection" will exercise the @c
2983 * "file,chosen" smart event coming from the file selector button:
2984 * @dontinclude fileselector_button_example.c
2986 * @until toggle inwin
2988 * Whenever you dismiss or acknowledges the file selector, after it's
2989 * raised, the @c event_info string will contain the last selection on
2990 * it (if any was made).
2992 * This is how the example, just after called, should look like:
2994 * @image html screenshots/fileselector_button_example_00.png
2995 * @image latex screenshots/fileselector_button_example_00.eps width=\textwidth
2997 * Click on the file selector button to raise its internal file
2998 * selector, which will be contained on an <b>"inner window"</b>:
3000 * @image html screenshots/fileselector_button_example_01.png
3001 * @image latex screenshots/fileselector_button_example_01.eps width=\textwidth
3003 * Toggle the "inwin mode" switch off and, if you click on the file
3004 * selector button again, you'll get @b two windows, the original one
3005 * (note the last selection there!)
3007 * @image html screenshots/fileselector_button_example_02.png
3008 * @image latex screenshots/fileselector_button_example_02.eps width=\textwidth
3010 * and the file selector's new one
3012 * @image html screenshots/fileselector_button_example_03.png
3013 * @image latex screenshots/fileselector_button_example_03.eps width=\textwidth
3015 * Play with the checkboxes to get the behavior changes on the file
3016 * selector button. The respective API calls on the widget coming from
3017 * those knobs where shown in the code already.
3019 * See the full @ref fileselector_button_example_c "source code" for
3022 * @example fileselector_button_example.c
3026 * @page fileselector_entry_example File selector entry widget example
3028 * This code places an Elementary file selector entry widget on a
3029 * window, along with some other checkboxes. Those are there just as
3030 * knobs on the file selector entry's state.
3032 * Here's how we instantiate it:
3033 * @dontinclude fileselector_entry_example.c
3034 * @skip ic = elm_icon_add
3035 * @until evas_object_show
3037 * Note that we set on it's button both icon and label
3038 * decorations. It's set to exhibit the path of (and list the contents
3039 * of, when internal file selector is launched) the @c "/tmp"
3040 * directory, also, with elm_fileselector_entry_path_set(). What
3041 * follows are checkboxes to exercise some of its API funtions:
3042 * @dontinclude fileselector_entry_example.c
3043 * @skip ck = elm_check_add
3044 * @until callback_add(fs_entry
3046 * The checkboxes will toggle whether the file selector entry's
3047 * internal file selector:
3048 * - must have an editable text entry for file names (thus, be in
3049 * "save dialog mode")
3050 * - is to be raised as an "inner window" (note it's the default
3051 * behavior) or as a dedicated window
3052 * - is to populate its view with folders only
3053 * - is to expand its folders, in its view, <b>in place</b>, and not
3054 * repainting it entirely just with the contents of a sole
3057 * Observe how the entry's text will match the string coming from the
3058 * @c "file,chosen" smart event:
3059 * @dontinclude fileselector_entry_example.c
3062 * Whenever you dismiss or acknowledges the file selector, after it's
3063 * raised, the @c event_info string will contain the last selection on
3064 * it (if any was made).
3066 * Try, also, to type in a valid system path and, then, open the file
3067 * selector's window: it will start the file browsing there, for you.
3069 * This is how the example, just after called, should look like:
3071 * @image html screenshots/fileselector_entry_example_00.png
3072 * @image latex screenshots/fileselector_entry_example_00.eps width=\textwidth
3074 * Click on the file selector entry to raise its internal file
3075 * selector, which will be contained on an <b>"inner window"</b>:
3077 * @image html screenshots/fileselector_entry_example_01.png
3078 * @image latex screenshots/fileselector_entry_example_01.eps width=\textwidth
3080 * Toggle the "inwin mode" switch off and, if you click on the file
3081 * selector entry again, you'll get @b two windows, the original one
3082 * (note the last selection there!)
3084 * @image html screenshots/fileselector_entry_example_02.png
3085 * @image latex screenshots/fileselector_entry_example_02.eps width=\textwidth
3087 * and the file selector's new one
3089 * @image html screenshots/fileselector_entry_example_03.png
3090 * @image latex screenshots/fileselector_entry_example_03.eps width=\textwidth
3092 * Play with the checkboxes to get the behavior changes on the file
3093 * selector entry. The respective API calls on the widget coming from
3094 * those knobs where shown in the code already.
3096 * See the full @ref fileselector_entry_example_c "source code" for
3099 * @example fileselector_entry_example.c
3103 * @page layout_example_01 Layout - Content, Table and Box
3105 * This example shows how one can use the @ref Layout widget to create a
3106 * customized distribution of widgets on the screen, controled by an Edje theme.
3107 * The full source code for this example can be found at @ref
3108 * layout_example_01_c.
3110 * Our custom layout is defined by a file, @ref layout_example_edc, which is an
3111 * Edje theme file. Look for the Edje documentation to understand it. For now,
3112 * it's enough to know that we describe some specific parts on this layout
3114 * @li a title text field;
3115 * @li a box container;
3116 * @li a table container;
3117 * @li and a content container.
3119 * Going straight to the code, the following snippet instantiates the layout
3122 * @dontinclude layout_example_01.c
3123 * @skip elm_layout_add
3124 * @until evas_object_show(layout)
3126 * As any other widget, we set some properties for the size calculation. But
3127 * notice on this piece of code the call to the function elm_layout_file_set().
3128 * Here is where the theme file is loaded, and particularly the specific group
3129 * from this theme file. Also notice that the theme file here is referenced as
3130 * an .edj, which is a .edc theme file compiled to its binary form. Again, look
3131 * for the Edje documentation for more information about theme files.
3133 * Next, we fetch from our theme a data string referenced by the key "title".
3134 * This data was defined in the theme, and can be used as parameters which the
3135 * program get from the specific theme that it is using. In this case, we store
3136 * the title of this window and program in the theme, as a "data" entry, just
3137 * for demonstration purposes:
3141 * This call elm_layout_data_get() is used to fetch the string based on the key,
3142 * and elm_object_part_text_set() will set the part defined in the theme as
3143 * "example/title" to contain this string. This key "example/title" has nothing
3144 * special. It's just an arbitrary convention that we are using in this example.
3145 * Every string in this example referencing a part of this theme will be of the
3146 * form "example/<something>".
3148 * Now let's start using our layout to distribute things on the window space.
3149 * Since the layout was added as a resize object to the elementary window, it
3150 * will always occupy the entire space available for this window.
3152 * The theme already has a title, and it also defines a table element which is
3153 * positioned approximately between 50% and 70% of the height of this window,
3154 * and has 100% of the width. We create some widgets (two icons, a clock and a
3155 * button) and pack them inside the table, in a distribution similar to a HTML
3158 * @until evas_object_show(bt)
3160 * Notice that we just set size hints for every object, and call the function
3161 * elm_layout_table_pack(), which does all the work. It will place the elements
3162 * in the specified row/column, with row and column span if required, and then
3163 * the object's size and position will be controled by the layout widget. It
3164 * will also respect size hints, alignments and weight properties set to these
3165 * widgets. The resulting distribution on the screen depends on the table
3166 * properties (described in the theme), the size hints set on each widget, and
3167 * on the cells of the table that are being used.
3169 * For instance, we add the two icons and the clock on the first, second and
3170 * third cells of the first row, and add the button the second row, making it
3171 * span for 3 columns (thus having the size of the entire table width). This
3172 * will result in a table that has 2 rows and 3 columns.
3174 * Now let's add some widgets to the box area of our layout. This box is around
3175 * 20% and 50% of the vertical size of the layout, and 100% of its width. The
3176 * theme defines that it will use an "horizontal flow" distribution to its
3177 * elements. Unlike the table, a box will distribute elements without knowing
3178 * about rows and columns, and the distribution function selected will take care
3179 * of putting them in row, column, both, or any other available layout. This is
3180 * also described in the Edje documentation.
3182 * This box area is similar to the @ref Box widget of elementary, with the
3183 * difference that its position and properties are controled by the theme of the
3184 * layout. It also contains more than one API to add items to it, since the
3185 * items position now is defined in terms of a list of items, not a matrix.
3186 * There's the first position (can have items added to it with
3187 * elm_layout_box_prepend()), the last position (elm_layout_box_append()), the
3188 * nth position (elm_layout_box_insert_at()) and the position right before an
3189 * element (elm_layout_box_insert_before()). We use insert_at and prepend
3190 * functions to add the first two buttons to this box, and insert_before on the
3191 * callback of each button. The callback code will be shown later, but it
3192 * basically adds a button just before the clicked button using the
3193 * elm_layout_box_insert_before() function. Here's the code for adding the first
3196 * @until evas_object_show(item)
3197 * @until evas_object_show(item)
3199 * Finally, we have an area in this layout theme, in the bottom part of it,
3200 * reserved for adding an specific widget. Differently from the 2 parts
3201 * described until now, this one can only receive one widget with the call
3202 * elm_object_part_content_set() for the layout. If there was already an item on this specific part,
3203 * it will be deleted (one can use elm_object_part_content_unset() in order to remove
3204 * it without deleting). An example of removing it without deleting, but
3205 * manually deleting this widget just after that, can be seen on the callback
3206 * for this button. Actually, the callback defined for this button will clean
3207 * the two other parts (deleting all of their elements) and then remove and
3208 * delete this button.
3210 * @until _swallow_btn_cb
3212 * Also notice that, for this last added button, we don't have to call
3213 * evas_object_show() on it. This is a particularity of the theme for layouts,
3214 * that will have total control over the properties like size, position,
3215 * visibility and clipping of a widget added with elm_object_part_content_set().
3216 * Again, read the Edje documentation to understand this better.
3218 * Now we just put the code for the different callbacks specified for each kind
3219 * of button and make simple comments about them:
3221 * @dontinclude layout_example_01.c
3223 * @until evas_object_del(item)
3226 * The first callback is used for the button in the table, and will just remove
3227 * itself from the table with elm_layout_table_unpack(), which remove items
3228 * without deleting them, and then calling evas_object_del() on itself.
3230 * The second callback is for buttons added to the box. When clicked, these
3231 * buttons will create a new button, and add them to the same box, in the
3232 * position just before the clicked button.
3234 * And the last callback is for the button added to the "content" area. It will
3235 * clear both the table and the box, passing @c EINA_TRUE to their respective @c
3236 * clear parameters, which will imply on the items of these containers being
3239 * A screenshot of this example can be seen on:
3241 * @image html screenshots/layout_example_01.png
3242 * @image latex screenshots/layout_example_01.eps width=\textwidth
3247 * @page layout_example_02 Layout - Predefined Layout
3249 * This example shows how one can use the @ref Layout with a predefined theme
3250 * layout to add a back and next button to a simple window. The full source code
3251 * for this example can be found at @ref layout_example_02_c.
3253 * After setting up the window and background, we add the layout widget to the
3254 * window. But instead of using elm_layout_file_set() to load its theme from a
3255 * custom theme file, we can use elm_layout_theme_set() to load one of the
3256 * predefined layouts that come with elementary. Particularly on this example,
3257 * we load the them of class "layout", group "application" and style
3258 * "content-back-next" (since we want the back and next buttons).
3260 * @dontinclude layout_example_02.c
3261 * @skip elm_layout_add
3262 * @until evas_object_show(layout)
3264 * This default theme contains only a "content" area named
3265 * "elm.swallow.content", where we can add any widget (it can be even a
3266 * container widget, like a box, frame, list, or even another layout). Since we
3267 * just want to show the resulting layout, we add a simple icon to it:
3269 * @until layout_content_set
3271 * This default layout also provides some signals when the next and prev buttons
3272 * are clicked. We can register callbacks to them with the
3273 * elm_object_signal_callback_add() function:
3275 * @until elm,action,next
3277 * In the @ref layout_example_03 you can see how to send signals to the layout with
3278 * elm_object_signal_emit().
3280 * Now our callback just changes the picture being displayed when one of the
3281 * buttons are clicked:
3283 * @dontinclude layout_example_02.c
3285 * @until standard_set
3288 * It's possible to see that it gets the name of the image being shown from the
3289 * array of image names, going forward on this array when "next" is clicked and
3290 * backward when "back" is clicked.
3292 * A screenshot of this example can be seen on:
3294 * @image html screenshots/layout_example_02.png
3295 * @image latex screenshots/layout_example_02.eps width=\textwidth
3299 * @page layout_example_03 Layout - Signals and Size Changed
3301 * This example shows how one can send and receive signals to/from the layout,
3302 * and what to do when the layout theme has its size changed. The full source
3303 * code for this example can be found at @ref layout_example_03_c.
3305 * In this exmaple we will use another group from the same layout theme file
3306 * used in @ref layout_example_01. Its instanciation and loading happens in the
3309 * @dontinclude layout_example_03.c
3310 * @skip elm_layout_add
3311 * @until evas_object_show
3313 * This time we register a callback to be called whenever we receive a signal
3314 * after the end of the animation that happens in this layout:
3316 * @until signal_callback_add
3318 * We also add a button that will send signals to the layout:
3320 * @until callback_add
3322 * The callback for this button will check what type of signal it should send,
3323 * and then emit it. The code for this callback follows:
3325 * @dontinclude layout_example_03.c
3326 * @skip static Eina_Bool
3331 * As we said before, we are receiving a signal whenever the animation started
3332 * by the button click ends. This is the callback for that signal:
3336 * Notice from this callback that the elm_layout_sizing_eval() function must be
3337 * called if we want our widget to update its size after the layout theme having
3338 * changed its minimum size. This happens because the animation specified in the
3339 * theme increases the size of the content area to a value higher than the
3340 * widget size, thus requiring more space. But the elementary layout widget
3341 * has no way to know this, thus needing the elm_layout_sizing_eval() to
3342 * be called on the layout, informing that this size has changed.
3344 * A screenshot of this example can be seen on:
3346 * @image html screenshots/layout_example_03.png
3347 * @image latex screenshots/layout_example_03.eps width=\textwidth
3351 * @page tutorial_hover Hover example
3352 * @dontinclude hover_example_01.c
3354 * On this example we are going to have a button that when clicked will show our
3355 * hover widget, this hover will have content set on it's left, top, right and
3356 * middle positions. In the middle position we are placing a button that when
3357 * clicked will hide the hover. We are also going to use a non-default theme
3358 * for our hover. We won't explain the functioning of button for that see @ref
3361 * We start our example with a couple of callbacks that show and hide the data
3362 * they're given(which we'll see later on is the hover widget):
3367 * In our main function we'll do some initialization and then create 3
3368 * rectangles, one red, one green and one blue to use in our hover. We'll also
3369 * create the 2 buttons that will show and hide the hover:
3372 * With all of that squared away we can now get to the heart of the matter,
3373 * creating our hover widget, which is easy as pie:
3376 * Having created our hover we now need to set the parent and target. Which if
3377 * you recall from the function documentations are going to tell the hover which
3378 * area it should cover and where it should be centered:
3381 * Now we set the theme for our hover. We're using the popout theme which gives
3382 * our contents a white background and causes their appearance to be animated:
3385 * And finally we set the content for our positions:
3388 * So far so good? Great 'cause that's all there is too it, what is left now is
3389 * just connecting our buttons to the callbacks we defined at the beginning of
3390 * the example and run the main loop:
3393 * Our example will initially look like this:
3395 * @image html screenshots/hover_example_01.png
3396 * @image latex screenshots/hover_example_01.eps width=\textwidth
3398 * And after you click the "Show hover" button it will look like this:
3400 * @image html screenshots/hover_example_01_a.png
3401 * @image latex screenshots/hover_example_01_a.eps width=\textwidth
3403 * @example hover_example_01.c
3407 * @page tutorial_flip Flip example
3408 * @dontinclude flip_example_01.c
3410 * This example will show a flip with two rectangles on it(one blue, one
3411 * green). Our example will allow the user to choose the animation the flip
3412 * uses and to interact with it. To allow the user to choose the interaction
3413 * mode we use radio buttons, we will however not explain them, if you would
3414 * like to know more about radio buttons see @ref Radio.
3416 * We start our example with the usual setup and then create the 2 rectangles
3417 * we will use in our flip:
3418 * @until show(rect2)
3420 * The next thing to do is to create our flip and set it's front and back
3424 * The next thing we do is set the interaction mode(which the user can later
3425 * change) to the page animation:
3428 * Setting a interaction mode however is not sufficient, we also need to
3429 * choose which directions we allow interaction from, for this example we
3430 * will use all of them:
3433 * We are also going to set the hitsize to the entire flip(in all directions)
3434 * to make our flip very easy to interact with:
3437 * After that we create our radio buttons and start the main loop:
3440 * When the user clicks a radio button a function that changes the
3441 * interaction mode and animates the flip is called:
3443 * @note The elm_flip_go() call here serves no purpose other than to
3444 * ilustrate that it's possible to animate the flip programmatically.
3446 * Our example will look like this:
3448 * @image html screenshots/flip_example_01.png
3449 * @image latex screenshots/flip_example_01.eps width=\textwidth
3451 * @note Since this is an animated example the screenshot doesn't do it
3452 * justice, it is a good idea to compile it and see the animations.
3454 * @example flip_example_01.c
3458 * @page tutorial_label Label example
3459 * @dontinclude label_example_01.c
3461 * In this example we are going to create 6 labels, set some properties on
3462 * them and see what changes in appearance those properties cause.
3464 * We start with the setup code that by now you should be familiar with:
3467 * For our first label we have a moderately long text(that doesn't fit in the
3468 * label's width) so we will make it a sliding label. Since the text isn't
3469 * too long we don't need the animation to be very long, 3 seconds should
3470 * give us a nice speed:
3473 * For our second label we have the same text, but this time we aren't going
3474 * to have it slide, we're going to ellipsize it. Because we ask our label
3475 * widget to ellipsize the text it will first diminsh the fontsize so that it
3476 * can show as much of the text as possible:
3479 * For the third label we are going to ellipsize the text again, however this
3480 * time to make sure the fontsize isn't diminshed we will set a line wrap.
3481 * The wrap won't actually cause a line break because we set the label to
3485 * For our fourth label we will set line wrapping but won't set ellipsis, so
3486 * that our text will indeed be wrapped instead of ellipsized. For this label
3487 * we choose character wrap:
3490 * Just two more, for our fifth label we do the same as for the fourth
3491 * except we set the wrap to word:
3494 * And last but not least for our sixth label we set the style to "marker" and
3495 * the color to red(the default color is white which would be hard to see on
3496 * our white background):
3499 * Our example will look like this:
3501 * @image html screenshots/label_example_01.png
3502 * @image latex screenshots/label_example_01.eps width=\textwidth
3504 * @example label_example_01.c
3508 * @page tutorial_image Image example
3509 * @dontinclude image_example_01.c
3511 * This example is as simple as possible. An image object will be added to the
3512 * window over a white background, and set to be resizable together with the
3513 * window. All the options set through the example will affect the behavior of
3516 * We start with the code for creating a window and its background, and also
3517 * add the code to write the path to the image that will be loaded:
3522 * Now we create the image object, and set that file to be loaded:
3526 * We can now go setting our options.
3528 * elm_image_no_scale_set() is used just to set this value to true (we
3529 * don't want to scale our image anyway, just resize it).
3531 * elm_image_resizable_set() is used to allow the image to be resized to a size
3532 * smaller than the original one, but not to a size bigger than it.
3534 * elm_elm_image_smooth_set() will disable the smooth scaling, so the scale
3535 * algorithm used to scale the image to the new object size is going to be
3536 * faster, but with a lower quality.
3538 * elm_image_orient_set() is used to flip the image around the (1, 0) (0, 1)
3541 * elm_image_aspect_fixed_set() is used to keep the original aspect
3542 * ratio of the image, even when the window is resized to another aspect ratio.
3544 * elm_image_fill_outside_set() is used to ensure that the image will fill the
3545 * entire area available to it, even if keeping the aspect ratio. The image
3546 * will overflow its width or height (any of them that is necessary) to the
3547 * object area, instead of resizing the image down until it can fit entirely in
3550 * elm_image_editable_set() is used just to cover the API, but won't affect
3551 * this example since we are not using any copy & paste property.
3553 * This is the code for setting these options:
3557 * Now some last touches in our object size hints, window and background, to
3558 * display this image properly:
3562 * This example will look like this:
3564 * @image html screenshots/image_example_01.png
3565 * @image latex screenshots/image_example_01.eps width=\textwidth
3567 * @example image_example_01.c
3571 * @page tutorial_icon Icon example
3572 * @dontinclude icon_example_01.c
3574 * This example is as simple as possible. An icon object will be added to the
3575 * window over a white background, and set to be resizable together with the
3576 * window. All the options set through the example will affect the behavior of
3579 * We start with the code for creating a window and its background:
3584 * Now we create the icon object, and set lookup order of the icon, and choose
3589 * An intersting thing is that after setting this, it's possible to check where
3590 * in the filesystem is the theme used by this icon, and the name of the group
3595 * We can now go setting our options.
3597 * elm_icon_no_scale_set() is used just to set this value to true (we
3598 * don't want to scale our icon anyway, just resize it).
3600 * elm_icon_resizable_set() is used to allow the icon to be resized to a size
3601 * smaller than the original one, but not to a size bigger than it.
3603 * elm_elm_icon_smooth_set() will disable the smooth scaling, so the scale
3604 * algorithm used to scale the icon to the new object size is going to be
3605 * faster, but with a lower quality.
3607 * elm_icon_fill_outside_set() is used to ensure that the icon will fill the
3608 * entire area available to it, even if keeping the aspect ratio. The icon
3609 * will overflow its width or height (any of them that is necessary) to the
3610 * object area, instead of resizing the icon down until it can fit entirely in
3613 * This is the code for setting these options:
3615 * @until fill_outside
3617 * However, if you try this example you may notice that this image is not being
3618 * affected by all of these options. This happens because the used icon will be
3619 * from elementary theme, and thus it has its own set of options like smooth
3620 * scaling and fill_outside options. You can change the "home" icon to use some
3621 * image (from your system) and see that then those options will be respected.
3623 * Now some last touches in our object size hints, window and background, to
3624 * display this icon properly:
3628 * This example will look like this:
3630 * @image html screenshots/icon_example_01.png
3631 * @image latex screenshots/icon_example_01.eps width=\textwidth
3633 * @example icon_example_01.c
3637 * @page tutorial_hoversel Hoversel example
3638 * @dontinclude hoversel_example_01.c
3640 * In this example we will create a hoversel with 3 items, one with a label but
3641 * no icon and two with both a label and an icon. Every item that is clicked
3642 * will be deleted, but everytime the hoversel is activated we will also add an
3643 * item. In addition our first item will print all items when clicked and our
3644 * third item will clear all items in the hoversel.
3646 * We will start with the normal creation of window stuff:
3649 * Next we will create a red rectangle to use as the icon of our hoversel:
3652 * And now we create our hoversel and set some of it's properties. We set @p win
3653 * as its parent, ask it to not be horizontal(be vertical) and give it a label
3657 * Next we will add our three items, setting a callback to be called for the
3661 * We also set a pair of callbacks to be called whenever any item is selected or
3662 * when the hoversel is activated:
3665 * And then ask that our hoversel be shown and run the main loop:
3668 * We now have the callback for our first item which prints all items in the
3672 * Next we have the callback for our third item which removes all items from the
3676 * Next we have the callback that is called whenever an item is clicked and
3677 * deletes that item:
3680 * And the callback that is called when the hoversel is activated and adds an
3681 * item to the hoversel. Note that since we allocate memory for the item we need
3682 * to know when the item dies so we can free that memory:
3685 * And finally the callback that frees the memory we allocated for items created
3686 * in the @p _add_item callback:
3689 * Our example will initially look like this:
3691 * @image html screenshots/hoversel_example_01.png
3692 * @image latex screenshots/hoversel_example_01.eps width=\textwidth
3694 * And when the hoversel is clicked it will look like this:
3696 * @image html screenshots/hoversel_example_01_a.png
3697 * @image latex screenshots/hoversel_example_01_a.eps width=\textwidth
3699 * @example hoversel_example_01.c
3703 * @page conformant_example Conformant Example.
3705 * In this example we'll explain how to create applications to work
3706 * with illume, considering space required for virtual keyboards, indicator
3709 * Illume is a module for Enlightenment that modifies the user interface
3710 * to work cleanly and nicely on a mobile device. It has support for
3711 * virtual keyboard, among other nice features.
3713 * Let's start creating a very simple window with a vertical box
3714 * with multi-line entry between two buttons.
3715 * This entry will expand filling all space on window not used by buttons.
3717 * @dontinclude conformant_example_01.c
3718 * @skipline elm_main
3721 * For information about how to create windows, boxes, buttons or entries,
3722 * look for documentation for these widgets.
3724 * It will looks fine when you don't need a virtual keyboard, as you
3725 * can see on the following image:
3727 * @image html screenshots/conformant_example_01.png
3728 * @image latex screenshots/conformant_example_01.eps width=\textwidth
3730 * But if you call a virtual keyboard, the window will resize, changing
3731 * widgets size and position. All the content will shrink.
3733 * If you don't want such behaviour, you
3734 * will need a conformant to account for space taken up by the indicator,
3735 * virtual keyboard and softkey.
3737 * In this case, using the conformant in a proper way, you will have
3738 * a window like the following:
3740 * @image html screenshots/conformant_example_02.png
3741 * @image latex screenshots/conformant_example_02.eps width=\textwidth
3743 * As you can see, it guess the space that will be required by the keyboard,
3744 * indicator and softkey bars.
3746 * So, let's study each step required to transform our initial example on
3749 * First of all, we need to set the window as an illume conformant window:
3750 * @dontinclude conformant_example_02.c
3751 * @skipline elm_win_conformant_set
3753 * Next, we'll add a conformant widget, and set it to resize with the window,
3754 * instead of the box.
3756 * @until evas_object_show
3758 * Finally, we'll set the box as conformant's content, just like this:
3759 * @skipline elm_object_content_set
3761 * Compare both examples code:
3762 * @ref conformant_example_01.c "conformant_example_01.c"
3763 * @ref conformant_example_02.c "conformant_example_02.c"
3765 * @example conformant_example_01.c
3766 * @example conformant_example_02.c
3770 * @page index_example_01 Index widget example 1
3772 * This code places an Elementary index widget on a window, which also
3773 * has a very long list of arbitrary strings on it. The list is
3774 * sorted alphabetically and the index will be used to index the first
3775 * items of each set of strings beginning with an alphabet letter.
3777 * Below the list are some buttons, which are there just to exercise
3778 * some index widget's API.
3780 * Here's how we instantiate it:
3781 * @dontinclude index_example_01.c
3782 * @skip elm_list_add
3783 * @until evas_object_show(d.index)
3784 * where we're showing also the list being created. Note that we issue
3785 * elm_win_resize_object_add() on the index, so that it's set to have
3786 * the whole window as its container. Then, we have to populate both
3787 * list and index widgets:
3788 * @dontinclude index_example_01.c
3789 * @skip for (i = 0; i < (sizeof(dict) / sizeof(dict[0])); i++)
3793 * The strings populating the list come from a file
3794 * @dontinclude index_example_01.c
3795 * @skip static const char *dict
3798 * We use the @c curr char variable to hold the last initial letter
3799 * seen on that ordered list of strings, so that we're able to have an
3800 * index item pointing to each list item starting a new letter
3801 * "section". Note that our index item data pointers will be the list
3802 * item handles. We are also setting a callback function to index
3803 * items deletion events:
3804 * @dontinclude index_example_01.c
3808 * There, we show you that the @c event_info pointer will contain the
3809 * item in question's data, i.e., a given list item's pointer. Because
3810 * item data is also returned in the @c data argument on
3811 * @c Evas_Smart_Cb functions, those two pointers must have the same
3812 * values. On this deletion callback, we're deleting the referred list
3813 * item too, just to exemplify that anything could be done there.
3815 * Next, we hook to two smart events of the index object:
3816 * @dontinclude index_example_01.c
3817 * @skip smart_callback_add(d.index
3818 * @until _index_selected
3819 * @dontinclude index_example_01.c
3820 * @skip "delay,changed" hook
3824 * Check that, whenever one holds the mouse pressed over a given index
3825 * letter for some time, the list beneath it will roll down to the
3826 * item pointed to by that index item. When one releases the mouse
3827 * button, the second callback takes place. There, we check that the
3828 * reported item data, on @c event_info, is the same reported by
3829 * elm_index_selected_item_get(), which gives the last selection's
3830 * data on the index widget.
3832 * The first of the three buttons that follow will call
3833 * elm_index_autohide_disabled_set(), thus showing the index automatically for
3834 * you, if it's not already visible, what is checked with
3835 * elm_index_autohide_disabled_get(). The second button will exercise @b deletion
3836 * of index item objects, by the following code:
3837 * @dontinclude index_example_01.c
3838 * @skip delete an index item
3841 * It will get the last index item selected's data and find the
3842 * respective index item handle(#Elm_Object_Item) with elm_index_item_find().
3843 * We need the latter to query the indexing letter string from, with
3844 * elm_index_item_letter_get(). Next, comes the delition, itself,
3845 * which will also trigger the @c _index_item_del callback function,
3848 * The third button, finally, will exercise elm_index_item_clear(),
3849 * which will delete @b all of the index's items.
3851 * This is how the example program's window looks like with the index
3853 * @image html screenshots/index_example_00.png
3854 * @image latex screenshots/index_example_00.eps
3856 * When it's shown, it's like the following figure:
3857 * @image html screenshots/index_example_01.png
3858 * @image latex screenshots/index_example_01.eps
3860 * See the full @ref index_example_01_c "source code" for
3863 * @example index_example_01.c
3867 * @page index_example_02 Index widget example 2
3869 * This code places an Elementary index widget on a window, indexing
3870 * grid items. The items are placed so that their labels @b don't
3871 * follow any order, but the index itself is ordered (through
3872 * elm_index_item_sorted_insert()). This is a complement to to @ref
3873 * index_example_01 "the first example on indexes".
3875 * Here's the list of item labels to be used on the grid (in that
3877 * @dontinclude index_example_02.c
3878 * @skip static const char *items
3881 * In the interesting part of the code, here, we first instantiate the
3882 * grid (more on grids on their examples) and, after creating our
3883 * index, for each grid item we also create an index one to reference
3885 * @dontinclude index_example_02.c
3886 * @skip grid = elm_gengrid_add
3888 * @until smart_callback_add
3890 * The order in which they'll appear in the index, though, is @b
3891 * alphabetical, becase of elm_index_item_sorted_insert() usage
3892 * together with the comparing function, where we take the letters of
3893 * each index item to base our ordering on. The parameters on
3894 * @c _index_cmp have to be declared as void pointers because of the
3895 * @c Eina_Compare_Cb prototype requisition, but in this case we know
3896 * they'll be index item(#Elm_Object_Item)'s:
3897 * @dontinclude index_example_02.c
3898 * @skip ordering alphabetically
3901 * The last interesting bit is the callback in the @c "delay,changed"
3902 * smart event, which will bring the given grid item to the grid's
3904 * @dontinclude index_example_02.c
3908 * Note how the grid will move kind of randomly while you move your
3909 * mouse pointer held over the index from top to bottom -- that's
3910 * because of the the random order the items have in the grid itself.
3912 * This is how the example program's window looks like:
3913 * @image html screenshots/index_example_03.png
3914 * @image latex screenshots/index_example_03.eps
3916 * See the full @ref index_example.c "source code" for
3919 * @example index_example_02.c
3923 * @page tutorial_ctxpopup Ctxpopup example
3924 * @dontinclude ctxpopup_example_01.c
3926 * In this example we have a list with two items, when either item is clicked
3927 * a ctxpopup for it will be shown. Our two ctxpopups are quite different, the
3928 * one for the first item is a vertical and it's items contain both labels and
3929 * icons, the one for the second item is horizontal and it's items have icons
3932 * We will begin examining our example code by looking at the callback we'll use
3933 * when items in the ctxpopup are clicked. It's very simple, all it does is
3934 * print the label present in the ctxpopup item:
3937 * Next we examine a function that creates ctxpopup items, it was created to
3938 * avoid repeating the same code whenever we needed to add an item to our
3939 * ctxpopup. Our function creates an icon from the standard set of icons, and
3940 * then creates the item, with the label received as an argument. We also set
3941 * the callback to be called when the item is clicked:
3944 * Finally we have the function that will create the ctxpopup for the first item
3945 * in our list. This one is somewhat more complex though, so let's go through it
3946 * in parts. First we declare our variable and add the ctxpopup:
3947 * @until ctxpopup_add
3949 * Next we create a bunch of items for our ctxpopup, marking two of them as
3950 * disabled just so we can see what that will look like:
3951 * @until disabled_set
3952 * @until disabled_set
3954 * Then we ask evas where the mouse pointer was so that we can have our ctxpopup
3955 * appear in the right place, set a maximum size for the ctxpopup, move it and
3959 * And last we mark the list item as not selected:
3962 * Our next function is the callback that will create the ctxpopup for the
3963 * second list item, it is very similar to the previous function. A couple of
3964 * interesting things to note is that we ask our ctxpopup to be horizontal, and
3965 * that we pass NULL as the label for every item:
3968 * And with all of that in place we can now get to our main function where we
3969 * create the window, the list, the list items and run the main loop:
3972 * The example will initially look like this:
3974 * @image html screenshots/ctxpopup_example_01.png
3975 * @image latex screenshots/ctxpopup_example_01.eps width=\textwidth
3977 * @note This doesn't show the ctxpopup tough, since it will only appear when
3978 * we click one of the list items.
3980 * Here is what our first ctxpopup will look like:
3982 * @image html screenshots/ctxpopup_example_01_a.png
3983 * @image latex screenshots/ctxpopup_example_01_a.eps width=\textwidth
3985 * And here the second ctxpopup:
3987 * @image html screenshots/ctxpopup_example_01_b.png
3988 * @image latex screenshots/ctxpopup_example_01_b.eps width=\textwidth
3990 * @example ctxpopup_example_01.c
3994 * @page tutorial_separator Separator example
3995 * @dontinclude separator_example_01.c
3997 * In this example we are going to pack two rectangles in a box, and have a
3998 * separator in the middle.
4000 * So we start we the window, background, box and rectangle creation, all pretty
4004 * Once we have our first rectangle in the box we create and add our separator:
4006 * @note Since our box is in horizontal mode it's a good idea to set the
4007 * separator to be horizontal too.
4009 * And now we add our second rectangle and run the main loop:
4012 * This example will look like this:
4014 * @image html screenshots/separator_example_01.png
4015 * @image latex screenshots/separator_example_01.eps width=\textwidth
4017 * @example separator_example_01.c
4021 * @page tutorial_radio Radio example
4022 * @dontinclude radio_example_01.c
4024 * In this example we will create 4 radio buttons, three of them in a group and
4025 * another one not in the group. We will also have the radios in the group
4026 * change the value of a variable directly and have then print it when the value
4027 * changes. The fourth button is in the example just to make clear that radios
4028 * outside the group don't affect the group.
4030 * We'll start with the usual includes:
4033 * And move right to declaring a static variable(the one whose value the radios
4037 * We now need to have a window and all that good stuff to be able to place our
4041 * And now we create a radio button, since this is the first button in our group
4042 * we set the group to be the radio(so we can set the other radios in the same
4043 * group). We also set the state value of this radio to 1 and the value pointer
4044 * to @p val, since val is @p 1 this has the additional effect of setting the
4045 * radio value to @p 1. For this radio we choose the default home icon:
4048 * To check that our radio buttons are working we'll add a callback to the
4049 * "changed" signal of the radio:
4050 * @until smart_callback
4052 * The creation of our second radio button is almost identical, the 2
4053 * differences worth noting are, the value of this radio 2 and that we add this
4054 * radio to the group of the first radio:
4055 * @until smart_callback
4057 * For our third callback we'll omit the icon and set the value to 3, we'll also
4058 * add it to the group of the first radio:
4059 * @until smart_callback
4061 * Our fourth callback has a value of 4, no icon and most relevantly is not a
4062 * member of the same group as the other radios:
4065 * We finally run the main loop:
4068 * And the last detail in our example is the callback that prints @p val so that
4069 * we can see that the radios are indeed changing its value:
4072 * The example will look like this:
4074 * @image html screenshots/radio_example_01.png
4075 * @image latex screenshots/radio_example_01.eps width=\textwidth
4077 * @example radio_example_01.c
4081 * @page tutorial_toggle Toggle example
4082 * @dontinclude toggle_example_01.c
4084 * In this example we'll create 2 toggle widgets. The first will have an icon
4085 * and the state names will be the default "on"/"off", it will also change the
4086 * value of a variable directly. The second won't have a icon, the state names
4087 * will be "Enabled"/"Disabled", it will start "Enabled" and it won't set the
4088 * value of a variable.
4090 * We start with the usual includes and prototype for callback which will be
4091 * implemented and detailed later on:
4094 * We then declare a static global variable(the one whose value will be changed
4095 * by the first toggle):
4098 * We now have to create our window and all that usual stuff:
4101 * The creation of a toggle is no more complicated than that of any other
4105 * For our first toggle we don't set the states labels so they will stay the
4106 * default, however we do set a label for the toggle, an icon and the variable
4107 * whose value it should change:
4110 * We also set the callback that will be called when the toggles value changes:
4111 * @until smart_callback
4113 * For our second toggle it important to note that we set the states labels,
4114 * don't set an icon or variable, but set the initial state to
4115 * EINA_TRUE("Enabled"):
4118 * For the second toggle we will use a different callback:
4119 * @until smart_callback
4121 * We then ask the main loop to start:
4124 * The callback for our first toggle will look the value of @p val and print it:
4127 * For our second callback we need to do a little bit more, since the second
4128 * toggle doesn't change the value of a variable we have to ask it what its
4132 * This example will look like this:
4134 * @image html screenshots/toggle_example_01.png
4135 * @image latex screenshots/toggle_example_01.eps width=\textwidth
4137 * @example toggle_example_01.c
4141 * @page tutorial_panel Panel example
4142 * @dontinclude panel_example_01.c
4144 * In this example will have 3 panels, one for each possible orientation. Two of
4145 * our panels will start out hidden, the third will start out expanded. For each
4146 * of the panels we will use a label as the content, it's however possible to
4147 * have any widget(including containers) as the content of panels.
4149 * We start by doing some setup, code you should be familiar with from other
4153 * And move right to creating our first panel, for this panel we are going to
4154 * choose the orientation as TOP and toggle it(tell it to hide itself):
4157 * For the second panel we choose the RIGHT orientation and explicitly set the
4161 * For our third and last panel we won't set the orientation(which means it will
4162 * use the default: LEFT):
4165 * All that is left is running the main loop:
4168 * This example will look like this;
4170 * @image html screenshots/panel_example_01.png
4171 * @image latex screenshots/panel_example_01.eps width=\textwidth
4172 * @note The buttons with arrow allow the user to hide/show the panels.
4174 * @example panel_example_01.c
4178 * @page gengrid_example Gengrid widget example
4180 * This application is a thorough exercise on the gengrid widget's
4181 * API. We place an Elementary gengrid widget on a window, with
4182 * various knobs below its viewport, each one acting on it somehow.
4184 * The code's relevant part begins at the grid's creation. After
4185 * instantiating it, we set its items sizes, so that we don't end with
4186 * items one finger size wide, only. We're setting them to fat, 150
4187 * pixel wide ones, for this example. We give it some size hints, not
4188 * to be discussed in this context and, than, we register a callback
4189 * on one of its smart events -- the one coming each time an item gets
4190 * doubly clicked. There, we just print the item handle's value.
4191 * @dontinclude gengrid_example.c
4192 * @skip grid = elm_gengrid_add
4193 * @until evas_object_sho
4194 * @dontinclude gengrid_example.c
4195 * @skip item double click callback
4198 * Before we actually start to deal with the items API, let's show
4199 * some things items will be using throughout all the code. The first
4200 * of them is a struct to be used as item data, for all of them:
4201 * @dontinclude gengrid_example.c
4202 * @skip typedef struct
4205 * That path will be used to index an image, to be swallowed into one
4206 * of the item's icon spots. The imagens themselves are distributed
4208 * @dontinclude gengrid_example.c
4209 * @skip static const char *imgs
4212 * We also have an (unique) gengrid item class we'll be using for
4213 * items in the example:
4214 * @dontinclude gengrid_example.c
4215 * @skip static Elm_Gengrid_Item_Class
4216 * @until static Elm_Gengrid_Item_Class
4217 * @dontinclude gengrid_example.c
4218 * @skip item_style =
4221 * As you see, our items will follow the default theme on gengrid
4222 * items. For the label fetching code, we return a string composed of
4223 * the item's image path:
4224 * @dontinclude gengrid_example.c
4225 * @skip label fetching callback
4228 * For item icons, we'll be populating the item default theme's two
4229 * icon spots, @c "elm.swallow.icon" and @c "elm.swallow.end". The
4230 * former will receive one of the images in our list (in the form of
4231 * a @ref bg_02_example_page "background"), while the latter will be
4232 * a check widget. Note that we prevent the check to propagate click
4233 * events, so that the user can toggle its state without messing with
4234 * the respective item's selection in the grid:
4235 * @dontinclude gengrid_example.c
4236 * @skip icon fetching callback
4237 * @until return NULL
4240 * As the default gengrid item's theme does not have parts
4241 * implementing item states, we'll be just returning false for every
4243 * @dontinclude gengrid_example.c
4244 * @skip state fetching callback
4247 * Finally, the deletion callback on gengrid items takes care of
4248 * freeing the item's label string and its data struct:
4249 * @dontinclude gengrid_example.c
4250 * @skip deletion callback
4253 * Let's move to item insertion/deletion knobs, them. They are four
4254 * buttons, above the grid's viewport, namely
4255 * - "Append" (to append an item to the grid),
4256 * - "Prepend" (to prepend an item to the grid),
4257 * - "Insert before" (to insert an item before the selection, on the
4259 * - "Insert after" (to insert an item after the selection, on the
4261 * - "Clear" (to delete all items in the grid),
4262 * - "Bring in 1st" (to make the 1st item visible, by scrolling),
4263 * - "Show last" (to directly show the last item),
4265 * which are displaced and declared in that order. We're not dealing
4266 * with the buttons' creation code (see @ref button_example_01
4267 * "a button example", for more details on it), but with their @c
4268 * "clicked" registered callbacks. For all of them, the grid's handle
4269 * is passed as @c data. The ones creating new items use a common
4270 * code, which just gives a new @c Example_Item struct, with @c path
4271 * filled with a random image in our images list:
4272 * @dontinclude gengrid_example.c
4273 * @skip new item with random path
4276 * Moreover, that ones will set a common function to be issued on the
4277 * selection of the items. There, we print the item handle's value,
4278 * along with the callback function data. The latter will be @c NULL,
4279 * always, because it's what we pass when adding all icons. By using
4280 * elm_object_item_data_get(), we can have the item data back and,
4281 * with that, we're priting the item's path string. Finally, we
4282 * exemplify elm_gengrid_item_pos_get(), printing the item's position
4284 * @dontinclude gengrid_example.c
4285 * @skip item selection callback
4288 * The appending button will exercise elm_gengrid_item_append(), simply:
4289 * @dontinclude gengrid_example.c
4290 * @skip append an item
4293 * The prepending, naturally, is analogous, but exercising
4294 * elm_gengrid_item_prepend(), on its turn. The "Insert before" one
4295 * will expect an item to be selected in the grid, so that it will
4296 * insert a new item just before it:
4297 * @dontinclude gengrid_example.c
4298 * @skip "insert before" callback
4301 * The "Insert after" is analogous, just using
4302 * elm_gengrid_item_insert_after(), instead. The "Clear" button will,
4303 * as expected, just issue elm_gengrid_clear():
4304 * @dontinclude gengrid_example.c
4305 * @skip delete items
4308 * The "Bring in 1st" button is there exercise two gengrid functions
4309 * -- elm_gengrid_first_item_get() and elm_gengrid_item_bring_in().
4310 * With the former, we get a handle to the first item and, with the
4311 * latter, you'll see that the widget animatedly scrolls its view
4312 * until we can see that item:
4313 * @dontinclude gengrid_example.c
4314 * @skip bring in 1st item
4317 * The "Show last", in its turn, will use elm_gengrid_last_item_get()
4318 * and elm_gengrid_item_show(). The latter differs from
4319 * elm_gengrid_item_bring_in() in that it immediately replaces the
4320 * contents of the grid's viewport with the region containing the item
4322 * @dontinclude gengrid_example.c
4323 * @skip show last item
4326 * To change the grid's cell (items) size, we've placed a spinner,
4327 * which has the following @c "changed" smart callback:
4328 * @dontinclude gengrid_example.c
4329 * @skip change items' size
4332 * Experiment with it and see how the items are affected. The "Disable
4333 * item" button will, as the name says, disable the currently selected
4335 * @dontinclude gengrid_example.c
4336 * @skip disable selected item
4338 * Note that we also make use of elm_gengrid_item_selected_set(),
4339 * there, thus making the item unselected before we actually disable
4342 * To toggle between horizontal and vertical layouting modes on the
4343 * grid, use the "Horizontal mode" check, which will call the
4344 * respective API function on the grid:
4345 * @dontinclude gengrid_example.c
4346 * @skip change layouting mode
4349 * If you toggle the check right after that one, "Always select",
4350 * you'll notice all subsequent clicks on the @b same grid item will
4351 * still issue the selection callback on it, what is different from
4352 * when it's not checked. This is the
4353 * elm_gengrid_select_mode_set() behavior:
4354 * @dontinclude gengrid_example.c
4355 * @skip "always select" callback
4358 * One more check follows, "Bouncing", which will turn on/off the
4359 * bouncing animations on the grid, when one scrolls past its
4360 * borders. Experiment with scrolling the grid to get the idea, having
4361 * it turned on and off:
4362 * @dontinclude gengrid_example.c
4363 * @skip "bouncing mode" callback
4366 * The next two checks will affect items selection on the grid. The
4367 * first, "Multi-selection", will make it possible to select more the
4368 * one item on the grid. Because it wouldn't make sense to fetch for
4369 * an unique selected item on this case, we also disable two of the
4370 * buttons, which insert items relatively, if multi-selection is on:
4371 * @dontinclude gengrid_example.c
4372 * @skip multi-selection callback
4375 * Note that we also @b unselect all items in the grid, when returning
4376 * from multi-selection mode, making use of
4377 * elm_gengrid_item_selected_set().
4379 * The second check acting on selection, "No selection", is just what
4380 * its name depicts -- no selection will be allowed anymore, on the
4381 * grid, while it's on. Check it out for yourself, interacting with
4383 * @dontinclude gengrid_example.c
4384 * @skip no selection callback
4387 * We have, finally, one more line of knobs, now sliders, to change
4388 * the grids behavior. The two first will change the horizontal @b
4389 * alignment of the whole actual grid of items within the gengrid's
4391 * @dontinclude gengrid_example.c
4392 * @skip items grid horizontal alignment change
4395 * Naturally, the vertical counterpart just issues
4396 * elm_gengrid_align_set() changing the second alignment component,
4399 * The last slider will change the grid's <b>page size</b>, relative
4400 * to its own one. Try to change those values and, one manner of
4401 * observing the paging behavior, is to scroll softly and release the
4402 * mouse button, with different page sizes, at different grid
4403 * positions, while having lots of items in it -- you'll see it
4404 * snapping to page boundaries differenty, for each configuration:
4405 * @dontinclude gengrid_example.c
4406 * @skip page relative size change
4409 * This is how the example program's window looks like:
4410 * @image html screenshots/gengrid_example.png
4411 * @image latex screenshots/gengrid_example.eps width=\textwidth
4413 * Note that it starts with three items which we included at will:
4414 * @dontinclude gengrid_example.c
4415 * @skip _clicked(grid,
4416 * @until _clicked(grid,
4417 * @until _clicked(grid,
4418 * @until _clicked(grid,
4420 * See the full @ref gengrid_example_c "source code" for
4423 * @example gengrid_example.c
4426 * @page entry_example_01 Entry - Example of simple editing
4428 * As a general overview of @ref Entry we are going to write an, albeit simple,
4429 * functional editor. Although intended to show how elm_entry works, this
4430 * example also makes extensive use of several other widgets. The full code
4431 * can be found in @ref entry_example.c "entry_example.c" and in the following
4432 * lines we'll go through the parts especific to the @ref Entry widget.
4434 * The program itself is a simple editor, with a file already set to it, that
4435 * can be set to autosave or not and allows insertion of emoticons and some
4436 * formatted text. As of this writing, the capabilities of format edition in
4437 * the entry are very limited, so a lot of manual work is required to change
4440 * In any case, the program allows some changes by using the buttons on the
4441 * top of the window and returning focus back to the main entry afterwards.
4443 * @image html screenshots/entry_example.png
4444 * @image latex screenshots/entry_example.eps width=\textwidth
4446 * We'll begin by showing a few structures used throught the program. First,
4447 * the application owns data that holds the main window and the main entry
4448 * where the editting happens. Then, an auxiliar structure we'll use later
4449 * when inserting icons in our text.
4450 * @dontinclude entry_example.c
4452 * @until App_Inwin_Data
4454 * A little convenience function will insert whatever text we need in the
4455 * buffer at the current cursor's position and set focus back to this entry.
4456 * This is done mostly because clicking on any button will make them steal
4457 * focus, which makes writing text more cumbersome.
4461 * One of the buttons on the top will trigger an @ref Inwin to open and show
4462 * us several icons we can insert into the text. We'll jump over most of these
4463 * functions, but when all the options are chosen, we insert the special
4464 * markup text that will show the chosen icon in place.
4465 * @skip edje_file_collection_list_free(emos)
4467 * @until evas_object_del
4470 * As can be seen in that function, the program lets us add icons to our entry
4471 * using all the possible configurations for them. That should help to
4472 * clarify how the different combinations work out by actually seeing them
4475 * The same popup window has a page to set the settings of the chosen icon,
4476 * that is, the size and how the item will be placed within the line.
4478 * The size is done with two entries, limitted to accept numbers and a fixed
4479 * size of characters. Changing the value in this entries will update the icon
4480 * size in our struct as seen in the next two callbacks.
4485 * The rest of the options are handled with radio buttons, since only one type
4486 * of size can be used (@c size, @c absize or @c relsize) and for the vertical
4487 * sizing it needs to choose between @c ascent and @c full. Depending on which
4488 * is chosen, the @c item tag is formed accordingly as seen before.
4489 * @skip static Evas_Object
4490 * @until evas_object_show(rvascent)
4492 * The first of our entries is here. There's something worth mentioning about
4493 * the way we'll create this one. Normally, any entry regardless of whether is
4494 * single line or not, will be set to scrollable, but in this case, since we
4495 * are limitting how many characters can fit in them and we know we don't need
4496 * scrolling, we are not setting this flag. This makes the entry have virtually
4497 * no appearance on screen, other than its text. This is because an entry is
4498 * just that, a box that holds text, and in order to have some frame around it
4499 * or a background color, another widget needs to provide this. When an entry
4500 * is scrollable, the same scroller used internally does this.
4501 * We are using @ref Frame "frames" here to provide some decoration around,
4502 * then creating our entries, set them to single line, add our two filters and
4503 * the callback for when their value change.
4504 * @until _height_changed_cb
4506 * This function ends with the button that will finally call the item
4507 * into our editting string.
4510 * Then we get to the format edition. Here we can add the @c bold and
4511 * @c emphasis tags to parts of our text. There's a lot of manual work to
4512 * know what to do here, since we are not implementing an entire state manager
4513 * and the entry itself doesn't, yet, support all the needed capabilities to
4514 * make this simpler. We begin by getting the format we are using in our
4515 * function from the button pressed.
4516 * @skip aid->naviframe = naviframe;
4517 * @until sizeof(fmt_close)
4519 * Next we need to find out if we need to insert an opening or a closing tag.
4520 * For this, we store the current cursor position and create a selection
4521 * from this point until the beginning of our text, and then get the selected
4522 * text to look for any existing format tags in it. This is currently the only
4523 * way in which we can find out what formats is being used in the entry.
4527 * Once we know what tag to insert, we need a second check in the case it was
4528 * a closing tag. This is because any other closing tag that comes after would
4529 * be left dangling alone, so we need to remove it to keep the text consistent.
4532 * Finally, we clear our fake selections and return the cursor back to the
4533 * position it had at first, since there is where we want to insert our format.
4534 * @until cursor_pos_set
4536 * And finish by calling our convenience function from before, to insert the
4537 * text at the current cursor and give focus back to the entry.
4540 * A checkbox on the top of our program tells us if the text we are editing
4541 * will autosave or not. In it's @c "changed" callback we get the value from
4542 * the checkbox and call the elm_entry_autosave_set() function with it. If
4543 * autosave is set, we also call elm_entry_file_save(). This is so the internal
4544 * timer used to periodically store to disk our changes is started.
4548 * Two more functions to show some cursor playing. Whenever we double click
4549 * anywhere on our entry, we'll find what word is the cursor placed at and
4550 * select it. Likewise, for triple clicking, we select the entire line.
4552 * @until _edit_tplclick_cb
4555 * And finally, the main window of the program contains the entry where we
4556 * do all the edition and some helping widgets to change format, add icons
4557 * or change the autosave flag.
4560 * @until _image_insert_cb
4562 * And the main entry of the program. Set to scroll, by default we disable
4563 * autosave and we'll begin with a file set to it because no file selector
4564 * is being used here. The file is loaded with #ELM_TEXT_FORMAT_MARKUP_UTF8
4565 * so that any format contained in it is interpreted, otherwise the entry
4566 * would load it as just text, escaping any tags found and no format or icons
4567 * would be shown. Then we connect to the double and triple click signals
4568 * and set focus on the entry so we can start typing right away.
4571 * @example entry_example.c
4575 * @page genlist_example_01 Genlist - basic usage
4577 * This example creates a simple genlist with a small number of items and
4578 * a callback that is called whenever an item is selected. All the properties of
4579 * this genlist are the default ones. The full code for this example can be seen
4580 * at @ref genlist_example_01_c.
4582 * For the simplest list that you plan to create, it's necessary to define some
4583 * of the basic functions that are used for creating each list item, and
4584 * associating them with the "item class" for that list. The item class is just
4585 * an struct that contains pointers to the specific list item functions that are
4586 * common to all the items of the list.
4588 * Let's show it by example. Our item class is declared globally and static as
4589 * it will be the only item class that we need (we are just creating one list):
4591 * @dontinclude genlist_example_01.c
4592 * @skip static Elm_Genlist
4593 * @until static Elm_Genlist
4595 * This item class will be used for every item that we create. The only
4596 * functions that we are going to set are @c label_get and @c icon_get. As the
4597 * name suggests, they are used by the genlist to generate the label for the
4598 * respective item, and to generate icon(s) to it too. Both the label and icon
4599 * get functions can be called more than once for each item, with different @c
4600 * part parameters, which represent where in the theme of the item that label or
4601 * icon is going to be set.
4603 * The default theme for the genlist contains only one area for label, and two
4604 * areas for icon ("elm.swallow.icon" and "elm.swallow.end"). Since we just want
4605 * to set the first icon (that will be at the left side of the label), we
4606 * compare the part name given with "elm.swallow.icon". Notice that the
4607 * @c label_get function must return a strduped string, that will be freed later
4608 * automatically by the list. Here's the code for @c label_get and @c icon_get:
4610 * @until static void
4612 * We will also provide a function that will be called whenever an item is
4613 * selected in the genlist. However, this function is not part of the item
4614 * class, it will be passed for each item being added to the genlist explicitly.
4615 * Notice the similarity of the function signature with those used by @c
4616 * evas_object_smart_callback_add:
4620 * Now let's show the code used for really creating the list. Skipping
4621 * boilerplate code used for creating a window and background, the first piece
4622 * of code specific to our genlist example is setting the pointer functions of
4623 * the item class to our above defined functions:
4628 * Notice that we also choose to use the "default" style for our genlist items.
4629 * Another interesting point is that @c state_get and @c del are set to @c NULL,
4630 * since we don't need these functions now. @c del doesn't need to be used
4631 * because we don't add any data that must be freed to our items, and @c
4632 * state_get is also not used since all of our items are the same and don't need
4633 * to have different states to be used for each item. Finally we create our
4636 * @until genlist_add
4638 * Now we append several items to the list, and for all of them we need to give
4639 * the list pointer, a pointer to the item class, the data that will be used
4640 * with that item, a pointer to the parent of this item if it is in a group type
4641 * list (this is not the case so we pass @c NULL), possible flags for this item,
4642 * the callback for when the item is selected, and the data pointer that will be
4643 * given to the selected callback.
4647 * The rest of the code is also common to all the other examples, so it will be
4648 * omitted here (look at the full source code link above if you need it).
4650 * You can try to play with this example, and see the selected callback being
4651 * called whenever an item is clicked. It also already has some features enabled
4652 * by default, like vertical bounce animation when reaching the end of the list,
4653 * automatically visible/invisible scrollbar, etc. Look at the @ref
4654 * genlist_example_02 to see an example of setting these properties to the list.
4656 * The current example will look like this when running:
4658 * @image html screenshots/genlist_example_01.png
4659 * @image latex screenshots/genlist_example_01.eps width=\textwidth
4663 * @page genlist_example_02 Genlist - list setup functions
4665 * This example is very similar to the @ref genlist_example_01, but it fetch
4666 * most of the properties of the genlist and displays them on startup (thus
4667 * getting the default value for them) and then set them to some other values,
4668 * to show how to use that API. The full source code is at @ref
4669 * genlist_example_02_c.
4671 * Considering that the base code for instantiating a genlist was already
4672 * described in the previous example, we are going to focus on the new code.
4674 * Just a small difference for the @c _item_label_get function, we are going to
4675 * store the time that this function was called. This is the "realized" time,
4676 * the time when the visual representation of this item was created. This is the
4677 * code for the @c label_get function:
4679 * @dontinclude genlist_example_02.c
4681 * @until return strdup
4683 * Now let's go to the list creation and setup. First, just after creating the
4684 * list, we get most of the default properties from it, and print them on the
4688 * @until printf("\n")
4690 * We are going to change some of the properties of our list.
4692 * There's no need to call the selected callback at every click, just when the
4693 * selected item changes, thus we call elm_genlist_always_select_mode_set() with
4696 * For this list we don't want bounce animations at all, so we set both the
4697 * horizontal bounce and the vertical bounce to false with
4698 * elm_genlist_bounce_set().
4700 * We also want our list to compress items if they are wider than the list
4701 * width (thus we call elm_genlist_mode_set(obj, ELM_LIST_COMPRESS).
4703 * The items have different width, so they are not homogeneous:
4704 * elm_genlist_homogeneous_set() is set to false.
4706 * Since the compress mode is active, the call to
4707 * elm_genlist_mode_set() doesn't make difference, but the current
4708 * option would make the list to have at least the width of the largest item.
4710 * This list will support multiple selection, so we call
4711 * elm_genlist_multi_select_set() on it.
4713 * The option elm_genlist_height_for_width_mode_set() would allow text block to
4714 * wrap lines if the Edje part is configured with "text.min: 0 1", for example.
4715 * But since we are compressing the elements to the width of the list, this
4716 * option wouldn't take any effect.
4718 * We want the vertical scrollbar to be always displayed, and the orizontal one
4719 * to never be displayed, and set this with elm_genlist_scroller_policy_set().
4721 * The timeout to consider a longpress is set to half of a second with
4722 * elm_genlist_longpress_timeout_set().
4724 * We also change the block count to a smaller value, but that should have not
4725 * impact on performance since the number of visible items is too small. We just
4726 * increase the granularity of the block count (setting it to have at most 4
4729 * @until block_count_set
4731 * Now let's add elements to the list:
4733 * @until item_append
4736 * It's exactly the same as the previous example. The difference is on the
4737 * behavior of the list, if you try to scroll, select items and so.
4739 * In this example we also need two buttons. One of them, when clicked, will
4740 * display several status info about the current selection, the "realized"
4741 * items, the item in the middle of the screen, and the current mode and active
4742 * item of that mode for the genlist.
4744 * The other button will ask the genlist to "realize" again the items already
4745 * "realized", so their respective label_get and icon_get functions will be
4748 * These are the callbacks for both of these buttons:
4750 * @dontinclude genlist_example_02.c
4756 * Try to scroll, select some items and click on the "Show status" button.
4757 * You'll notice that not all items of the list are "realized", thus consuming
4758 * just a small amount of memory. The selected items are listed in the order
4759 * that they were selected, and the current selected item printed using
4760 * elm_genlist_selected_item_get() is the first selected item of the multiple
4763 * Now resize the window so that you can see the "realized time" of some items.
4764 * This is the time of when the label_get function was called. If you click on
4765 * the "Realize" button, all the already realized items will be rebuilt, so the
4766 * time will be updated for all of them.
4768 * The current example will look like this when running:
4770 * @image html screenshots/genlist_example_02.png
4771 * @image latex screenshots/genlist_example_02.eps width=\textwidth
4775 * @page genlist_example_03 Genlist - different width options
4777 * This example doesn't present any other feature that is not already present in
4778 * the other examples, but visually shows the difference between using the
4779 * default list options (first list of the example), setting the horizontal mode
4780 * to #ELM_LIST_LIMIT (second list), enabling compress mode (third list) and
4781 * using height_for_width option (fourth list).
4783 * The full code for this example is listed below:
4785 * @include genlist_example_03.c
4787 * And the screenshot of the running example:
4789 * @image html screenshots/genlist_example_03.png
4790 * @image latex screenshots/genlist_example_03.eps width=\textwidth
4792 * @example genlist_example_03.c
4796 * @page genlist_example_04 Genlist - items manipulation
4798 * This example is also similar ot the @ref genlist_example_01, but it
4799 * demonstrates most of the item manipulation functions. See the full source
4800 * code at @ref genlist_example_04_c.
4802 * In this example, we also will use the concept of creating groups of items in
4803 * the genlist. Each group of items is composed by a parent item (which will be
4804 * the index of the group) and several children of this item. Thus, for the
4805 * children, we declare a normal item class. But we also are going to declare a
4806 * different item class for the group index (which in practice is another type
4807 * of item in the genlist):
4809 * @dontinclude genlist_example_04.c
4810 * @skip _item_sel_cb
4815 * We will add buttons to the window, where each button provides one
4816 * functionality of the genlist item API. Each button will have a callback
4817 * attached, that will really execute this functionality. An example of these
4818 * callbacks is the next one, for the elm_genlist_item_insert_after() function:
4820 * @skip insert_before_cb
4824 * If you want ot see the other button functions, look at the full source code
4827 * Each button will be created with a function that already creates the button,
4828 * add it to an elementary box, and attach the specified callback. This is the
4829 * function that does it:
4831 * @skip genlist_item_update
4835 * In our @c elm_main function, besides the code for setting up the window, box
4836 * and background, we also initialize our two item classes:
4838 * @skip _itc.item_style
4839 * @until _itc_group.func.del
4841 * This example uses a different style for the items, the @a double_label, which
4842 * provides a text field for the item text, and another text field for a subtext.
4844 * For the group index we use the @a group_index style, which provides a
4845 * different appearance, helping to identify the end of a group and beginning of
4848 * Now, after the code for creating the list, setting up the box and other
4849 * stuff, let's add the buttons with their respective callbacks:
4852 * @until bt_top_show
4854 * The main code for adding items to the list is a bit more complex than the one
4855 * from the previous examples. We check if each item is multiple of 7, and if
4856 * so, they are group indexes (thus each group has 6 elements by default, in
4863 * Then we also check for specific items, and add callbacks to them on the
4864 * respective buttons, so we can show, bring in, etc.:
4869 * Once you understand the code from the @ref genlist_example_01, it should be
4870 * easy to understand this one too. Look at the full code, and also try to play
4871 * a bit with the buttons, adding items, bringing them to the viewport, and so.
4873 * The example will look like this when running:
4875 * @image html screenshots/genlist_example_04.png
4876 * @image latex screenshots/genlist_example_04.eps width=\textwidth
4880 * @page genlist_example_05 Genlist - working with subitems
4882 * This is probably the most complex example of elementary @ref Genlist. We
4883 * create a tree of items, using the subitems properties of the items, and keep
4884 * it in memory to be able to expand/hide subitems of an item. The full source
4885 * code can be found at @ref genlist_example_05_c
4887 * The main point is the way that Genlist manages subitems. Clicking on an
4888 * item's button to expand it won't really show its children. It will only
4889 * generate the "expand,request" signal, and the expansion must be done
4892 * In this example we want to be able to add items as subitems of another item.
4893 * If an item has any child, it must be displayed using a parent class,
4894 * otherwise it will use the normal item class.
4896 * It will be possible to delete items too. Once a tree is constructed (with
4897 * subitems of subitems), and the user clicks on the first parent (root of the
4898 * tree), the entire subtree must be hidden. However, just calling
4899 * elm_genlist_item_expanded_set(item, EINA_FALSE) won't hide them. The only
4900 * thing that happens is that the parent item will change its appearance to
4901 * represent that it's contracted. And the signal "contracted" will be emitted
4902 * from the genlist. Thus, we must call elm_genlist_item_subitems_clear() to
4903 * delete all its subitems, but still keep a way to recreate them when expanding
4904 * the parent again. That's why we are going to keep a node struct for each
4905 * item, that will be the data of the item, with the following information:
4907 * @dontinclude genlist_example_05.c
4911 * This @c Node_Data contains the value for the item, a number indicating its
4912 * level under the tree, a list of children (to be able to expand it later) and
4913 * a boolean indicating if it's a favorite item or not.
4915 * We use 3 different item classes in this example:
4917 * One for items that don't have children:
4924 * One for items that have children:
4931 * And one for items that were favorited:
4937 * The favorite item class is there just to demonstrate the
4938 * elm_genlist_item_item_class_update() function in action. It would be much
4939 * simpler to implement the favorite behavior by just changing the icon inside
4940 * the icon_get functions when the @c favorite boolean is activated.
4942 * Now we are going to declare the callbacks for the buttons that add, delete
4945 * First, a button for appending items to the list:
4947 * @until item_append
4950 * If an item is selected, a new item will be appended to the same level of that
4951 * item, but using the selected item's parent as its parent too. If no item is
4952 * selected, the new item will be appended to the root of the tree.
4954 * Then the callback for marking an item as favorite:
4956 * @until elm_genlist_item_update
4959 * This callback is very simple, it just changes the item class of the selected
4960 * item for the "favorite" one, or go back to the "item" or "parent" class
4961 * depending on that item having children or not.
4963 * Now, the most complex operation (adding a child to an item):
4965 * @until elm_genlist_item_update
4968 * This function gets the data of the selected item, create a new data (for the
4969 * item being added), and appends it to the children list of the selected item.
4971 * Then we must check if the selected item (let's call it @c item1 now) to which
4972 * the new item (called @c item2 from now on) was already a parent item too
4973 * (using the parent item class) or just a normal item (using the default item
4974 * class). In the first case, we just have to append the item to the end of the
4975 * @c item1 children list.
4977 * However, if the @c item1 didn't have any child previously, we have to change
4978 * it to a parent item now. It would be easy to just change its item class to
4979 * the parent type, but there's no way to change the item flags and make it be
4980 * of the type #ELM_GENLIST_ITEM_TREE. Thus, we have to delete it and create
4981 * a new item, and add this new item to the same position that the deleted one
4982 * was. That's the reason of the checks inside the bigger @c if.
4984 * After adding the item to the newly converted parent, we set it to not
4985 * expanded (since we don't want to show the added item immediately) and select
4986 * it again, since the original item was deleted and no item is selected at the
4989 * Finally, let's show the callback for deleting items:
4991 * @until elm_genlist_item_update
4994 * Since we have an iternal list representing each element of our tree, once we
4995 * delete an item we have to go deleting each child of that item, in our
4996 * internal list. That's why we have the function @c _clear_list, which
4997 * recursively goes freeing all the item data.
4999 * This is necessary because only when we really want to delete the item is when
5000 * we need to delete the item data. When we are just contracting the item, we
5001 * need to hide the children by deleting them, but keeping the item data.
5003 * Now there are two callbacks that will be called whenever the user clicks on
5004 * the expand/contract icon of the item. They will just request to items to be
5005 * contracted or expanded:
5007 * @until elm_genlist_item_expanded_set(
5008 * @until elm_genlist_item_expanded_set(
5011 * When the elm_genlist_item_expanded_set() function is called with @c
5012 * EINA_TRUE, the @c _expanded_cb will be called. And when this happens, the
5013 * subtree of that item must be recreated again. This is done using the internal
5014 * list stored as item data for each item. The function code follows:
5018 * Each appended item is set to contracted, so we don't have to deal with
5019 * checking if the item was contracted or expanded before its parent being
5020 * contracted. It could be easily implemented, though, by adding a flag expanded
5021 * inside the item data.
5023 * Now, the @c _contracted_cb, which is much simpler:
5027 * We just have to call elm_genlist_item_subitems_clear(), that will take care
5028 * of deleting every item, and keep the item data still stored (since we don't
5029 * have any del function set on any of our item classes).
5031 * Finally, the code inside @c elm_main is very similar to the other examples:
5036 * The example will look like this when running:
5038 * @image html screenshots/genlist_example_05.png
5039 * @image latex screenshots/genlist_example_05.eps width=\textwidth
5043 * @page thumb_example_01 Thumb - generating thumbnails.
5045 * This example shows how to create a simple thumbnail object with Elementary.
5046 * The full source code can be found at @ref thumb_example_01_c
5048 * Everything is very simple. First we need to tell elementary that we need
5049 * Ethumb to generate the thumbnails:
5051 * @dontinclude thumb_example_01.c
5052 * @skipline elm_need_ethumb
5054 * Then, after creating the window and background, we setup our client to
5055 * generate images of 160x160:
5060 * After that, we can start creating thumbnail objects. They are very similar to
5061 * image or icon objects:
5063 * @until thumb_reload
5065 * As you can see, the main different function here is elm_thumb_reload(), which
5066 * will check if the options of the Ethumb client have changed. If so, it will
5067 * re-generate the thumbnail, and show the new one.
5069 * Notice in this example that the thumbnail object is displayed on the size of
5070 * the window (320x320 pixels), but the thumbnail generated and stored has size
5071 * 160x160 pixels. That's why the picture seems upscaled.
5073 * Ideally, you will be generating thumbnails with the size that you will be
5076 * The example will look like this when running:
5078 * @image html screenshots/thumb_example_01.png
5079 * @image latex screenshots/thumb_example_01.eps width=\textwidth
5083 * @page progressbar_example Progress bar widget example
5085 * This application is a thorough example of the progress bar widget,
5086 * consisting of a window with varios progress bars, each with a given
5087 * look/style one can give to those widgets. With two auxiliary
5088 * buttons, one can start or stop a timer which will fill in the bars
5089 * in synchrony, simulating an underlying task being completed.
5091 * We create @b seven progress bars, being three of them horizontal,
5092 * three vertical and a final one under the "wheel" alternate style.
5094 * For the first one, we add a progress bar on total pristine state,
5095 * with no other call than the elm_progressbar_add() one:
5096 * @dontinclude progressbar_example.c
5097 * @skip pb with no label
5099 * See, than, that the defaults of a progress bar are:
5100 * - no primary label shown,
5101 * - unit label set to @c "%.0f %%",
5104 * The second progress bar is given a primary label, <c>"Infinite
5105 * bounce"</c>, and, besides, it's set to @b pulse. See how, after one
5106 * starts the progress timer, with the "Start" button, it animates
5107 * differently than the previous one. It won't account for the
5108 * progress, itself, and just dumbly animate a small bar within its
5110 * @dontinclude progressbar_example.c
5111 * @skip pb with label
5114 * Next, comes a progress bar with an @b icon, a primary label and a
5115 * @b custom unit label set. It's also made to grow its bar in an
5116 * @b inverted manner, so check that out during the timer's progression:
5117 * @dontinclude progressbar_example.c
5120 * Another important thing in this one is the call to
5121 * elm_progressbar_span_size_set() -- this is how we forcefully set a
5122 * minimum horizontal size to our whole window! We're not resizing it
5123 * manually, as you can see in the @ref progressbar_example_c
5126 * The next three progress bars are just variants on the ones already
5127 * shown, but now all being @b vertical. Another time we use one of
5128 * than to give the window a minimum vertical size, with
5129 * elm_progressbar_span_size_set(). To demonstrate this trick once
5130 * more, the fifth one, which is also set to pulse, has a smaller
5131 * hardcoded span size:
5132 * @dontinclude progressbar_example.c
5133 * @skip vertical pb, with pulse
5136 * We end the widget demonstration by showing a progress bar with the
5137 * special @b "wheel" progress bar style. One does @b not need to set
5138 * it to pulse, with elm_progressbar_pulse_set(), explicitly, because
5139 * its theme does not take it in account:
5140 * @dontinclude progressbar_example.c
5144 * The two buttons exercising the bars, the facto, follow:
5145 * @dontinclude progressbar_example.c
5146 * @skip elm_button_add
5147 * @until evas_object_show(bt)
5148 * @until evas_object_show(bt)
5150 * The first of the callbacks will, for the progress bars set to
5151 * pulse, start the pulsing animation at that time. For the others, a
5152 * timer callback will take care of updating the values:
5153 * @dontinclude progressbar_example.c
5154 * @skip static Eina_Bool
5159 * Finally, the callback to stop the progress timer will stop the
5160 * pulsing on the pulsing progress bars and, for the others, to delete
5161 * the timer which was acting on their values:
5162 * @dontinclude progressbar_example.c
5167 * This is how the example program's window looks like:
5168 * @image html screenshots/progressbar_example.png
5169 * @image latex screenshots/progressbar_example.eps width=\textwidth
5171 * See the full @ref progressbar_example_c "source code" for
5174 * @example progressbar_example.c
5178 * @page tutorial_notify Notify example
5179 * @dontinclude notify_example_01.c
5181 * In this example we will have 3 notifys in 3 different positions. The first of
5182 * which will dissapear after 5 seconds or when a click outside it occurs, the
5183 * second and third will not dissapear and differ from each other only in
5186 * We start our example with the usual stuff you've seen in other examples:
5189 * We now create a label to use as the content of our first notify:
5192 * Having the label we move to creating our notify, telling it to block events,
5193 * setting its timeout(to autohide it):
5196 * To have the notify dissapear when a click outside its area occur we have to
5197 * listen to its "block,clicked" signal:
5198 * @until smart_callback
5200 * Our callback will look like this:
5203 * @dontinclude notify_example_01.c
5205 * Next we create another label and another notify. Note, however, that this
5206 * time we don't set a timeout and don't have it block events. What we do is set
5207 * the orient so that this notify will appear in the bottom of its parent:
5208 * @skip smart_callback
5212 * For our third notify the only change is the orient which is now center:
5215 * Now we tell the main loop to run:
5218 * Our example will initially look like this:
5220 * @image html screenshots/notify_example_01.png
5221 * @image latex screenshots/notify_example_01.eps width=\textwidth
5223 * Once the first notify is hidden:
5225 * @image html screenshots/notify_example_01_a.png
5226 * @image latex screenshots/notify_example_01_a.eps width=\textwidth
5228 * @example notify_example_01.c
5232 * @page popup_example_01_c popup_example_01.c
5233 * @include popup_example_01.c
5235 * This example will initially look like this:
5237 * @image html screenshots/popup_example_01.png
5238 * @image latex screenshots/popup_example_01.eps width=\textwidth
5240 * Once the popup is hidden after timeout:
5242 * @image html screenshots/popup_example_01_a.png
5243 * @image latex screenshots/popup_example_01_a.eps width=\textwidth
5245 * @example popup_example_01.c
5248 /** @page popup_example_02_c popup_example_02.c
5249 * @include popup_example_02.c
5251 * This example will look like this:
5253 * @image html screenshots/popup_example_02.png
5254 * @image latex screenshots/popup_example_02.eps width=\textwidth
5256 * @example popup_example_02.c
5260 * @page popup_example_03_c popup_example_03.c
5261 * @include popup_example_03.c
5263 * This example will look like this:
5265 * @image html screenshots/popup_example_03.png
5266 * @image latex screenshots/popup_example_03.eps width=\textwidth
5268 * @example popup_example_03.c
5272 * @page tutorial_frame Frame example
5273 * @dontinclude frame_example_01.c
5275 * In this example we are going to create 4 Frames with different styles and
5276 * add a rectangle of different color in each.
5278 * We start we the usual setup code:
5281 * And then create one rectangle:
5284 * To add it in our first frame, which since it doesn't have it's style
5285 * specifically set uses the default style:
5288 * And then create another rectangle:
5291 * To add it in our second frame, which uses the "pad_small" style, note that
5292 * even tough we are setting a text for this frame it won't be show, only the
5293 * default style shows the Frame's title:
5295 * @note The "pad_small", "pad_medium", "pad_large" and "pad_huge" styles are
5296 * very similar, their only difference is the size of the empty area around
5297 * the content of the frame.
5299 * And then create yet another rectangle:
5302 * To add it in our third frame, which uses the "outdent_top" style, note
5303 * that even tough we are setting a text for this frame it won't be show,
5304 * only the default style shows the Frame's title:
5307 * And then create one last rectangle:
5310 * To add it in our fourth and final frame, which uses the "outdent_bottom"
5311 * style, note that even tough we are setting a text for this frame it won't
5312 * be show, only the default style shows the Frame's title:
5315 * And now we are left with just some more setup code:
5318 * Our example will look like this:
5320 * @image html screenshots/frame_example_01.png
5321 * @image latex screenshots/frame_example_01.eps width=\textwidth
5323 * @example frame_example_01.c
5327 * @page tutorial_anchorblock_example Anchorblock/Anchorview example
5328 * This example will show both Anchorblock and @ref Anchorview,
5329 * since both are very similar and it's easier to show them once and side
5330 * by side, so the difference is more clear.
5332 * We'll show the relevant snippets of the code here, but the full example
5333 * can be found here... sorry, @ref anchorblock_example_01.c "here".
5335 * As for the actual example, it's just a simple window with an anchorblock
5336 * and an anchorview, both containing the same text. After including
5337 * Elementary.h and declaring some functions we'll need, we jump to our
5338 * elm_main (see ELM_MAIN) and create our window.
5339 * @dontinclude anchorblock_example_01.c
5344 * With the needed variables declared, we'll create the window and a box to
5345 * hold our widgets, but we don't need to go through that here.
5347 * In order to make clear where the anchorblock ends and the anchorview
5348 * begins, they'll be each inside a @ref Frame. After creating the frame,
5349 * the anchorblock follows.
5350 * @skip elm_frame_add
5351 * @until elm_frame_content_set
5353 * Nothing out of the ordinary there. What's worth mentioning is the call
5354 * to elm_anchorblock_hover_parent_set(). We are telling our widget that
5355 * when an anchor is clicked, the hover for the popup will cover the entire
5356 * window. This affects the area that will be obscured by the hover and
5357 * where clicking will dismiss it, as well as the calculations it does to
5358 * inform the best locations where to insert the popups content.
5359 * Other than that, the code is pretty standard. We also need to set our
5360 * callback for when an anchor is clicked, since it's our task to populate
5361 * the popup. There's no default for it.
5363 * The anchorview is no different, we only change a few things so it looks
5365 * @until elm_frame_content_set
5367 * Then we run, so stuff works and close our main function in the usual way.
5370 * Now, a little note. Normally you would use either one of anchorblock or
5371 * anchorview, set your one callback to clicks and do your stuff in there.
5372 * In this example, however, there are a few tricks to make it easier to
5373 * show both widgets in one go (and to save me some typing). So we have
5374 * two callbacks, one per widget, that will call a common function to do
5375 * the rest. The trick is using ::Elm_Entry_Anchorblock_Info for the
5376 * anchorview too, since both are equal, and passing a callback to use
5377 * for our buttons to end the hover, because each widget has a different
5379 * @until _anchorview_clicked_cb
5382 * The meat of our popup is in the following function. We check what kind
5383 * of menu we need to show, based on the name set to the anchor in the
5384 * markup text. If there's no type (something went wrong, no valid contact
5385 * in the address list) we are just putting a button that does nothing, but
5386 * it's perfectly reasonable to just end the hover and call it quits.
5388 * Our popup will consist of one main button in the middle of our hover,
5389 * and possibly a secondary button and a list of other options. We'll create
5390 * first our main button and check what kind of popup we need afterwards.
5393 * @until eina_stringshare_add
5396 * Each button has two callbacks, one is our hack to close the hover
5397 * properly based on which widget it belongs to, the other a simple
5398 * printf that will show the action with the anchors own data. This is
5399 * not how you would usually do it. Instead, the common case is to have
5400 * one callback for the button that will know which function to call to end
5401 * things, but since we are doing it this way it's worth noting that
5402 * smart callbacks will be called in reverse in respect to the order they
5403 * were added, and since our @c btn_end_cb will close the hover, and thus
5404 * delete our buttons, the other callback wouldn't be called if we had
5407 * After our telephone popup, there are a few others that are practically
5408 * the same, so they won't be shown here.
5410 * Once we are done with that, it's time to place our actions into our
5411 * hover. Main button goes in the middle without much questioning, and then
5412 * we see if we have a secondary button and a box of extra options.
5413 * Because I said so, secondary button goes on either side and box of
5414 * options either on top or below the main one, but to choose which
5415 * exactly, we use the hints our callback info has, which saves us from
5416 * having to do the math and see which side has more space available, with
5417 * a little special case where we delete our extra stuff if there's nowhere
5421 * @skip evas_object_smart
5422 * @until evas_object_del(box)
5426 * The example will look like this:
5428 * @image html screenshots/anchorblock_01.png
5429 * @image latex screenshots/anchorblock_01.eps width=\textwidth
5431 * @example anchorblock_example_01.c
5435 * @page tutorial_check Check example
5436 * @dontinclude check_example_01.c
5438 * This example will show 2 checkboxes, one with just a label and the second
5439 * one with both a label and an icon. This example also ilustrates how to
5440 * have the checkbox change the value of a variable and how to react to those
5443 * We will start with the usual setup code:
5446 * And now we create our first checkbox, set its label, tell it to change
5447 * the value of @p value when the checkbox stats is changed and ask to be
5448 * notified of state changes:
5451 * For our second checkbox we are going to set an icon so we need to create
5454 * @note For simplicity we are using a rectangle as icon, but any evas object
5457 * And for our second checkbox we set the label, icon and state to true:
5460 * We now do some more setup:
5463 * And finally implement the callback that will be called when the first
5464 * checkbox's state changes. This callback will use @p data to print a
5467 * @note This work because @p data is @p value(from the main function) and @p
5468 * value is changed when the checkbox is changed.
5470 * Our example will look like this:
5472 * @image html screenshots/check_example_01.png
5473 * @image latex screenshots/check_example_01.eps width=\textwidth
5475 * @example check_example_01.c
5479 * @page tutorial_colorselector Color selector example
5480 * @dontinclude colorselector_example_01.c
5482 * This example shows how to change the color of a rectangle using a color
5483 * selector. We aren't going to explain a lot of the code since it's the
5487 * Now that we have a window with background and a rectangle we can create
5488 * our color_selector
5489 * @until elm_colorselector_add
5491 * Now colors can be loaded to color selector's palette by setting the palette name
5494 * Next we ask to be notified whenever the color changes on selector:
5497 * Next we ask to be notified whenever the color item is selected and longpressed:
5498 * @until color,item,longpressed
5500 * We add some more code to the usual setup code:
5503 * now get to the "changed" callback that sets the color of the rectangle:
5506 * And now get to the "color,item,selected" callback that sets the color of the rectangle:
5509 * And now get to the "color,item,longpressed" callback that gets and displays
5510 * the color of the rectangle:
5513 * This example will look like this:
5515 * @image html screenshots/colorselector_example_01.png
5516 * @image latex screenshots/colorselector_example_01.eps width=\textwidth
5518 * @example colorselector_example_01.c
5522 * @page slideshow_example Slideshow widget example
5524 * This application is aimed to exemplify the slideshow widget. It
5525 * consists of a window with a slideshow widget set as "resize
5526 * object", along with a control bar, in the form of a notify. Those
5527 * controls will exercise most of the slideshow's API functions.
5529 * We create the slideshow, itself, first, making it @b loop on its
5530 * image itens, when in slideshow mode:
5531 * @dontinclude slideshow_example.c
5532 * @skip slideshow = elm_slideshow_add
5533 * @until evas_object_show
5535 * Next, we define the <b>item class</b> for our slideshow
5536 * items. Slideshow images are going to be Elementary @ref Photo "photo"
5537 * widgets, here, as pointed by our @c get class
5538 * function. We'll let the Elementary infrastructure to delete those
5539 * objects for us, and, as there's no additional data attached to our
5540 * slideshow items, the @c del class function can be left undefined:
5541 * @dontinclude slideshow_example.c
5544 * @dontinclude slideshow_example.c
5547 * @dontinclude slideshow_example.c
5548 * @skip get our images to make slideshow items
5551 * We now get to populate the slideshow widget with items. Our images
5552 * are going to be some randomly chosen from the Elementary package,
5553 * nine of them. For the first eight, we insert them ordered in the
5554 * widget, by using elm_slideshow_item_sorted_insert(). The comparing
5555 * function will use the image names to sort items. The last item is
5556 * inserted at the end of the slideshow's items list, with
5557 * elm_slideshow_item_add(). We check out how that list ends with
5558 * elm_slideshow_items_get(), than:
5559 * @dontinclude slideshow_example.c
5560 * @skip static const char *img
5562 * @dontinclude slideshow_example.c
5566 * Note that we save the pointers to the first and last items in the
5567 * slideshow, for future use.
5569 * What follows is the code creating a notify, to be shown over the
5570 * slideshow's viewport, with knobs to act on it. We're not showing
5571 * that boilerplate code, but only the callbacks attached to the
5572 * interesting smart events of those knobs. The first four are
5573 * buttons, which will:
5574 * - Select the @b next item in the slideshow
5575 * - Select the @b previous item in the slideshow
5576 * - Select the @b first item in the slideshow
5577 * - Select the @b last item in the slideshow
5579 * Check out the code for those four actions, being the two last @c
5580 * data pointers the same @c first and @c last pointers we save
5581 * before, respectively:
5582 * @dontinclude slideshow_example.c
5583 * @skip jump to next
5589 * What follow are two hoversels, meant for one to change the
5590 * slideshow's @b transition and @b layout styles, respectively. We
5591 * fetch all the available transition and layout names to populate
5592 * those widgets and, when one selects any of them, we apply the
5593 * corresponding setters on the slideshow:
5594 * @dontinclude slideshow_example.c
5595 * @skip hv = elm_hoversel_add
5598 * @dontinclude slideshow_example.c
5599 * @skip transition changed
5603 * For one to change the transition @b time on the slideshow widget,
5604 * we use a spinner widget. We set it to the initial value of 3
5605 * (seconds), which will be probed by the next knob -- a button
5606 * starting the slideshow, de facto. Note that changing the transition
5607 * time while a slideshow is already happening will ajust its
5609 * @dontinclude slideshow_example.c
5610 * @skip spin = elm_spinner_add
5611 * @until evas_object_show
5612 * @dontinclude slideshow_example.c
5613 * @skip slideshow transition time has
5616 * Finally, we have two buttons which will, respectively, start and
5617 * stop the slideshow on our widget. Here are their "clicked"
5619 * @dontinclude slideshow_example.c
5620 * @skip start the show
5624 * This is how the example program's window looks like:
5625 * @image html screenshots/slideshow_example.png
5626 * @image latex screenshots/slideshow_example.eps width=\textwidth
5628 * See the full @ref slideshow_example_c "source code" for
5631 * @example slideshow_example.c
5635 * @page tutorial_photocam Photocam example
5636 * @dontinclude photocam_example_01.c
5638 * In this example we will have a photocam and a couple of buttons and slider to
5639 * control the photocam. To avoid cluttering we'll only show the parts of the
5640 * example that relate to the photocam, the full source code can be seen @ref
5641 * photocam_example_01.c "here".
5643 * Creating a photocam is as easy as creating any other widget:
5644 * @skipline elm_photocam_add
5646 * A photocam is only useful if we have a image on it, so lets set a file for it
5650 * We now set the photocam to not bounce horizontally:
5653 * And we want to know when the photocam has finished loading the image so:
5654 * @until smart_callback
5656 * The reason to know when the image is loaded is so that we can bring the
5657 * center of the image into view:
5661 * As mentioned we have 2 buttons in this example, the "Fit" one will cause
5662 * the photocam to go in to a zoom mode that makes the image fit inside the
5663 * photocam. Tough this has no effect on the image we also print what region was
5664 * being viewed before setting the zoom mode:
5666 * @note When in fit mode our slider(explained below) won't work.
5668 * The second button("Unfit") will bring the photocam back into manual zoom
5672 * Our slider controls the level of zoom of the photocam:
5674 * @note It is important to note that this only works when in manual zoom mode.
5676 * Our example will initially look like this:
5678 * @image html screenshots/photocam_example_01.png
5679 * @image latex screenshots/photocam_example_01.eps width=\textwidth
5681 * @example photocam_example_01.c
5685 * @page inwin_example_01 Inwin - General overview
5687 * Inwin is a very simple widget to show, so this example will be a very simple
5688 * one, just using all of the available API.
5690 * The program is nothing but a window with a lonely button, as shown here.
5692 * @image html screenshots/inwin_example.png
5693 * @image latex screenshots/inwin_example.eps width=\textwidth
5695 * And pressing the button makes an inwin appear.
5697 * @image html screenshots/inwin_example_a.png
5698 * @image latex screenshots/inwin_example_a.eps width=\textwidth
5700 * And the code is just as simple. We being with some global variables to keep
5701 * track of our Inwin.
5702 * @dontinclude inwin_example.c
5704 * @until current_style
5706 * And two callbacks used by the buttons the above screenshot showed. In these,
5707 * we check if @c inwin exists and execute the proper action on it. If it's not
5708 * there anymore, then we were abandoned to our luck, so we disabled ourselves.
5709 * @until _inwin_destroy
5713 * The lonely button from the beginning, when clicked, will call the following
5714 * function, which begins by checking if an inwin exists, and if it's there,
5715 * we bring it back to the front and exit from our function without any further
5719 * But if no inwin is there to show, we need to create one. First we need the
5720 * top-most window for the program, as no inwin can be created using other
5721 * objects as parents. Then we create our popup, set the next style in the list
5723 * @until current_style =
5725 * As for the content of our inwin, it's just a box with a label and some
5727 * @until _inwin_destroy
5730 * Now, all the code above shows how every object must always be set as content
5731 * for some other object, be it by setting the full content, packing it in a
5732 * box or table or working as icon for some other widget. But we didn't do
5733 * anything like that for the inwin, this one is just created and shown and
5734 * everything works. Other widgets can be used this way, but they would need
5735 * to be placed and resized manually or nothing would be shown correctly. The
5736 * inwin, however, sets itself as a children of the top-level window and will
5737 * be resized as the parent window changes too.
5739 * Another characteristic of Inwin is that when it's shown above everyone else,
5740 * it will work kind of like a modal window, blocking any other widget from
5741 * receiving events until the window is manually dismissed by pressing some
5742 * button to close it or having blocking task signalling its completion so
5743 * normal operations can be resumed. This is unlike the @ref Hover widget,
5744 * that would show its content on top of the designated target, but clicking
5745 * anywhere else would dismiss it automatically.
5747 * To illustrate that last point, when we close the main window and an inwin
5748 * is still there, we'll take out the content from the inwin and place it in
5753 * And the rest of the program doesn't have anything else related to inwin,
5754 * so it won't be shown here, but you can find it in
5755 * @ref inwin_example.c "inwin_example.c".
5757 * @example inwin_example.c
5761 * @page tutorial_scroller Scroller example
5762 * @dontinclude scroller_example_01.c
5764 * This example is very short and will illustrate one way to use a scroller.
5765 * We'll omit the declaration of the @p text variable because it's a very long
5766 * @htmlonly<a href="http://lipsum.com/">@endhtmlonly ipsum lorem
5767 * @htmlonly</a>@endhtmlonly. If you really want to see the full code, it's @ref
5768 * scroller_example_01.c "scroller_example_01.c".
5770 * We start our example by creating our window and background:
5774 * Next we create a label and set it's text to @p text(very long ipsum lorem):
5775 * @until show(label)
5777 * We then create our scroller, ask that it have the same size as the window and
5779 * @until content_set
5781 * We are now going to set a number of properties in our scroller:
5782 * @li We make it bounce horizontally but not vertically.
5783 * @li We make both scrollbars always be visible.
5784 * @li We have the events be propagated from the content to the scroller.
5785 * @li We enforce a page policy vertically(having a page be the size of the
5786 * viewport) and leave horizontal scrolling free.
5787 * @li And finally we ask the scroller to show us a region starting at 50,50 and
5788 * having a width and height of 200px.
5789 * @until region_show
5790 * @note Observant reader will note that the elm_scroller_region_show() didn't
5791 * scroll the view vertically, this is because we told the scroller to only
5792 * accept vertical scrolling in pages.
5794 * And now we're done:
5797 * Our example will look like this:
5799 * @image html screenshots/scroller_example_01.png
5800 * @image latex screenshots/scroller_example_01.eps width=\textwidth
5802 * @example scroller_example_01.c
5806 * @page tutorial_table_01
5808 * In this example we add four labels to a homogeneous table that has a padding
5809 * of 5px between cells.
5811 * The interesting bits from this example are:
5812 * @li Where we set the table as homogeneous and the padding:
5813 * @dontinclude table_example_01.c
5815 * @until homogeneous_set
5816 * @li Where we add each label to the table:
5817 * @skipline elm_table_pack
5818 * @skipline elm_table_pack
5819 * @skipline elm_table_pack
5820 * @skipline elm_table_pack
5822 * Here you can see the full source:
5823 * @include table_example_01.c
5825 * Our example will look like this:
5827 * @image html screenshots/table_example_01.png
5828 * @image latex screenshots/table_example_01.eps width=\textwidth
5830 * @example table_example_01.c
5834 * @page tutorial_table_02
5836 * For our second example we'll create a table with 4 rectangles in it. Since
5837 * our rectangles are of different sizes our table won't be homogeneous.
5839 * The interesting bits from this example are:
5840 * @li Where we set the table as not homogeneous:
5841 * @dontinclude table_example_02.c
5842 * @skipline homogeneous_set
5843 * @li Where we add each rectangle to the table:
5844 * @skipline elm_table_pack
5845 * @skipline elm_table_pack
5846 * @skipline elm_table_pack
5847 * @skipline elm_table_pack
5849 * Here you can see the full source:
5850 * @include table_example_02.c
5852 * Our example will look like this:
5854 * @image html screenshots/table_example_02.png
5855 * @image latex screenshots/table_example_02.eps width=\textwidth
5857 * @example table_example_02.c
5861 * @page tutorial_menu Menu Example
5862 * @dontinclude menu_example_01.c
5864 * This example shows how to create a menu with regular items, object items,
5865 * submenus and how to delete items from a menu. The full source for this
5866 * example is @ref menu_example_01.c "menu_example_01.c".
5868 * We'll start looking at the menu creation and how to create a very simple
5873 * For our next item we are going to add an icon:
5876 * Now we are going to add more items, but these icons are going to have a
5877 * parent, which will put them in a sub-menu. First just another item with an
5881 * Next we are going to add a button to our menu(any elm widget can be added to
5885 * We are also going to have the button delete the first item of our
5886 * sub-menu when clicked:
5887 * @until smart_callback
5888 * @dontinclude menu_example_01.c
5892 * We now add a separator and three more regular items:
5897 * We now add another item, however this time it won't go the sub-menu and it'll
5899 * @until disabled_set
5901 * To make sure that our menu is shown whenever the window is clicked(and where
5902 * clicked) we use the following callback:
5903 * @dontinclude menu_example_01.c
5908 * Our example will look like this:
5910 * @image html screenshots/menu_example_01.png
5911 * @image latex screenshots/menu_example_01.eps width=\textwidth
5913 * @example menu_example_01.c
5917 * @page win_example_01 Win - General API overview
5919 * For most users of the Elementary API, the @ref Win widget has a lot more
5920 * functions than what they need.
5922 * In general, a developer will create a window, set some content on it and
5923 * forget about it for the rest of its program's life, letting whatever
5924 * Window Manager is there to handle the window. Here, however, we are going
5925 * to show how to generally manage a window.
5927 * We'll have a bit more than the usual includes here, since part of the
5928 * example requires some low level fiddling.
5929 * @dontinclude win_example.c
5930 * @skip Elementary.h
5933 * The program then, consists of one window with two lists of buttons, each
5934 * of which operates on another two windows. One of them is a normal window,
5935 * the other has the @c override flag set so the Window Manager ignores it.
5937 * Pressing each button will call the corresponding function to act on the
5938 * corresponding window. These are pretty self explanatory, so we'll show
5939 * them in one batch.
5941 * @until elm_win_sticky_set
5944 * Next, we handle the main window closing. We have a @c "delete,request"
5945 * callback set to ask if really want to quit. If so, we end the main loop,
5946 * otherwise just delete the popup message and continue running normally.
5947 * @until _no_quit_cb
5948 * @until _no_quit_cb
5951 * The non-managed window, being completely ignored by the Window Manager,
5952 * is likely to never receive keyboard focus, even if we click on its entry
5953 * to write something. So we have a button on it that will forcefully focus
5954 * it by using some lower level functions to act directly on the X window.
5955 * Then, each time one of the window is focused, we print some message on a
5956 * console to show this more clearly.
5957 * @until _win_focused_cb
5960 * And to finalize, the main function creates a window to hold all the action
5961 * buttons and another two to show how (and what) works on each of them.
5963 * First, the main window will be a normal window, we'll enable the focus
5964 * highlight regardless of how it is configured so it's easier to navigate
5965 * the window with the keyboard. Then we hook our focus and delete callbacks
5966 * and set up the rest of the window's content.
5967 * @until evas_object_show(box)
5969 * The first of our sub-windows is the managed one. We'll create it as a
5970 * dialog, which should make the Window Manager treat it as a non-resizable
5971 * window. We are also setting the window to be auto-deleted when the close
5972 * button in the titlebar is pressed.
5973 * @until evas_object_show(o)
5975 * Now, we added an icon to the window as a resize object. We also set this
5976 * icon to not scale, and no weight size hints have been set for it. This way,
5977 * even if we hadn't created the window as a dialog, it would still not be
5978 * resizable. The window size is defined by its content, so it would never be
5979 * smaller than the smallest of its resize objects, and for it to be resizable,
5980 * all of those objects have to allow it.
5982 * Next, we add the buttons with the actions to perform on this window. Using
5983 * a macro saves us typing and makes the world a happier place.
5984 * @until WIN_ACTION(sticky)
5986 * The maximize one is likely to not work, because the Window Manager will
5987 * probably not enforce it upon a window that states its maximum size, much
5988 * less a dialog. But that can be changed by editting the example to use
5989 * #ELM_WIN_BASIC when creating the window and adding the following line to
5990 * the icon set as content
5992 * evas_object_size_hint_weight_set(o, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
5995 * Lastly, the second sub-window will have it's override flag set. In it we
5996 * have a label with some text, and entry and a button. The entry can be
5997 * clicked normally to set focus on it, but whether it actually gets keyboard
5998 * input will also depend on the window getting focus, and since the window
5999 * is an override one, it will probably not gain it by normal means. The
6000 * button is there to force the focus at the X level to go to our window.
6001 * And to finish, another list of buttons with actions to perform on this
6002 * last window. Remember that most of them are requests or hints for the
6003 * Window Manager, so they are likely to do nothing on this window.
6004 * Similarly, there won't be any way to move it or resize it, because we
6005 * haven't implemented that kind of control on this example and that's
6006 * something controlled by Window Managers on windows they are tracking, which
6007 * is not the case with this one.
6010 * The full code listing of this example can be found at
6011 * @ref win_example.c "win_example.c".
6013 * @example win_example.c
6017 * @page web_example_01 Web - Simple example
6019 * WebKit-EFL is independent of any particular toolkit, such as Elementary,
6020 * so using it on applications requires that the programmer writes a lot of
6021 * boiler plate code to manage to manage the web object.
6023 * For a full featured browser this may make sense, as the programmer will
6024 * want to have full control of every aspect of the web object, since it's the
6025 * main component of the application. But other programs with simpler
6026 * requirements, having to write so much code is undesired.
6028 * This is where elm_web comes in. Its purpose is to provide a simple way
6029 * for developers to embed a simple web object in their programs, simplifying
6030 * the common use cases.
6032 * This is not to say that a browser can't be made out of it, as this example
6035 * We'll be making a simple browser, consisting of one window with an URL bar,
6036 * a toolbar to be used for the tabs and a pager to show one page at a time.
6038 * When all tabs are closed, we'll be showing a default view with some custom
6039 * content, for which we need to get the internal @c ewk_view object and use
6040 * some WebKit functions on it, thus we need to include the necessary headers
6043 * @dontinclude web_example.c
6047 * A struct to keep track of the different widgets in use and the currently
6048 * shown tab. There's also an @c exiting flag, used to work around the overly
6049 * simplistic way in which this example is written, just to avoid some
6050 * warnings when closing the program.
6056 * Each tab has its own struct too, but there's not much to it.
6059 * Whenever the currently selected tab changes, we need to update some state
6060 * on the application. The back and forward buttons need to be disabled
6061 * accordingly and the URL bar needs to show the right address.
6064 * @until naviframe_item_simple_promote
6067 * Other updates happen based on events from the web object, like title change
6068 * to update the name shown in the tab, and URL change which will update the
6069 * URL bar if the event came from the currently selected tab.
6071 * @skip tab_current_set
6076 * Adding a new tab is just a matter of creating a new web widget, its data
6077 * and pushing it into the pager. A lot of the things that we should handle
6078 * here, such as how to react to popups and JavaScript dialogs, are done
6079 * already in the @c elm_web widget, so we can rely on their default
6080 * implementations. For the JavaScript dialogs we are going to avoid having
6081 * them open in a new window by setting the @c Inwin mode.
6083 * There is no default implementation, however, for the requests to create a
6084 * new window, so we have to handle them by setting a callback function that
6085 * will ultimately call this very same function to add a new tab.
6090 * Entering an address in the URL bar will check if a tab exists, and if not,
6091 * create one and set the URL for it. The address needs to conform to the URI
6092 * format, so we check that it does and add the protocol if it's missing.
6095 * @until eina_stringshare_del
6098 * The navigation buttons are simple enough. As for the refresh, it normally
6099 * reloads the page using anything that may exist in the caches if applicable,
6100 * but we can press it while holding the @c Shift key to avoid the cache.
6103 * @until web_forward
6106 * The callback set for the new window request creates a new tab and returns
6107 * the web widget associated with it. This is important, this function must
6108 * return a valid web widget returned by elm_web_add().
6110 * @skip static Evas_Object
6113 * Pressing @c Ctrl-F will bring up the search box. Nothing about the box
6114 * itself is worth mentioning here, but it works as you would expect from any
6115 * other browser. While typing on it, it will highlight all occurrences of the
6116 * searched word. Pressing @c Enter will go to the next instance and the two
6117 * buttons next to the entry will move forward and backwards through the found
6120 * @skip win_del_request
6122 * @until win_search_trigger
6125 * Last, create the main window and put all of the things used above in it. It
6126 * contains a default web widget that will be shown when no tabs exist. This
6127 * web object is not browsable per se, so history is disabled in it, and we
6128 * set the same callback to create new windows, on top of setting some custom
6129 * content of our own on it, with some links that will open new tabs to start
6135 * Some parts of the code were left out, as they are not relevant to the
6136 * example, but the full listing can be found at @ref web_example.c
6139 * @example web_example.c
6143 * @page efl_thread_1 EFL Threading example 1
6145 * You can use threads with Elementary (and EFL) but you need to be careful
6146 * to only use eina or eet calls inside a thread. Other libraries are not
6147 * totally threadsafe except for some specific ecore calls designed for
6148 * working from threads like the ecore_pipe_write() and ecore_thread calls.
6150 * Below is an example of how to use EFL calls from a native thread you have
6151 * already created. You have to put the EFL calls inside the critical block
6152 * between ecore_thread_main_loop_begin() and ecore_thread_main_loop_end()
6153 * which ensure you gain a lock on the mainloop. Beware that this requires
6154 * that the thread WAIT to synchronize with the mainloop at the beginning of
6155 * the critical section. It is highly suggested you use as few of these
6156 * in your thread as possible and probably put just a single
6157 * ecore_thread_main_loop_begin() / ecore_thread_main_loop_end() section
6158 * at the end of the threads calculation or work when it is done and
6159 * would otherwise exit to sit idle.
6161 * For a progression of examples that become more complex and show other
6162 * ways to use threading with EFL, please see:
6174 * @include efl_thread_1.c
6178 * @page efl_thread_2 EFL Threading example 2
6180 * You can also use ecore_main_loop_thread_safe_call_sync() to call a
6181 * specific function that needs to do EFL main loop operations. This call
6182 * will block and wait to synchronise to the mainloop just like
6183 * ecore_thread_main_loop_begin() / ecore_thread_main_loop_end() will,
6184 * but instead you simply provide it the function callback to call instead
6185 * of inlining your code.
6195 * @include efl_thread_2.c
6199 * @page efl_thread_3 EFL Threading example 3
6201 * Like with ecore_main_loop_thread_safe_call_sync() you can provide a
6202 * callback to call inline in the mainloop, but this time with
6203 * ecore_main_loop_thread_safe_call_async() the callback is queued and
6204 * called asynchronously, without the thread blocking. The mainloop will
6205 * call this function when it comes around to its synchronisation point. This
6206 * acts as a "fire and forget" way of having the mainloop do some work
6207 * for a thread that has finished processing some data and is read to hand it
6208 * off to the mainloop and the thread wants to march on and do some more work
6209 * while the main loop deals with "displaying" the results of the previous
6218 * @include efl_thread_3.c
6222 * @page efl_thread_4 EFL Threading example 4
6224 * Now when you want to have a thread do some work, send back results to
6225 * the mainloop and continue running but the mainloop controls when the
6226 * thread should stop working, you need some extra flags. This is an example
6227 * of how you might use ecore_main_loop_thread_safe_call_async() and pthreads
6234 * @include efl_thread_4.c
6238 * @page efl_thread_5 EFL Threading example 5
6240 * This is the same as @ref efl_thread_4 but now uses the ecore_thread
6241 * infrastructure to have a running worker thread that feeds results back
6242 * to the mainloop and can easily be cancelled. This saves some code in the
6243 * application and makes for fewer problem spots if you forget a mutex.
6247 * @include efl_thread_5.c
6251 * @page efl_thread_6 EFL Threading example 6
6253 * You can also use the ecore_thread infrastructure for compute tasks that
6254 * don't send feedback as they go - they are one-shot compute jobs and when
6255 * done they will trigger the end callback in the mainloop which is intended
6256 * to pick up the results and "display them".
6258 * @include efl_thread_6.c
6262 * @page bg_example_01_c bg_example_01.c
6263 * @include bg_example_01.c
6264 * @example bg_example_01.c
6268 * @page bg_example_02_c bg_example_02.c
6269 * @include bg_example_02.c
6270 * @example bg_example_02.c
6274 * @page bg_example_03_c bg_example_03.c
6275 * @include bg_example_03.c
6276 * @example bg_example_03.c
6280 * @page actionslider_example_01 Actionslider example
6281 * @include actionslider_example_01.c
6282 * @example actionslider_example_01.c
6286 * @page transit_example_01_c Transit example 1
6287 * @include transit_example_01.c
6288 * @example transit_example_01.c
6292 * @page transit_example_02_c Transit example 2
6293 * @include transit_example_02.c
6294 * @example transit_example_02.c
6298 * @page general_functions_example_c General (top-level) functions example
6299 * @include general_funcs_example.c
6300 * @example general_funcs_example.c
6304 * @page clock_example_c Clock example
6305 * @include clock_example.c
6306 * @example clock_example.c
6310 * @page datetime_example_c Datetime example
6311 * @include datetime_example.c
6312 * @example datetime_example.c
6316 * @page dayselector_example_c Dayselector example
6317 * @include dayselector_example.c
6318 * @example dayselector_example.c
6322 * @page flipselector_example_c Flipselector example
6323 * @include flipselector_example.c
6324 * @example flipselector_example.c
6328 * @page fileselector_example_c Fileselector example
6329 * @include fileselector_example.c
6330 * @example fileselector_example.c
6334 * @page fileselector_button_example_c Fileselector button example
6335 * @include fileselector_button_example.c
6336 * @example fileselector_button_example.c
6340 * @page fileselector_entry_example_c Fileselector entry example
6341 * @include fileselector_entry_example.c
6342 * @example fileselector_entry_example.c
6346 * @page index_example_01_c Index example
6347 * @include index_example_01.c
6348 * @example index_example_01.c
6352 * @page index_example_02_c Index example
6353 * @include index_example_02.c
6354 * @example index_example_02.c
6358 * @page layout_example_01_c layout_example_01.c
6359 * @include layout_example_01.c
6360 * @example layout_example_01.c
6364 * @page layout_example_02_c layout_example_02.c
6365 * @include layout_example_02.c
6366 * @example layout_example_02.c
6370 * @page layout_example_03_c layout_example_03.c
6371 * @include layout_example_03.c
6372 * @example layout_example_03.c
6376 * @page layout_example_edc An example of layout theme file
6378 * This theme file contains two groups. Each of them is a different theme, and
6379 * can be used by an Elementary Layout widget. A theme can be used more than
6380 * once by many different Elementary Layout widgets too.
6382 * @include layout_example.edc
6383 * @example layout_example.edc
6387 * @page gengrid_example_c Gengrid example
6388 * @include gengrid_example.c
6389 * @example gengrid_example.c
6393 * @page genlist_example_01_c genlist_example_01.c
6394 * @include genlist_example_01.c
6395 * @example genlist_example_01.c
6399 * @page genlist_example_02_c genlist_example_02.c
6400 * @include genlist_example_02.c
6401 * @example genlist_example_02.c
6405 * @page genlist_example_04_c genlist_example_04.c
6406 * @include genlist_example_04.c
6407 * @example genlist_example_04.c
6411 * @page genlist_example_05_c genlist_example_05.c
6412 * @include genlist_example_05.c
6413 * @example genlist_example_05.c
6417 * @page thumb_example_01_c thumb_example_01.c
6418 * @include thumb_example_01.c
6419 * @example thumb_example_01.c
6423 * @page progressbar_example_c Progress bar example
6424 * @include progressbar_example.c
6425 * @example progressbar_example.c
6429 * @page slideshow_example_c Slideshow example
6430 * @include slideshow_example.c
6431 * @example slideshow_example.c
6435 * @page efl_thread_1_c EFL Threading example 1
6436 * @include efl_thread_1.c
6437 * @example efl_thread_1.c
6441 * @page efl_thread_2_c EFL Threading example 2
6442 * @include efl_thread_2.c
6443 * @example efl_thread_2.c
6447 * @page efl_thread_3_c EFL Threading example 3
6448 * @include efl_thread_3.c
6449 * @example efl_thread_3.c
6453 * @page efl_thread_4_c EFL Threading example 4
6454 * @include efl_thread_4.c
6455 * @example efl_thread_4.c
6459 * @page efl_thread_5_c EFL Threading example 5
6460 * @include efl_thread_5.c
6461 * @example efl_thread_5.c
6465 * @page efl_thread_6_c EFL Threading example 6
6466 * @include efl_thread_6.c
6467 * @example efl_thread_6.c