@YOhoho
Thank you for the patch and updates! It is nice :)

@bu5hm4n
I mean that your patch is good. There is no problem on that.
But I was not sure if it was sufficient to close this task.
(But now I think that this task is to evaluate the main task so it is ok this task is closed)

@segfaultxavi
Thank you for searching! :)

@lauromoura
Thank you for the patch :)

@YOhoho
Could you please check the comments?

@bu5hm4n
Regarding resolving this task with 3ddd577fb0c67b1867c6664af42a89652134c73a, I want to discuss about it.
I understand that the patch forbid a regular class to inherit from a new regular class from mixin.

@lauromoura
What do you think about @segfaultxavi 's opinion?

Thank you for your comment :)
I updated commit message.

Could you move the definition of struct Efl.Ui.Relative_Params to efl_ui_relative.eo file?

Thank you for this patch :) It looks fine to me.

update examples to fix build error

Thank you for sharing the lua code :)

Could you share print_hierarchy.lua? :)

Thank you :)

If we only talk about namespaces under "Efl.", then it would be as follows.
(I only write namespaces except class, abstract, interface, mixin name itself)

Thank you for reply :)

Thank you :) No one noticed the existence of these variables!

Thank you for update :)

I think that the added program signal is duplicated.

The reason why I want to modify theme is because there is no rule prev_btn and next_btn should be inside the title area.

How about changing the state of "elm.swallow.prev_btn" and "elm.swallow.next_btn" in naviframe.edc instead of code change?

"EFL_GFX_SIZE_HINT_FILL" with "hint_align_set" still exists in code.

Could you let me know the progress of this task if it is done?

As far as I see, the main purpose of this task is to implement Efl.Gfx.Image_Load_Controller.load_state { get; } in Efl.Canvas.Image.

This task is done by the patch f85325d924d93e84ffee08b7bffd39d33347998f

Could you tell us what the current status of this task is?

are you going to submit your patch to master branch?

This new class name is Efl.Access_Event_Handler.

We need to decide which name is categorized as a namespace and which is not.

please remove the typo

Class name cannot be used as a namespace.

Oh! Really?
I got reported that edje_cc which is compiled on Ubuntu 16.04 does not work on Ubuntu 18.04 since Ubuntu 18.04 does not support libpng12.

Could you give some comments on this patch? :)

Thank you for clear summarize.

How about we use one group for scr_edje and panel_edje? (i.e. efl/panel)

rebase based on Efl.Ui.Layout class

Yes, you are right. It is not easy to apply composite object to all mixin cases automatically. So it is a problem..

I understand your point.
I think that you mean that Efl.Access.Object should be changed to a regular class and all elementary widget classes inherit from Efl.Access.Object to inherit from Efl.Object.

Thank you for review :)

I agree with you :)

could you share the current status of supporting widget style in constructor in C#?

Is there any suggestion to rename class "Config" which mainly supports Init() and Shutdown()?
(e.g. efl.ui.Config, eina.Config, ...)

rebase

d4526f44b8c20010061c42a87ac0496796311afb replaces this patch and it has been submitted to master.

d4526f44b8c20010061c42a87ac0496796311afb replaces this patch and it has been submitted to master.

d4526f44b8c20010061c42a87ac0496796311afb replaces this patch and it has been submitted to master.

d4526f44b8c20010061c42a87ac0496796311afb replaces this patch and it has been submitted to master.

Based on @herb 's comment, this patch is abandoned.

Instead of this patch, 743e0468e910a4f0928bcbf8f7547203108f0d78 has been submitted to master.

Instead of this patch 743e0468e910a4f0928bcbf8f7547203108f0d78 has been submitted to master.

How is it possible that elementary_test already had a test for this functionality if you are adding it in this patch?

Modified the enum name from "failed" to "fail" to be a noun like "success".
(from EFL_UI_THEME_APPLY_RESULT_FAILED to EFL_UI_THEME_APPLY_RESULT_FAIL)

Thank you for reviewing! :)

I left a trivial suggestion which changes the variable names of callback and data.

update comments

@CHAN
I think we can make gesture cs files after we verify that gesture interface works on C#.

Please give some comments or feedback on this patch :)

Thank you for the feedbacks :)
Then, let's think about handling events by "Efl.App" when it becomes necessary.

@segfaultxavi

regarding your first point, do you want the app to be able to intercepting any event before it is processed by anybody else?

Yes. In android, "activity" handles events before "view" handles it.
The android's "activity" is similar to EFL's "Efl.App" so I wanted to provide a way to let "Efl.App" handles events like the android's "activity" does.

updated as @segfaultxavi commented

Thank you :)