> Another wrinkle is that we'd like to create a core library that is
> only loosely tied to any specific underlying display system. We're
> still in the process of abstracting the evas and edje specifics into
> engines, and I don't want to add too many more direct dependencies.
> This could be don
On Feb 15, 2008, at 8:36 PM, Nathan Ingersoll wrote:
>
>
> Yeah, unfortunately my participation at SCALE fell through. I'm not
> sure if raster made it, but it would be good to hear a trip report if
> he did. :-)
http://arstechnica.com/news.ars/post/20080211-the-enlightened-future-of-openmoko-l
On Fri, Feb 15, 2008 at 10:05 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Good questions.. Don't know. A buffer canvas would be nice to
> have for several reasons, but as you mention it may not be the best
> way to realize a canvas widget for other reasons.. it also depends on
>
> > 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
On Fri, Feb 15, 2008 at 3:50 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 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
>
> > Until a more generic solution presents itself, why not have
> > a separate Ewl_Evas lib, with say a 'ewl_evas' widget, that has
> > a function to get an underlying evas..?
>
> Getting to the evas is not a problem:
>
> embed = ewl_embed_widget_find(some_widget_on_my_evas);
> evas = embed-
On Fri, Feb 15, 2008 at 2:01 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> That seems to me like it might be a BIG problem for any
> sufficiently flexible use of ewl and evas. :(
>
> Until a more generic solution presents itself, why not have
> a separate Ewl_Evas lib, with
> > Does ewl have something like a canvas widget that one can add
> > evas objects to?
>
> Not atm.
That seems to me like it might be a BIG problem for any
sufficiently flexible use of ewl and evas. :(
Until a more generic solution presents itself, why not have
a separate Ewl_Ev
On Fri, Feb 15, 2008 at 12:18 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Nathan wrote:
>
> > The answer is yes and no. You can certainly do this simply by
> > mapping the theme for a widget to your Edje. The problem is that
>
> Is "mapping the theme for a widget to your
Nathan wrote:
> The answer is yes and no. You can certainly do this simply by
> mapping the theme for a widget to your Edje. The problem is that
Is "mapping the theme for a widget to your Edje" a standard,
well-known thing to do in ewl? Is that the same as using one's own
edj fil
The answer is yes and no. You can certainly do this simply by mapping
the theme for a widget to your Edje. The problem is that any events
will automatically have the source set as "EWL" instead of the clicked
part. The problem is that we do dispatching to the widget inside of
EWL, and w/o an API to
11 matches
Mail list logo
