summaryrefslogtreecommitdiff
path: root/src/lib/elementary/elm_ctxpopup.eo (follow)
AgeCommit message (Collapse)Author
2019-03-07elm_ctxpopup: remove all legacy usage from eo filesMike Blumenkrantz
this takes the current generated output from eolian for legacy code in efl and adds it to the tree, then removes legacy references from the corresponding eo files. in the case where the entire eo file was for a legacy object, that eo file has been removed from the tree ref T7724 Reviewed-by: Cedric BAIL <cedric.bail@free.fr> Differential Revision: https://phab.enlightenment.org/D8163
2019-03-04efl.ui.widget: widget_event -> widget_input_event_handlerMike Blumenkrantz
Summary: ref T7553 Depends on D8081 Reviewers: cedric Reviewed By: cedric Subscribers: cedric, #reviewers, #committers Tags: #efl Maniphest Tasks: T7553 Differential Revision: https://phab.enlightenment.org/D8082
2019-02-28interfaces: don't inherit efl.ui.layout anymoreMike Blumenkrantz
Summary: this removes efl.file from the class hierarchy Reviewers: segfaultxavi Reviewed By: segfaultxavi Subscribers: segfaultxavi, cedric, #reviewers, #committers Tags: #efl_api Differential Revision: https://phab.enlightenment.org/D8042
2019-02-27elementary: remove unnecessessary disabled setterMarcel Hollerbach
summary_: those objects are disabled anyways, because disabled is applied to the objects in a tree. Which means, subobjects of a widget are disabled whenever the widget is disabled anyways. Depends on D8015 Reviewers: cedric, zmike, segfaultxavi, stefan_schmidt Reviewed By: segfaultxavi Subscribers: cedric, #reviewers, #committers Tags: #efl Reviewed-by: Xavi Artigas <xavierartigas@yahoo.es> Differential Revision: https://phab.enlightenment.org/D8016
2019-02-25efl_ui_widget: remove focused_itemMarcel Hollerbach
focused_item is only used in item containers. This API is now moved into a widget item container, which *can* have a focused item. ref T7553 Reviewed-by: WooHyun Jung <woohyun0705@gmail.com> Differential Revision: https://phab.enlightenment.org/D8013
2019-01-18efl: convert all classes to the new eolian syntaxMarcel Hollerbach
ref T7459 Reviewed-by: Daniel Kolesa <daniel@octaforge.org> Reviewed-by: Xavi Artigas <xavierartigas@yahoo.es> Differential Revision: https://phab.enlightenment.org/D7684
2019-01-02elementary: rename Efl.Ui.Translatable -> Efl.Ui.L10nCedric BAIL
If we are to choose Efl.Ui.I18n for the internationalization support, the localization API should be named accordingly L10n. Reviewed-by: Xavi Artigas <xavierartigas@yahoo.es> Differential Revision: https://phab.enlightenment.org/D7507
2018-11-16elementary: remove Efl.Ui.Layout namespaceJaehyun Cho
Summary: Efl.Ui.Layout namespace is removed to keep consistency with other widgets. Consequently, "Efl.Ui.Layout.Object" is renamed to "Efl.Ui.Layout" and "Efl.Ui.Layout." is renamed to "Efl.Ui.Layout_". Reviewers: segfaultxavi, bu5hm4n, cedric Reviewed By: segfaultxavi Subscribers: #reviewers, #committers, SanghyeonLee, woohyun Tags: #efl Differential Revision: https://phab.enlightenment.org/D7291
2018-05-24efl: major rewrite of efl_part.Cedric BAIL
The interface efl_part_get should not be directly called from C, but the efl_part wrapper should. It rely on efl_noref to properly destroy the object. Binding can control the lifecycle of the reference the way they want by either calling the wrapper or efl_part_get directly. It also means that the ugly ___efl_auto_unref_set doesn't need to be exposed outside of EFL anymore. Differential Revision: https://phab.enlightenment.org/D6098
2018-05-19efl: Add missing event typesXavi Artigas
Summary: All events must have a type now, otherwise bindings don't know how to handle the event_info field. Most of the missing event types were actually "void" (no event_info present). Some struct definitions had to be moved to eo instead of h files, so they are available to bindings. Some have not, and are marked with FIXME. Some namespaces have been fixed (like Efl_Event_Cb -> Efl.Event_Cb). In general, there are hundreds of changed files, but mostly to add a type which was not present before, so there's no harm done. Also, A lot of FIXMEs have been added which should be, like, fixed. For example, some events can send different types of event_info, which is very inconvenient (and error prone). Test Plan: make with c# bindings works, make check and make examples work too. Reviewers: cedric, q66, lauromoura Subscribers: zmike Tags: #efl Differential Revision: https://phab.enlightenment.org/D6169
2018-04-24Efl.Ui.Layout.Object (from Efl.Ui.Layout)Xavi Artigas
Ref https://phab.enlightenment.org/T6847 Reviewed-by: Cedric Bail <cedric@osg.samsung.com>
2018-04-24Efl.Access.Object (from Efl.Access)Xavi Artigas
Ref https://phab.enlightenment.org/T6847 Reviewed-by: Cedric Bail <cedric@osg.samsung.com>
2018-04-16elm_menu, toolbar, ctxpopup : remove unnecesary interface efl_ui_item and ↵SangHyeon Lee
efl_ui_menu Summary: Legacy menu toolbar and ctxpopup are not new efl interface widget, but it have efl interfaces, efl_ui_item and efl_ui_menu. if we plan to implement this two, it should be a class not a interface, so I remove it on legacy widget. Subscribers: cedric Differential Revision: https://phab.enlightenment.org/D5939 Reviewed-by: Cedric BAIL <cedric@osg.samsung.com>
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: https://phab.enlightenment.org/D5748
2018-01-08widget: rename elm widget to Efl.Ui.Widget.Amitesh Singh
2017-11-16elm: Rename elm_interface_atspi_widget_action mixinLukasz Stanislawski
Reviewers: jpeg Subscribers: jenkins, cedric, jpeg Differential Revision: https://phab.enlightenment.org/D5400
2017-11-15CtxPopup: Add implementation for getting focused itemGodly T.Alias
Summary: Adding the focused_item_get implementation for ctxpopup widget for getting the focused item Signed-off-by: Godly T.Alias <godlytalias@yahoo.co.in> Test Plan: elm_object_focused_item_get Reviewers: cedric, raster, prince.dubey, shilpasingh, jpeg Reviewed By: shilpasingh Subscribers: Jaehyun_Cho, Blackmole, jpeg, rajeshps, shilpasingh Differential Revision: https://phab.enlightenment.org/D5474
2017-10-19elm: rename Elm_Interface_Atspi_Accessible interfaceLukasz Stanislawski
Subscribers: cedric, jpeg Differential Revision: https://phab.enlightenment.org/D5341
2017-10-10elm: introduce efl_ui_focus_layerMarcel Hollerbach
what it does is described in the mixin this commit refactors inwin hover popup ctxpopup to use that behaviour. Since it should do exactly that.
2017-09-26elm: Introduce interface Efl.Ui.TranslatableJean-Philippe Andre
This will be used to replace the part translation API in Elm.Widget. It should work for both parts and non-parts (ie. the main text of a button, for instance). For now I'm taking the following approach: - All efl_text_set/get strings are untranslatable, i.e. get() returns the visible string, set replaces and can not be translated. - translatable_text_set/get needs to be used to enable automatic translation, which in turns calls efl_text_set to modify the visible string. Thus, translatable applications will have to use efl_ui_translatable_text_set a lot more than efl_text_set, unless they translate strings application-side. Note that some other frameworks take a simpler approach equivalent to calling efl_text_set() with an already translated text. This prevents runtime language changes of the application, unless the application handles them specifically.
2017-09-18efl: Introduce Eina.Rect and switch EO APIs to itJean-Philippe Andre
It's a complex struct but defined in EO as a simple struct. ABI-wise it's equivalent to Eina_Rectangle. Some macros that use Eina_Rectangle also work on Eina_Rect out of the box, most of the code dealing with x,y,w,h will require no modifications either. But Eina_Rect provides direct access to a size or position 2d component, as well as the usual x,y,w,h. The field "rect" is provided as a convenience for code dealing with both Eina_Rectangle and Eina_Rect. We may or may not require it. Note: Size2D could use unsigned values but I have spotted a few places in the code that actually use -1 to indicate invalid size (as opposed to 0x0). @feature
2017-09-13evas: Use Eina_Rectangle internallyJean-Philippe Andre
Instead of Evas_Coord_Rectangle which is exactly the same thing but with a different name and typedefs.
2017-08-29widget: Rename hook "disable" (EO)Jean-Philippe Andre
Renamed to on_disabled_update. Also passed in the new state of disabled. It's more convenient this way, than having the subclasses call disabled_get. Also simplify some code... Ref T5363
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-08-10ctxpopup: Remove use of Orientation API (EO)Jean-Philippe Andre
ctxpopup belongs to legacy, some work is ongoing to provide a cleaner EO based API for popups, etc... See T5326 Revert "ctxpopup: implement Efl.Orientation interface functions" This reverts commit 736fb9d4980a7dee83ca0721d8b9b58c6c12a39d. Ref T5870
2017-08-10elm_ctxpopup: Add APIs to insert before/after item to a ctxpopup object.JEONGHYUN YUN
Summary: There were only 2 APIs (item_append, item_prepend) for ctxpopup item add. Added more item add APIs (item_insert_before and item_insert_after) for convenience. Test Plan: 1. launch elementary_test - ctxpopup 2. click Ctxpopup with callback function sample 3. check whether there are 3 items on ctxpopup Reviewers: woohyun, Jaehyun, jpeg, cedric Reviewed By: jpeg Subscribers: cedric, jpeg Differential Revision: https://phab.enlightenment.org/D5004
2017-08-08elm: Rename elm_layout to Efl.Ui.LayoutJean-Philippe Andre
Some names have not been changed, hopefully making a distinction between legacy APIs and internal code (elm_layout_blah) and valid EO usages. This means many internal functions are still elm_layout_ as their sole purpose is to support the legacy API. Ref T5315
2017-08-08elm: Move elm_layout_sizing_eval to legacyJean-Philippe Andre
elm_layout_sizing_eval() marks an object as requiring recalc. Unfortunately, it's been massively abused by various widgets into actually doing the calc, or the min calc. So we end up with one API that has 3 different definitions depending on the widget type: 1. Mark as requiring recalc (correct, respects doc, elm_layout) 2. Calculate min size and other size hints 3. Actually do some geometry modification I believe we need to clarify these 3 requirements into 3 very clear and specific APIs in elementary. Right now we have similar functions in evas for 1 (evas_object_smart_changed) and 3 (smart_calculate). But their exact definition also isn't necessarily what we want for elementary. Another clear problem is that layout_eval does not do any calculation (in theory), so the "eval" word is a bit of a stretch here. Once we're sure about the exact API we want, we can add this back to EO and make it work across our EO widgets. For now let's just keep the legacy API, and its EO overrides, as is. Ref T5315
2017-08-04layout: Remove sub_object_add_enableJean-Philippe Andre
Same as the previous patch. This was an ugly hack. Use another one instead. Ref T5315
2017-05-19evas/elm: Make group_add/group_del internal functionsJean-Philippe Andre
This hides those two legacy functions from the EO API.
2017-01-11eolian: enforce specification of both get and set in prop implsDaniel Kolesa
Now you can't use the same syntax as you would for a method to implement a property as whole, instead you need to specify the getter and/or setter explicitly. This is to allow parent classes to expand their properties without altering behavior of the child classes.
2017-01-03Elm.Widget: rename "event.*" methods to solve name conflictJee-Yong Um
Summary: Elm.Widget.event_callback_add conflicts with Efl.Object.event_callback_add. To solve this problem, "widget_" prefix is added to methods starting with "event". Reviewers: cedric, jpeg Differential Revision: https://phab.enlightenment.org/D4521
2016-12-27elm: use new property implement syntax everywhereDaniel Kolesa
2016-11-30Menu,Item Interface: Common interface for menu, toolbar and ctxpopupAmitesh Singh
Summary: efl_ui_menu interface provides common functions of menu, toolbar and ctxpopup. efl_ui_item interface provides common functions of menu_item, toolbar_item and ctxpopup_item. Also implemented some missing functions like selected_item set/get in ctxpopup. efl_ui_item interface should be used for other widget items as well. Test Plan: elementary_test Reviewers: jpeg, felipealmeida, raster, SanghyeonLee, cedric, yashu21985 Subscribers: bu5hm4n Differential Revision: https://phab.enlightenment.org/D3897
2016-11-21docs: elm_ctxpopup: fill gaps in elm_ctxpopup 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-31eolian: utilize the new builtin string type across eo filesDaniel Kolesa
2016-05-26Efl: Remove part name in Efl.Container (use Efl.Part)Jean-Philippe Andre
This touches Edje and also Elementary where part names are used. This commit blew up in size since now all content part APIs (get, set, unset) require to use Efl.Part instead. This is a big refactoring commit, but no logic should have been changed. Fingers crossed.
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-12Elm interface atspi: Fix namespacing to use . and not _.Tom Hacohen
2016-05-12Elm items: Fix namespacing to use . and not _.Tom Hacohen
2016-05-12Evas object smart: Fix namespace to use . and not _.Tom Hacohen
2016-04-26Efl: Introduce Efl.Container and unify APIsJean-Philippe Andre
This removes Efl.Pack_Named which had a terrible name, removes Elm.Container which should have been renamed Efl.Ui.Container anyway, and introduces an interface Efl.Container instead. The hierarchy tree is now changed as objects don't inherit from Efl.Container (it's an interface, not a regular class) but only implement it. Obviously it is very easy to reintroduce an Efl.Ui.Container parent class if we need it, but I guess it should have some actual logic. It's basically part of what Elm.Widget already does. Some function names have been modified to look better in C with the efl_content prefix. @feature
2016-04-18Elm widget: rename parent to widget_parent and mark as protected.Tom Hacohen
This removes the conflicts between the different parents and also indicates that this is to be used internally by widgets and should not be confused with the normal user visible parent. It is an internal attribute that should not be used by people not implementing widgets. Marking it as protected signifies it as such.