> You can do this now with Ewl. The only problem being, everything
> is absolute coordinates which is a bit strange for this kind of
> widget. If you want to do this, inherit ewl_box, remove configure
> event, add your own configure and use ewl_object_place to put the
> widgets where you want them. (Or, alternatively, I think this is
> what ewl_overlay does already but I haven't used the overlay).
However you have it (though rel coords would seem best),
if you really want ewl to be a flexible tool for building artistic,
rich apps, then you'll want a natural way to arbitrarily position
child *widgets* - not just evas objects.. and to allow for custom
kinds of child widget layout mechanisms.
One should not have to 'go-out' of the toolkit based widget
framework (and into evas say) in order to develop 'rich' apps.
It's not enough to have such abilities only with evas objects,
or that you can do this and that and then... It has to be a basic
feature of the toolkit itself.
But those are just my thoughts on it, others might see
things differently.
-------------------------------------------------------------------------
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
