* Roman Shaposhnik <[EMAIL PROTECTED]> wrote: > Well, in that case it seems that it would be indeed, all you need. > I'm very far from being an expert on how modern browsers are designed, > but it seems the only shared thing between a browser and a plugin > should be set of rectangular framebuffers. I would expect the rest > of resources to be either available as-is (audio, etc.) or be request > from the browser in a general fashion (bookmarks, history, etc.).
hmm, just had a quick look through the swfdec plugin code ... Seems to be some bit more. There are also things like input stream, URL access, etc. Okay, let's start with an Canvas. I've collected some ideas: * http://oss-qm.metux.de/index.php/9forge/Canvas > The trickiest part seems to be exploring locality for the mapped > rendering (imagine a multimedia plugin displaying an HD movie). Those things require special interfaces, which tunnel streams through 9P. Maybe something like mjpeg with timestamps. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ ---------------------------------------------------------------------
