TODO

1. implement margin.
2. add more examples.
3. add more tests.
4. enhance documentations.
5. implement a chain dependency check.(efl_ui_relative_example02)
6. implement scale.

Class Diagram

Testcase

Interesting :D

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

I am not to sure of the name of this new class as it doesn't express in the name the fact that it is a container. Also, and it is something that I am sure @segfaultxavi will point out, it is lacking a lot of documentation :-)

In D7524#132661, @cedric wrote:

I am not to sure of the name of this new class as it doesn't express in the name the fact that it is a container. Also, and it is something that I am sure @segfaultxavi will point out, it is lacking a lot of documentation :-)

Yes, documentation is in progress. i'll enhance it after adding more testcase and examples.
BTW, i am not sure that there isn't structural holes. :|

In D7524#132938, @YOhoho wrote:

1. add elementary_test example.
2. rename to left, right, top, bottom.
3. remove register api. (when a child have relation, it is registered)
   
   I want overload relation_#direction# apis. for example,
4. relation_left_set(Eo *obj, Eo *child, Eo *target) to set only to.
5. relation_left_set(Eo *obj, Eo *child, double relative) to set only relative.
6. relation_left_set(Eo *obj, Eo *child, Eo *target, double relative) to set both to and relative.
   
   However, EO doesn't support method overloading. so there are xxx_to, xxx_relative apis.

Don't we have a way to define a default value here ? I would think that in C, if you pass NULL or 0.0, it would just work. In C# and other language, it could just use the default value. So something like :

relation_left_set(Eo *obj, Eo *child, Eo *target, double relative);

Would just work for all case.

@cedric
Agreed.

relation_left_set(Eo *obj, Eo *child, Eo *target, double relative);

Would cover all cases passing NULL.

When widget have a relation, default relation is set as

left.to = parent;
left.relative = 0.0;
right.to = parent;
right.relative = 1.0;
top.to = parent;
top.relative = 0.0;
bottom.to = parent;
bottom.relative = 1.0;

It is same to Edje.

I think its now ready to land.
I'm waiting for review.
Please check updated class diagram and testcases in my previous comment.

In D7524#131897, @YOhoho wrote:

Should we implement Efl.Pack or not to call layout,updated event?

Is there any reason why relative layout itself becomes a child?

In D7524#139233, @Jaehyun_Cho wrote:

Should we implement Efl.Pack or not to call layout,updated event?

What do you think to move 'layout,updated' to Efl.Pack_Layout?
I think that is more suitable event for Efl.Pack_Layout which have layout_update method.