Re: [E-devel] Ewl and Edje

[Nathan I. <nin...@gm...>]

On Fri, Feb 15, 2008 at 3:50 PM, jos...@ju... <jos...@ju...> wrote:
>
>         Umm... It still sems to me like you'd want some kind of canvas
>  widget to which one could add arbitrary evas objects to, directly or
>  indirectly (I believe that etk has something like that), in order to
>  have a more flexible "evas objs in a ewl app" system, and just feed ewl
>  events on that canvas widget to the underlying evas..?

The idea of a canvas has been under consideration for a while, but has
been lower priority than other things that still need work.

Through what mechanism are you proposing we build the canvas widget?
It could be a buffer evas as we already have a pretty good wrapper
around that, but the levels of indirection are additional overhead
(maybe a reasonable amount). That would solve the problem of feeding
events since they could go directly through the global evas event API.
I'd prefer to have a sub-canvas abstraction around the windows
existing evas, which we can clip to the region of the canvas widget.

>         But as far as the particular events issue you bring up, maybe
>  you could write up a preliminary evas patch with the changes/additions
>  you feel are needed.. and battle it out with raster if need be. :)

I'm not sure if you've noticed my commit level lately, but it hasn't
been what I would call "active". I'll look at this if have a chunk of
time to commit to it, but I'm hoping someone with an itch to scratch
will beat me to it.