On 2/13/13 9:47 PM, Brian Anderson wrote:
During a lunch discussion today we decided that we have three areas that
we care most about this year: layout, crow, and dom bindings.
We still need to make basic measurements of round-trip times through our
DOM to layout and back on a sync layout flush. I haven't been able to
do that yet, not least because I haven't actually managed to get servo
to compile any of the times I've tried it recently....
I believe that's higher priority than pretty much anything else right
now, because we need that to know whether the general architecture is
getting us the performance we want.
That said, what is "crow"?
I haven't actually created a DOM-related milestone yet because we
haven't come up with a goal that I'm satisfied with ("create working dom
bindings" is vague). Things we've considered as short-term bindings
goals are canvas and WebGL. Does anybody have suggestions here?
How about deciding on an actual implementation strategy for the DOM?
Simple things like how we actually plan to represent DOM objects in Rust
in a way that allows bindings to work with reasonable performance (i.e.
without having to make everything a virtual call) would be a good
start... I've tried bringing this up before and keep being told that
the relevant parts of Rust are in flux so we have to decide later.
-Boris
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
