path: root/src/lib/elementary/elm_box.eo (follow)
AgeCommit message (Collapse)Author
2018-01-24efl_ui_legacy: add new interface to indicate legacy widgetSungtaek Hong
Summary: For now, how to check whether a widget is legacy or not is to check flags in private data or static flag, which is set during elm_legacy_add. If Efl.Ui.Legacy interface is added, it can be easilly checked by efl_isa(obj, EFL_UI_LEGACY_INTERFACE) Reviewers: woohyun, jpeg, cedric, Jaehyun_Cho Subscribers: conr2d, cedric, jpeg Differential Revision:
2018-01-08widget: rename elm widget to Efl.Ui.Widget.Amitesh Singh
2017-10-16elm_box: port to compositionMarcel Hollerbach
2017-10-10elm_box: remove old api!Marcel Hollerbach
2017-09-15elementary: convert to new ownershipDaniel Kolesa
2017-09-02elm_widget: move the complete regsiter/unregister logicMarcel Hollerbach
We had here a little problem, state focus_state_eval function handled the unregisteration and consideration of the focus flags and then only called a helper function (which was a widget function), that then did the registeration in logical or regular mode. Elm scroller for example took that function overwrote it and did onyl permit logical registrations. Then again a evaluation of the focus state and flags took place, and the function considered elm_scroller should be registered as regular object, but found it to be logical. This lead to the problem that we permantently unregistered Elm.Scroller and registered it again as logical just to unregister it again. This was on the one side a performance downside. But also a bug since all items from within the Elm_Scrollers sub manager are getting reparent onto the parent, which means not the root of the scroller (the scroller itself) is the logical entrypoint to the widget but rather this reparented widget, which led to unexpected focus warps like described in T5923. tldr: this fixes T5923
2017-08-23widget: Make sub_object add/del protected (EO)Jean-Philippe Andre
Also prefix with widget. I want to rename this as child rather than sub. It's inconsistent with the other parent/child hierarchies. Anyway the various hierarchies are confusing, so let's keep this name :) Ref T5363
2017-05-29ecore: Remove ecore_types.eotJean-Philippe Andre
This moves one enum from EO to legacy only (Ecore_Pos_Map). Ideally the type should be in Ecore_Legacy and no Common, that can be done later. Ref T5522
2017-05-24elm: Remove elm_box_layout_set from EOJean-Philippe Andre
This removes a type from ecore_types.eot elm_box is legacy. Efl.Ui.Box is the new EO-enabled box. Ref T5522
2017-05-19evas/elm: Make group_add/group_del internal functionsJean-Philippe Andre
This hides those two legacy functions from the EO API.
2017-05-15evas: Remove Evas.Coord from EOJean-Philippe Andre
This may be a bit more controversial... But Evas_Coord really is just an int and all the internals of EFL assume that the base coordinate type is a 32-bit int. So this type is a bit redondant and can't easily be changed to, say, a float or int64. Ref T5312
2017-04-25elm_box/table: set the order directly when a container is registeredMarcel Hollerbach
The following situation: - A Box in a naviframe, with n children. - All added children register to the focus graph with the box as parent, order gets set correctly. - Naviframe hides this item, so box property tree unfocusable gets set to true, it gets unregistered from the focus graph, even every single child gets unregistered. - The item gets shown - every child and the table are getting registered again. - Order is not set again, since the box does not get changed - Order of the children is mixed up. This should fix this case since the order is flushed every time the box gets registered.
2016-11-24docs: elm: fill gaps in box, grid, icon, inwin and label eo file documentationStefan Schmidt
2016-08-11Change the EFL to follow the new Eo rename.Tom Hacohen
2016-06-21evas: Rename Evas.Object to Efl.Canvas.ObjectJean-Philippe Andre
One step closer to make the EO inheritance tree look like it's all Efl.
2016-06-17Evas: Rename smart object into Efl.Canvas.GroupJean-Philippe Andre
2016-06-17Evas: Add smart_ prefix to all smart functions (eo)Jean-Philippe Andre
This is a first step at separating legacy smart object features away from standard efl interfaces.
2016-06-02eolian: utilize the new void_ptr builtin across eo filesDaniel Kolesa
This lets me narrow down the remaining cases of pointers across the EFL. The void pointers will later need to be reevaluated on per-case basis and replaced appropriately where possible/feasible.
2016-05-23eolian: remove pointers from complex and class typesDaniel Kolesa
Complex types (i.e. list, array, hash, accessor etc.) now do not require pointers with them anymore (the pointer is implied) and the same goes for class handles. Eolian now explicitly disallows creating pointers to these as well. This is the first part of the work to remove pointers from Eolian completely, with the goal of simplifying the DSL (higher level) and therefore making it easier for bindings (as well as easier API usage). @feature
2016-05-17eolian: add event_prefix and have classes follow that or eo_prefix by defaultDaniel Kolesa
Previously events used to use class name as a prefix and ignored eo_prefix when specified. This is no longer the case. Events follow eo_prefix by default now. In order to get around this for classes where this is undesirable, a new field event_prefix was added which takes priority over eo_prefix. If neither is specified, class name is used like previously. @feature
2016-05-12Add legacy_prefix now that the default has changed to null.Tom Hacohen
2016-05-12Evas object smart: Fix namespace to use . and not _.Tom Hacohen
2016-04-20Ecore eo: Resolve duplicate Ecore_Cb definition.Tom Hacohen
2016-04-19Elm box: Fix eo type errors.Tom Hacohen
2016-03-23elementary: move all legacy files to their expected new location.Cedric BAIL