Stefan Seefeld <[EMAIL PROTECTED]> writes:
> Speaking about video and animation, may I come back to
> a suggestion I had a couple of weeks back ?
>
> I proposed to separate the 'Visual' structure into a
> 'Drawable' and a part concerned about event handling.
> The argument is quite in line with Andreas' request to
> refactor functionality in decompressing and drawing:
> Drawing and event handling have *nothing* to do with
> each other.
Sure they do, how else would you know what happens to the visual?
Expose events and such.
Besides I'm not really sure what you mean by separating out the
event handling from the visual structure. Of the whole ggi_visual_t
there is one single pointer related to event handling, isn't that
separated enough for you?
> My reason to ask this is that I'd like to
> see one day a 'drawable store' manager able to allocate
> any number of Drawables which I can draw into and then
> copy from one into another etc. However, there's always
> just one event listener.
> Berlin currently uses one Visual to draw into (via GGIMesa
> or libArt) but I'd like to have offscreen drawables which
> I can draw animations, videos and other things into before
> I blend them into the scene graph. Even animated pointers
> could be handled this way.
> The manager I'm talking about would then inspect the
> amount of accessible video memory and allocate either from
> that or, if it runs out of vram, from normal heap.
A manager for video memory will be implemented in LibGGI soon,
Andy and I have just talked about that. This will make it simple
to implement an extension for offscreen images.
//Marcus
--
-------------------------------+------------------------------------
Marcus Sundberg | http://www.stacken.kth.se/~mackan
Royal Institute of Technology | Phone: +46 707 295404
Stockholm, Sweden | E-Mail: [EMAIL PROTECTED]
