In what sense are any of these things (outside of utility-like data structures) reusable? Or, is it possible to swap out one implementation for another? Is this just a workaround for lacking incremental compilation? Do we want to encourage modularity at the task or functionality boundaries?
Almost any new layout features in the near future will require changes to the display list machinery, in addition to changes in other submodules such as css and platform APi bindings. As submodules stand now, it's getting quite hard to understand the project history, as it's scattered across 30 git logs. On Nov 11, 2012, at 19:47 , Patrick Walton wrote: > Just FYI, I've split out GFX and all its dependencies (image, resource, text, > most of util) into the servo-gfx crate as a submodule. This means that if > you're just modifying layout you can avoid rebuilding some ~5000 lines of > code of the graphics module. > > The resource crate and util should further be split out; clearly the resource > manager does not belong in the graphics crate. Possibly we should split out > layout as well. > > Patrick > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
