aboutsummaryrefslogtreecommitdiffstats
path: root/src/lib/edje/edje_object.eo (follow)
Commit message (Collapse)AuthorAgeFilesLines
* edje: rename Edje.Object to Efl.Canvas.LayoutAmitesh Singh2017-12-061-142/+0
|
* edje: rename intf Efl.Canvas.Layout_Group to Efl.Layout.GroupAmitesh Singh2017-12-051-4/+4
|
* edje: rename intf Efl.Canvas.Layout_Calc to Efl.Layout.CalcAmitesh Singh2017-12-051-7/+7
|
* edje: rename intf Efl.Canvas.Layout.Signal to Efl.Layout.SignalAmitesh Singh2017-12-051-6/+6
|
* efl.gfx: move scale{} from efl.ui.base to efl.gfxAmitesh Singh2017-12-041-1/+1
|
* Efl.Ui.Base: remove base_scale.get{} from interface.Amitesh Singh2017-11-301-1/+0
| | | | base_scale for edje would be legacy now.
* edje: Move perspective to legacyJean-Philippe Andre2017-11-301-30/+0
| | | | | | | | | | | | Note: Edje.Perspective is not bound to EO, and this is the only reason why I'm moving this to legacy only. Marking as beta would mean the legacy APIs would not be generated, so that would have almost the same effect as moving to legacy. It would be nice to actually support this in EO, though this seems like a rarely used feature. Ref T5315
* edje: Move text_change_cb to legacy onlyJean-Philippe Andre2017-11-291-11/+0
| | | | | | | | | | | This should probably be replaced by a well defined signal. Note: If edje sends signals on swallow/unswallow and text set/unset we could simplify some of the elementary code, eg. for button's icon handling. The theme should be handling the padding automatically, it's not the elementary widget's role Ref T5315
* edje: Move "preload" to legacy onlyJean-Philippe Andre2017-11-291-20/+0
| | | | | | | | | EO file API is still in flux, especially wrt. async loading. Let's just keep this in legacy for now. A few more patches and Edje.Object will reach its final form. Ref T5315
* edje: Implement Efl.File.load_errorJean-Philippe Andre2017-11-291-16/+1
| | | | Don't create a new function with the same name, it's absurd.
* edje: add event for inform about circular dependencyVyacheslav Reutskiy2017-11-131-0/+1
| | | | | | | This commit add the event "circular,dependency" for edje object. Given event is called when edje found the circular dependency between parts in object. This event will be usefull and informative paired with Edje_Edit API.
* Efl: add class interfaces (color/text/size)Jee-Yong Um2017-11-081-216/+10
| | | | | | | | | | Summary: implement Efl.Gfx.Class interface Reviewers: jpeg, cedric Subscribers: taxi2se, herdsman Differential Revision: https://phab.enlightenment.org/D4403
* eo files: convert various to use @crefDaniel Kolesa2017-11-021-1/+1
|
* edje_object: Mark access_part_iterate as @betaJean-Philippe Andre2017-10-121-1/+1
| | | | | | | This may be internal... Not sure we need this exposed outside of the ATSPI layer, really. Marking as beta for now. Ref T5315
* edje: remove duplicated code and rely on Efl.File { set; get; } mixin.Cedric Bail2017-10-041-2/+0
|
* edje: Add part_type_get APIJean-Philippe Andre2017-09-211-20/+1
| | | | | | | | | | | | For now I made this EO-only but this definitely could be expose in legacy API as well. This simply gives exact information about the type of part, after doing a recursive search. Edit Edit doesn't do a recursive search, only a direct one, which can yield invalid results (eg. RECT or NONE instead of TEXT in case of "elm.units.max" for a slider). @feature
* Edje: move selection-related part_text API to legacyDaniel Hirt2017-09-201-64/+0
|
* Edje: move IMF-related part_text API to legacyDaniel Hirt2017-09-201-292/+0
|
* edje: Merge calc_size_min_restricted & calc_size_minJean-Philippe Andre2017-09-181-1/+0
| | | | | | | calc_size_min was just a helper passing 0,0 to the restricted form. Let's not duplicate APIs in EO and use an optional argument instead. Bindings should be nicer and C could use a macro if it's too cumbersome to pass in 0,0.
* efl interfaces: convert to new ownershipDaniel Kolesa2017-09-151-1/+1
|
* evas/edje/elm: Remove all uses of clipped groupsJean-Philippe Andre2017-09-131-1/+1
| | | | | This removes the uses of the *EO* class, obviously not the use of the clipped smart objects.
* edje: implement edje.player interface functionsAmitesh Singh2017-08-041-43/+6
| | | | fixes T5560
* edje: Move size_min/max and data to an interfaceJean-Philippe Andre2017-08-041-99/+4
| | | | | | | | | The new interface is: Efl.Canvas.Layout_Group I'm not fan of the name. Ref T5315
* edje: Move signal APIs to an interfaceJean-Philippe Andre2017-08-041-149/+7
| | | | | | This interface will be used by elm_layout as well. Ref T5315
* edje: Split off calc APIs to an interface (EO)Jean-Philippe Andre2017-08-041-128/+8
| | | | | | | | | | | | Those APIs can then be used by Elm.Layout, hopefully simplifying the API. I wonder if the APIs should be prefixed "calc_" (as is) or "layout_calc_". The extra "layout_" prefix would make it common with other layout APIs (eg. signals, data, size min/max, ...). Ref T5315
* eo debug name: Use strbuf instead of slstrJean-Philippe Andre2017-08-041-1/+1
| | | | | This should be a little bit more efficient, even if more "risky" in terms of leaks. The final API still looks exactly the same.
* evas/edje/elm: Override debug_name in core classesJean-Philippe Andre2017-08-041-0/+1
| | | | | | | | | | | | This is really only a demonstration of what kind of information we can print with efl_debug_name_get(). Hopefully this can help debugging with printf/ERR logs and even help with live debugging inside gdb. This shouldn't be used for other purposes than debugging, as the exact string format is not defined. @feature
* elm_entry: Add prediction hint APIJihoon Kim2017-06-261-0/+13
| | | | | | prediction hint can be used to provide an intelligent reply suggestion. @feature
* edje: Move base_scale to Efl.Ui.BaseJean-Philippe Andre2017-06-121-15/+1
| | | | | | | | | This API is used by elementary widgets like: edje_object_base_scale_get(elm_layout_edje_get(ly)); This means elm_layout in fact should also expose it directly. Ref T5315
* Canvas layout: port 'part_text' to Efl.Text.*Daniel Hirt2017-06-121-482/+0
| | | | | | | | | | | | | | | | | | | | | | | The following API is now supported with efl_part: - Efl.Text.text { set; get; } - Efl.Text.Cursor.cursor { get; } - Efl.Text.Cursor.cursor_paragraph_first; - Efl.Text.Cursor.cursor_paragraph_last; - Efl.Text.Cursor.cursor_position { set; get; } - Efl.Text.Cursor.cursor_coord_set; - Efl.Text.Cursor.cursor_line_char_first; - Efl.Text.Cursor.cursor_line_char_last; - Efl.Text.Cursor.cursor_char_next; - Efl.Text.Cursor.cursor_char_prev; - Efl.Text.Cursor.cursor_line_jump_by; - Efl.Text.Cursor.cursor_copy; - Efl.Text.Cursor.cursor_content { get; } - Efl.Text.Cursor.cursor_geometry { get; } - Efl.Text.Cursor.cursor_text_insert; Many of the 'part_text' functionality was moved to legacy, too. See the edje_object.eo to see which ones are still supported.
* Canvas layout: port part_text to efl_partDaniel Hirt2017-06-121-19/+0
| | | | | | | | | | | | You now use the following: efl_text_set(efl_part(edje_obj, "part"), "text"); const char *text = efl_text_get(efl_part(edje_obj, "part")); The former method of edje_object_part_text_set/get is now legacy. Also, adjusted 'tests/emotion/emotion_test_main-eo.c' with this change.
* edje: Move some functions to Efl.Ui.Base (EO)Jean-Philippe Andre2017-05-311-66/+4
| | | | | | | | | | | | | | | | | This introduces the new interface Efl.Ui.Base, intended to share some APIs between Edje and Elm: - mirrored (rtl) - language - scale base_scale remains in Edje.Object for now. I don't think it applies to generic widgets. The new interface uses eo prefix "efl_ui". It could be renamed as Efl.Ui (no Base), or anything else. As always, I'm open to propositions! Ref T5315
* edje: Reshuffle a bit edje_object.eoJean-Philippe Andre2017-05-311-158/+152
| | | | | | | | | | | | This changes a few method names: - freeze -> calc_freeze - thaw -> calc_thaw - update_hints -> calc_update_hints Otherwise this is mostly about reshuffling the EO file itself and changing documentation. Ref T5315
* edje: Rename "data" to "group_data" for EOJean-Philippe Andre2017-05-311-23/+19
| | | | | | | | Still not happy with the name. I'm trying to avoid a name clash between other "data" elements in the object. This is the EDC group "data item". Ref T5315
* edje: Move part drag APIs to efl_partJean-Philippe Andre2017-05-311-175/+1
| | | | | | | | | This moves all part_drag APIs to legacy and implements them for EO using efl_part(). All parts now support these APIs, even if they are not draggable. Making this more fine grained would probably be much extra work for little gain. This creates a new interface Efl.Ui.Drag.
* edje: Improve reference doc for part drag APIsJean-Philippe Andre2017-05-311-92/+106
|
* edje: Remove external_object_get from EOJean-Philippe Andre2017-05-301-21/+0
| | | | | This will be replaced by a trick: composition on the part object itself!
* edje: Remove part_external_content_get from EOJean-Philippe Andre2017-05-301-13/+0
| | | | | | | I couldn't find a use of this API. This looks like it returns an object inside a part inside an external (so, inside an edje). Kept as legacy only.
* edje: Move external_param_set to a efl_part APIJean-Philippe Andre2017-05-301-73/+0
| | | | | | | | | | | | This adds a new class: Efl.Canvas.Layout.External. I hate this long name... This class represents an external part, and for now only supports param_set/get as well as param_type_get. For now param_type_get() still returns an Edje_External_Param_Type and not another more generic type. TODO: enumerate choices, return object, return content
* edje: Enhance documentation for play vs animationJean-Philippe Andre2017-05-301-30/+29
| | | | | | | I had to test in order to get an idea of what those two similar properties meant. Hopefully this is clear and not wrong. See example: edje-animations
* edje: Add recursive flag for message_signal_processJean-Philippe Andre2017-05-291-2/+10
| | | | | | | | | | | | | | | Original patch by Jinwoo Shin: If edje has multiple levels of child group, edje_object_message_signal_process cannot process message on child group. To cover that, it needs to add new API which traverses its hierarchy and process messages. @feature Signed-off-by: jinwoo.shin <jw0227.shin@samsung.com> Differential Revision: https://phab.enlightenment.org/D4914
* edje: Move part_state_get to efl_partJean-Philippe Andre2017-05-291-14/+0
|
* edje: Implement part_geometry_get with Efl.PartJean-Philippe Andre2017-05-291-26/+0
| | | | | | | | This refactors even more the edje part eo internals. But now common part APIs can easily be implemented in edje_part.c The API now looks like: efl_gfx_geometry_get(efl_part(edje, "part"), &x, &y, &w, &h)
* edje: Remove part_object_get from EOJean-Philippe Andre2017-05-291-25/+0
| | | | | | | | | | | Ooooh. This one might be controversial, as some apps definitely use the function. But it is so easily abused. For our EO API we are trying to not expose any internal object, as this prevents us from making changes to the internal behaviour and structure. All the features that this API provided should be limited to read-only access to the internal object. In order to replace this, we will have to return an Efl.Part object that implements all those APIs: geometry_get, visibility_get, etc...
* edje: Unify load error types for image and edje (EO)Jean-Philippe Andre2017-05-291-17/+9
| | | | | | | | Most of the values were the same, with edje having just a couple more error codes. Not entirely sure the prefix Efl.Image is correct for this type. Maybe just Efl.Load.Error?
* edje: Implement EO API for message_sendJean-Philippe Andre2017-05-241-9/+8
| | | | | | | | | | | | | | Since this uses generic_value (aka Eina_Value), there is an implicit type detection and conversion. I did not attempt to cover all types (namely string+int and string+float and even less sets of those) as I believe they aren't really used. Or they most likely could be replaced by multiple messages rather than a single message. Note: should we pass ptr(generic_value) instead of generic_value? The API looks a little odd in C when passing by value. @feature
* edje: Remove message_handler_set from EOJean-Philippe Andre2017-05-241-21/+2
| | | | | | | | | | | | | | | It is used to receive messages with a payload from embryo to C. This API has a function pointer, which means it would have to be manually bound, or transformed (eg. eo event). Also, prepare the change for message_send to use Eina_Value and no explicit type. This feature seems rarely used. But note that handler_set is in fact used in terminology, rage and luncher. So, if the need arises, it will have to be transformed in a proper EO way.
* evas/elm: Make group_add/group_del internal functionsJean-Philippe Andre2017-05-191-2/+0
| | | | This hides those two legacy functions from the EO API.
* evas: Remove Evas.Coord from EOJean-Philippe Andre2017-05-151-40/+38
| | | | | | | | | | 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
* evas: Remove Evas_Font_Size from EOJean-Philippe Andre2017-05-151-1/+1
| | | | Ref T5312