andres schrieb:
Hello, in order to implement the layout objects for my SoC project I need to
know if it would be possible to add size hints to Evas Objects.
I attached a patch file with the required changes. I tried following the
implementation of size hints since its a similar concept but
Gustavo Sverzut Barbieri schrieb:
Just to make clear: what goes into Evas_Object is the hints. They
could be represented as allocated structs managed with
evas_object_data_*(), but since they're so common we could 1) make it
more standard, helping integration and
I don't see where they are so
On Fri, May 2, 2008 at 11:23 AM, Peter Wehrfritz [EMAIL PROTECTED] wrote:
Gustavo Sverzut Barbieri schrieb:
Just to make clear: what goes into Evas_Object is the hints. They
could be represented as allocated structs managed with
evas_object_data_*(), but since they're so common we could
Gustavo Sverzut Barbieri schrieb:
On Fri, May 2, 2008 at 11:23 AM, Peter Wehrfritz [EMAIL PROTECTED] wrote:
You can use a hash or a tree instead.
sure, but then you waste almost a kb on the bucket allocation. it's a
trade off, no free lunch.
(btw, yes, evas speed up this by
Hello, in order to implement the layout objects for my SoC project I need to
know if it would be possible to add size hints to Evas Objects.
I attached a patch file with the required changes. I tried following the
implementation of size hints since its a similar concept but I can't compile
the
On Wed, Apr 30, 2008 at 11:40 AM, andres [EMAIL PROTECTED] wrote:
Hello, in order to implement the layout objects for my SoC project I need to
know if it would be possible to add size hints to Evas Objects.
I attached a patch file with the required changes. I tried following the
As we discussed at IRC, probably this policies can be handled on top
of currently existing Size_Hints and no other members should be added
to the struct.
Also agreed at IRC is that most difficult part is to get all the
requirements written, we should start with V/HBox as they're useful
and
On Wed, Apr 30, 2008 at 7:59 PM, Jose Gonzalez [EMAIL PROTECTED] wrote:
As we discussed at IRC, probably this policies can be handled on top
of currently existing Size_Hints and no other members should be added
to the struct.
Also agreed at IRC is that most difficult part is to
Gustavo wrote:
One of the things I see going on with this kind of thing is
an attempt to put more and more 'widgetry/layout' kinds of needs
into evas objects in a generic way. The 'problem' with some of this
is that evas objects don't have any real notion of 'inheritance' or
