On Tuesday, November 11, 2014 10:48:15 AM UTC-6, Josh Matthews wrote: > Here are the transcribed discussions from the work week that took place > in Mountain View last week: > > https://github.com/servo/servo/wiki/Workweek-graphics-toolkit - > replacing GLFW/GLUT with glutin; advantages/disadvantages of CEF vs. > native toolkit for embedding; thoughts on Skia vs. GL vs. D2D; CEF concerns. > > https://github.com/servo/servo/wiki/Workweek-rasterization - current > status; CPU or GPU; rasterization on ARM; Moz2D vs. Skia; GLES on > Android; mixed CPU/GPU layers. > > https://github.com/servo/servo/wiki/Workweek-android-arm - current > status; overview of available ARM devices; brainstorming "usable" public > APK; action items. > > https://github.com/servo/servo/wiki/Workweek-encoding - UTF16/UTF8/WTF8 > upsides and downsides; obtaining relevant perf/usage measurements; let's > talk to the SpiderMonkey team. > > https://github.com/servo/servo/wiki/Workweek-governance - creating a > Servo module; are CLAs required; explicit commit access/review powers > policy. > > https://github.com/servo/servo/wiki/Workweek-layers2 - iframes and the > compositor; coordinate systems in layers; layer hierarchy in compositor; > CSS transforms and animations and Gecko's refresh driver; cross-origin > iframe security. > > https://github.com/servo/servo/wiki/Workweek-js-bindings-status > (unfocused discussion) - difficulties of ensuring correctness of > bindings-related things; rewriting C++ code in Rust; Gecko security bug > audits. > > https://github.com/servo/servo/wiki/Workweek-boot-2-servo - b2g > architecture; motivations/goals of b2s; power/performance concerns. > > https://github.com/servo/servo/wiki/Workweek-security - security bug > policy; known vulnerabilities; desired security for first nightlies; > whitelisting visitable sites. > > https://github.com/servo/servo/wiki/Workweek-dogfooding - discussion of > UI for first release; identifying high-priority missing features > required for serious dogfooding. > > https://github.com/servo/servo/wiki/Workweek-alt-js - motivations for > creating a new JS engine in Rust; alternatives to rewrite-the-world; > further discussion tabled until mid 2015. > > https://github.com/servo/servo/wiki/Workweek-script-crate - splitting up > script/DOM-related code to reduce compile times. > > Action items: > - Update Skia to the newest version. (Martin Robinson) > - Make GPU rendering the default on OSX. (zwarich) > - Get OSX GPU reftests passing. (zwarich) > - Follow-up: can we just remove Azure/Moz2D and use Skia directly? > Involve Gecko gfx team in decision. (discuss with gfx team) > - Follow-up: new ARM gl2d work that we should look at. (lars) > - Build an Android wikipedia browser using glutin in Q1 (mbrubeck) > - Get the Android buildbot both building and testing (larsberg) > - Look at ARM Linux performance measurement on a custom board (e.g., > NVidia shield) (larsberg) > - Write up governance and r+ stuff on the wiki (larsberg) > - Talk with gerv about what we need people to sign (larsberg) > - Fix bors to use the Github owners list instead of a private r+ list > (larsberg) > - Compositor will get short-term ability to add layers (mrobinson) > - Decision on restricted browser vs. dropdown vs. open address bar will > be determined by what's working when we want to ship the alpha > - Need simple cert checking in Servo (manishearth, december) > - Need wiki page for security bug reporting in Servo, with known issues, > too (kmc) > - Craft good disclaimer that encourages people to attack & report vulns > (dave) > - Build custom chrome with URL bars on desktop platforms with native > controls (pcwalton, jack) > - Make a link to the dogfooding bugs next to the E-Easy bugs to make > them visible (jdm) > - glutin or cef windowing harness to do things like load time testing > (what format to spit out? investigate what devtools do for this in other > browsers), simplified scroll tests (ensuring compositor runs at 60fps) > (mbrubeck) > - crash tests (minimized crashers, in tree) (jdm) > - arewefastyet/areweslimyet style recording/display of servo data over > time (mbrubeck) > - try organizing js team collab in portland (encoding, discussing moving > gc plans, utf8, etc) (jack) > > Cheers, > Josh
For the workweek-Rasterization notes, one tidbit is that it looks like CEF offscreen rendering now supports some hardware accelerated rendering (enabling CSS3 transforms and webgl) but still lacks the ability to render directly to a client provided buffer without a CPU copy: https://code.google.com/p/chromiumembedded/issues/detail?id=1006 I definitely support the idea of having a common embedding API / ABI making it easier to test Servo by swapping it with CEF in my applications. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
