Hi, Recently I have been working on B2G port to mobile Linux which would be widget toolkit-independent (qt/gtk/cocoa/etc).
The goal is to make it easy to build Mozilla/Gecko on boards like BeagleBoard (ubuntu-arm), PandaBoard (ubuntu-arm), Tegra (L4T), Raspberry Pi (debian-arm). Quite often such boards come with very little userland software stack ported to them, so widget toolkits might not be readily available, optimized, etc. What they often do come with is GL stack, which is much better shape. We could use that to bring up B2G drawing without much fuss and dropping widget toolkits dependencies altogether. So I decided to create a new widget backend called cairo-linuxgl. You can think of it as GONK backend but with Android dependencies stripped out. This allows building of fast and efficient rendering/events pipeline while skipping redundant layers of code coming from widget toolkits. The initial patch queue is available here: http://hg.mozilla.org/users/romaxa_gmail.com/embedipc_queue/file/linuxglpure/linuxgl Patch queue contains: configure system gfxPlatform Widget DOM part The patches allow one to build runnable B2G configuration with new cairo-linuxgl backend. Currently framebuffer/GL rendering works pretty good, there is basic mouse events support. Key events recognized but aren’t dispatched properly yet. Original bug related to that work: https://bugzilla.mozilla.org/show_bug.cgi?id=731498 Some people already expressed interest in working with me on this so I'm trying to figure out what is the best place to park the code we are going to work on. Would it make sense to land initial build/run configuration support into mozilla-central now and work on it in main tree. Alternatively we could maintain a branch outside (github or similar) but that would mean frequent rebases. Any suggestions, ideas? Everybody is welcome to join! Br, Oleg _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
