On Thu, 6 Mar 2008 06:17:06 GMT "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> babbled:
> > Gustavo wrote: > > > We were discussing about this idea at IRC and the summary is > > written at: > > > > http://wiki.enlightenment.org/index.php/Evas_Object_Size_Hints > > > > Idea is to move this common requirement to Evas_Object so it can be > > shared by toolkits, Edje and even the layout smart objects I plan > > to add someday in future. Adding this is pretty straightforward and > > I should do it soon, next moving Edje to use it. > > > > Any comments on that? Requirements we failed to notice? Better > > functions/types names? > > They seem fine to me - it's a good idea, even if some objects > may want to be stubborn about this stuff sometimes. One question > though: is there such a thing as a 'natural size' notion used by > people? "size_request" would cover that. given an input size - what would it naturally want given that input. aspect is good too. min and max are directly useful for calculating container extents and more. edje works around this at the moment - and this would just make edje's min and max calls direct evas wrappers. this also incidentally would help ewl and etk merge some of this in and not build their own things like edje did. any comments from ewl/etk land are absolutely welcome here. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
