> On Tue, 21 Jan 2003, Christoph Egger wrote: > > > > On Tue, 21 Jan 2003, Christoph Egger wrote: > > > > How about using the memory target within libggi's kgi-target, when > the > > > > application runs in background? > > > > > > That's basically what I mean. > > > > Then you were not precisely enough. By using the word "offscreen", > > everybody thought, you mean an offscreen area of the onboard framebuffer... > > Why not? If there's enough space in the gfx board memory then the > offscreen buffer should be allocated there.
If you mean both, then please say that... :-) > > > hw-sprites, I guess, would still be accessed trough an API, right? > > > Hence when the visual is not visible just update the internal sprites' > > > state, don't actually display them. The same goes for the YUV overlay: > > > redirect it to a memory target. When the visual become visible again then > > > refresh the display with the content of the various buffers and the sprites. > > > > That sounds a good idea. But then a) the memory-target must be extended > > to "support" overlay resources > > Not a big deal, is it? Ideally a memory target shouldn't care at all about > what it contains, it's just a framebuffer after all. No. All what is needed is support for virtual objects storing any kind of information in a memory block. The content management of this memory block is left to userspace. This makes the objects useable in a generic way. The content management (which information is how structured) can be done in userspace. I think, that's ok, since this will almost be used from within other targets and/or GGI extensions. Brian: What do you think about this? > > and b) the GGI application should be notified > > somehow, so that the GGI app can stop wasting CPU time with decoding > > a video, for example, when it knows that the result (the decoded video) > > gets no longer displayed... > > If there's any support for applications to get notified when they get > "iconified", then the kgi case should be aliased to it, that is for the > application it's actually the same thing. If there's no such support, then > it's time to implement it :) Note, that not only kgi can take benefit from this. _Any_ target can do so. In order to not redo the same work for each target, this notifying mechanism should be implemented in an helper target. The mansync helper can be used as an example code for an helper target. BTW: Fabio: As you probably guess right, new members in our developer team are always welcome! :-)) -- CU, Christoph Egger E-Mail: [EMAIL PROTECTED] +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!
