path: root/src/lib/elementary/elm_naviframe_part.eo
diff options
authorJean-Philippe Andre <>2017-11-20 15:41:07 +0900
committerJean-Philippe Andre <>2017-11-20 19:02:09 +0900
commitdda18948ae762d7a37c0035a44b69f44ec615214 (patch)
tree513ea65743b9e70ab7305431b0b7e9119704efc9 /src/lib/elementary/elm_naviframe_part.eo
parent67188ba22b804cba20ed904df5026b45336e09fe (diff)
efl: Split Efl.Container and Efl.Content
When I first implemented the Efl.Container interface I made a mistake of mixing "single slot" content API's with "multiple children" content API's. This should fix that, by separating API's that are for a single part and those that deal with a list of children. Efl.Content: Single slot. This will be used a lot by efl_part() objects, and for the default content of widgets (eg. the window content). Efl.Container: Multiple children. Used by lists, boxes, layouts (edje/elm), etc... I didn't see any class that implemented both interfaces (note: Layout implements Container and Button implements Content, so technically Button implements both through inheritance). For now the eo_prefix is not changed in Efl.Container. I wonder if it should be reset (to efl_container) or not. This would only affect the C API. Ref T5328
Diffstat (limited to 'src/lib/elementary/elm_naviframe_part.eo')
1 files changed, 2 insertions, 2 deletions
diff --git a/src/lib/elementary/elm_naviframe_part.eo b/src/lib/elementary/elm_naviframe_part.eo
index 429dee6..a84559f 100644
--- a/src/lib/elementary/elm_naviframe_part.eo
+++ b/src/lib/elementary/elm_naviframe_part.eo
@@ -3,8 +3,8 @@ class Elm.Naviframe.Part (Efl.Ui.Layout.Part_Legacy)
3 [[Elementary naviframe internal part class]] 3 [[Elementary naviframe internal part class]]
4 data: null; 4 data: null;
5 implements { 5 implements {
6 Efl.Container.content { get; set; } 6 Efl.Content.content { get; set; }
7 Efl.Container.content_unset; 7 Efl.Content.content_unset;
8 Efl.Text.text { set; get; } 8 Efl.Text.text { set; get; }
9 } 9 }
10} 10}