Hi, I'm the main developer of the Swfdec Flash player. I'm currently trying to update DirectFB's Swfdec integration to the current Swfdec version. However I have never used DirectFB at all - both technological and organizational - so I have some questions. Here they go in no particular order:
Currently DirectFB uses Swfdec as a video provider. I'm wondering if that makes sense for the Flash format, as Flash is a lot more similar to (scripted) SVG or HTML. Would you suggest providing a browser component as an IDirectFBVideoProvider? Would you prefer I develop the integration inside the Swfdec sources or should it be developed inside the DIrectFB? For me it's definitely easier in the Swfdec source tree as I already have access to all the services I need, but it might be undiscoverable for people wanting to use DirectFB. Swfdec nowadays relies on Cairo for all the rendering done. So the speed of rendering relies heavily on the optimizations done in the Cairo DirectFB backend. As far as I've understood, the "official" backend is unmaintained, but there's also a cairo repository in DirectFB git. So I'm a bit confused about the current state of Cairo on DirectFB. Which one is best to use? How will it go forward? As far as I have seen DirectFB does not have any event loop and relies on threads, which causes a lot of locking to go on in the current Swfdec video provider. Are threads still the suggested method to interact with DirectFB? What's the suggested way of developing DirectFB apps if I don't want to live without my Gnome desktop? Is there some way of running DirectFB on X? Thanks in advance for the answers. Cheers, Benjamin _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
