1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
/**
* @defgroup Naviframe Naviframe
* @ingroup Elementary
*
* @image html naviframe_inheritance_tree.png
* @image latex naviframe_inheritance_tree.eps
*
* @brief Naviframe stands for navigation frame. It's a views manager
* for applications.
*
* A naviframe holds views (or pages) as its items. Those items are
* organized in a stack, so that new items get pushed on top of the
* old, and only the topmost view is displayed at one time. Due to the
* characteristics of a stack, even though you push a new item, previous item
* is not deleted. Previous item will be shown when you pop new item. The
* transition between views is animated, depending on the theme applied to the
* widget.
*
* Naviframe views hold spaces to various elements, which are:
* - back button, used to navigate to previous views,
* - next button, used to navigate to next views in the stack,
* - title label,
* - sub-title label,
* - title icon and
* - content area.
*
* One can use @ref elm_object_item_part_content_set,
* @ref elm_object_item_part_content_get,
* @ref elm_object_item_part_content_unset functions to handle the contents.
* The swallow part name should be one of these:
* @li @c "default" - The main content of the current page
* @li @c "icon" - An icon in the title area of the current page
* @li @c "prev_btn" - A button of the current page to go to the
* previous page
* @li @c "next_btn" - A button of the current page to go to the next
* page
*
* One can use @ref elm_object_item_part_text_set,
* @ref elm_object_item_part_text_get to handle the text parts.
* The swallow part name should be one of these:
* @li @c "default" - A title label in the title area of the current page
* @li @c "subtitle" - A sub-title label in the title area of the
* current page
*
* Most of those content objects can be passed at the time of an item
* creation (see elm_naviframe_item_push()).
*
* Naviframe items can have different styles, which affect the
* transition between views, for example. On the default theme, two of
* them are supported:
* - @c "basic" - views are switched sliding horizontally, one after
* the other
* - @c "overlap" - like the previous one, but the previous view stays
* at its place and is overlapped by the new
*
*
* This widget emits the following signals, besides the ones sent from
* @ref Layout:
* @li @c "transition,finished" - When the transition is finished in
* changing the item
* @li @c "title,transition,finished" - When the title area's transition
* is finished in changing the state
* of the title
* @li @c "title,clicked" - User clicked title area
* @li @c "focused" - When the naviframe has received focus. (since 1.8)
* @li @c "unfocused" - When the naviframe has lost focus. (since 1.8)
* @li @c "language,changed" - the program's language changed (since 1.9)
*
* All the parts, for content and text, described here will also be
* reachable by naviframe @b items direct calls:
* @li @ref elm_object_item_del
* @li @ref elm_object_item_part_text_set
* @li @ref elm_object_item_part_text_get
* @li @ref elm_object_item_part_content_set
* @li @ref elm_object_item_part_content_get
* @li @ref elm_object_item_part_content_unset
* @li @ref elm_object_item_signal_emit
*
* What happens is that the topmost item of a naviframe will be the
* widget's target layout, when accessed directly. Items lying below
* the top one can be interacted with this way.
*
* Here is an example on its usage:
* @li @ref naviframe_example
*/
/**
* @addtogroup Naviframe
* @{
*/
#include "elc_naviframe_common.h"
#ifdef EFL_EO_API_SUPPORT
#include "elc_naviframe_eo.h"
#endif
#ifndef EFL_NOLEGACY_API_SUPPORT
#include "elc_naviframe_legacy.h"
#endif
/**
* @}
*/
|
