--- Jason Tackaberry <[EMAIL PROTECTED]> escreveu:
> On Mon, 2004-08-09 at 18:42 -0300, Gustavo Sverzut Barbieri wrote:
> > Maybe I didn't understand you, but are you talking about
> backends...
> > gdkpixbuf and every other you talked about don't support anything
> > other
> > than X11 or maybe directfb... AFAIK, there's nothing else based on
> SDL
> > other than pygame... so we will stay with pygame as default
> backend?
>
> I am working on a canvas library that supports multiple image
> libraries
> and displays, each of which are independent of the other. This means
> you can use any supported image library for image manipulation, like
> pyimlib2, pygame, gdkpixbuf, PIL, pyimagemagick (just for examples;
> of
> course PIL isn't very good) on any supported display, like X11 (via
> pyimlib2, pygame, etc.), bmovl2, framebuffer, etc. (Strictly
> speaking
> bmovl2 isn't a display, but as far as the canvas is concerned it is.)
>
> So it is possible to use pyimlib2 for all image manipulation
> (loading,
> blending, scaling, etc.) and pygame for display. The canvas objects
> should also support dynamically changing image backends. That is, if
> it
> turns out that gdkpixbuf for both image manipulation and display is
> the
> best combination for a given situation (say for X11), when the user
> loads a movie in MPlayer and we want to offer an interface from
> within
> the movie, we'll switch to a bmovl2 canvas using a pyimlib2 imagelib
> backend, and all the objects of the old pygame canvas can be moved to
> the bmovl2 canvas without any fuss.
>
> The system can choose which image library to use with which display
> backend to give the best performance given what's available on the
> system.
>
> I hope that's not too confusing. :) Basically the canvas provides a
> layer between the application and all image operations and display
> operations.
>
> +-------------+
> | Application |
> +-------------+
> |
> +--------+
> | Canvas |
> +--------+
> / \
> +------------+ +----------+
> | Image libs | | Displays |
> +------------+ +----------+
>
> The intent of the canvas is to offer a convenient API to deal with
> displaying graphical elements and it figures out the appropriate way
> to
> talk with a particular display.
>
> Hopefully that explains it a bit better. Eventually you'll see what
> I
> mean with code. Anyway, this is what I'm working on. How this all
> ties
> in with Freevo is dischi's turf.
>
This I already know :)
What I don't know is the talk about "We can't use evas since it's only
X11", but evas is the display, not the image lib.
Am I wrong or the only display that supports many devices is
sdl/pygame? There is another?
BTW: Just something that pop in my mind right now: it's possible to do
an export VF in mplayer that will let mplayer use the display from
other app? That way we could have mplayer to use our windows and vanish
with the mess it's now (launching mplayer window atop of freevo).
Gustavo
_______________________________________________________
Yahoo! Acesso Grátis - navegue de graça com conexão de qualidade! Acesse:
http://br.acesso.yahoo.com/
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
