`viewer' is really a layout engine unit test harness, and has several
features that an `embedding sample app' doesn't and shouldn't have
(e.g., the ability to run regression tests, dump frame and content
models, debug hooks to measure memory usage). I think it's appropriate
to keep these separate.
chris
Mike Pinkerton wrote:
>
> Quick question:
>
> With the embedding harnesses being built, shouldn't those be our new
> "viewer" for testing? We have a lot of code (widgets, etc) that are
> bloating our app _only_ for viewer. The harnesses have that code in
> their app, not in the widget DLL.
>
> Can we make the switch?
