On Sat, 12 Apr 2008 03:15:46 -0400 Jose Gonzalez <[EMAIL PROTECTED]> babbled:
>
> >> What do you do if such a native surface is set and one asks
> >> for the argb data? What do you do about users setting native surfaces
> >> which don't match with the display targets somehow (differing x
>
>> What do you do if such a native surface is set and one asks
>> for the argb data? What do you do about users setting native surfaces
>> which don't match with the display targets somehow (differing x
>> resources for example).
>> I'd say - restrict native surface api to only have a
On Sat, 12 Apr 2008 01:53:16 -0400 Jose Gonzalez <[EMAIL PROTECTED]> babbled:
>Carsten wrote:
>
> >>But what I was curious about was what exactly you had in mind
> >> with your:
> >>
> >> typedef struct _Evas_Native_Surface Evas_Native_Surface;
> >> /**< A generic datatype for engine spe
Carsten wrote:
>> But what I was curious about was what exactly you had in mind
>> with your:
>>
>> typedef struct _Evas_Native_Surface Evas_Native_Surface;
>> /**< A generic datatype for engine specific
>> native surface information */
>>
>> EAPI void
>> evas_object_image_native_sur
On Mon, 10 Mar 2008 06:31:51 GMT "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
babbled:
>
> > > I have a question for you on this though: I imagined having
> > > 'native surface' image obj api given in each of the engine headers,
> > > but you added a generic evas api for it.. What exactly do you have
Carsten Haitzler (The Rasterman) wrote:
>
>> Either way, this would allow for engine-specific extensions
>> for evas.. wrapping things adequately would allow for things like
>> say an "evas3D" lib if really desired.
>
> sure. 3d INSIDE a "3d object" i can deal with in evas :)
>
Exactly. W
> > I have a question for you on this though: I imagined having
> > 'native surface' image obj api given in each of the engine headers,
> > but you added a generic evas api for it.. What exactly do you have
> > in mind here? eg. say with gl-textures?
>
> literally evas exposing the engine drawing
http://arstechnica.com/news.ars/post/20080303-creating-rich-internet-applications-on-linux-with-webkit.html
Hmm
On Sun, Mar 9, 2008 at 6:23 PM, The Rasterman Carsten Haitzler <
[EMAIL PROTECTED]> wrote:
> On Thu, 6 Mar 2008 06:12:55 GMT "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> babbled:
>
>
On Thu, 6 Mar 2008 06:12:55 GMT "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> babbled:
>
> Carsten wrote:
>
> > ... what would be the right way would be to allow new extended
> > objects (smart objects) to set rendering calls - the same way
> > evas internal objects do, and then do their own re
Carsten wrote:
> ... what would be the right way would be to allow new extended
> objects (smart objects) to set rendering calls - the same way
> evas internal objects do, and then do their own rendering.
> breaking this out to a nice public api would be really nice and
> allow for objec
On Wed, Mar 5, 2008 at 12:26 AM, The Rasterman Carsten Haitzler
<[EMAIL PROTECTED]> wrote:
> On Mon, 25 Feb 2008 23:50:41 -0300 "Gustavo Sverzut Barbieri"
> <[EMAIL PROTECTED]> babbled:
>
>
>
> > On Mon, Feb 25, 2008 at 9:09 PM, raoul <[EMAIL PROTECTED]> wrote:
> > > Hi there,
> > >
> > > I t
On Mon, 25 Feb 2008 23:50:41 -0300 "Gustavo Sverzut Barbieri"
<[EMAIL PROTECTED]> babbled:
> On Mon, Feb 25, 2008 at 9:09 PM, raoul <[EMAIL PROTECTED]> wrote:
> > Hi there,
> >
> > I think there is a great stuff missing in efls, it's a web rendering
> > engine. The main purpose would be to have a
Le mardi 26 février 2008, vous avez écrit :
> On Mon, Feb 25, 2008 at 9:09 PM, raoul <[EMAIL PROTECTED]> wrote:
> > Hi there,
> >
> > I think there is a great stuff missing in efls, it's a web rendering
> > engine. The main purpose would be to have a full-efl based web browser.
> > But also have s
> As for implementation details, smart object is not the best option,
> actually using Evas as WebKit backend is not the best option around.
> ...
> ...
> So the best option is to draw to some buffer and use this as image
> data, then take care of event passing to this webkit engine. Using
> ...
On Mon, Feb 25, 2008 at 9:09 PM, raoul <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I think there is a great stuff missing in efls, it's a web rendering engine.
> The main purpose would be to have a full-efl based web browser. But also have
> some web rendering inside Evas/Edje based apps. This co
Hi there,
I think there is a great stuff missing in efls, it's a web rendering engine.
The main purpose would be to have a full-efl based web browser. But also have
some web rendering inside Evas/Edje based apps. This could really be awsome.
I started to search how to have such capability and t
16 matches
Mail list logo
