On Mon, Dec 20, 2010 at 2:28 AM, Daniel Juyung Seo <seojuyu...@gmail.com> wrote:
> Hello,
>
> For these two APIs,
> 'elm_box_pack_start / evas_object_box_prepend', 'elm_box_pack_end /
> evas_object_box_append',
> it looks like evas_object_box APIs are more general compared to other
> elementary API names.
> Why elm_box is so different?
> I have the same question with Myungjae Lee.
elm_box is basically e_box, which is way older... and also older than
size hints.
discussing with other developers it was agreed that we should
introduce size hints and common box behavior with customizable layout
functions to be shared by evas, edje and elementary. So it was
developed.
unfortunately as elm_box pre-dates size hints its behavior did not
match there and thus we left it for backward compatibility. the plan
was to remove it one day.
I can't compare the code, but feel free to fix the flow mode if you
think it's wrong. If you think we need another mode, then add it to
Evas itself, just document used size hints. Adding it to elementary
is bad as it may generate more fragmentation and eventual copy&paste
to use it elsewhere.
also, see the documentation about flow mode and used size-hints,
maybe you can do what you need with it.
--
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: barbi...@gmail.com
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
