Re: Revival!

[Pascal C. <pi...@gm...>]

I committed a version where the most common DTD files are embedded in the
assembly, so it is not necessary to download them anymore when loading a
document.
This makes the point for merging all assemblies: currently it is handled in
ObjectModel assembly, since it is related to SVG. Anyway, during unit tests,
we still have very slow loading when we test Document or CssXmlDocument,
 because the optimization is below them.

So we have two options:
- moving DTDs and embedded resources into the Dom assembly
- merging all assemblies

Or maybe the tests are not accurate, and SvgDocuments should be used when
SVG DTD are referenced?

Pascal.

jabber/gtalk: pa...@ja...
msn: pa...@cr...



On Wed, Feb 4, 2009 at 20:10, Niklas Gustavsson <ni...@pr...>wrote:

> On Wed, Feb 4, 2009 at 2:19 PM, Pascal Craponne <pi...@gm...> wrote:
> > - merging assemblies (at least SharpVectorsBindings, SharpVectorCss,
> > SharpVectorDom, SharpVectorUtil and SharpVectorObjectModel).
>
> This is probably the most controversial change. One reason for the
> split was an idea that each assembly could be reused on its own (like
> by someone needing CSS support but not SVG). I don't think this has
> exactly been a huge success in the user community so from my point
> feel free to do whatever you find best :-)
>
> /niklas
>