From: Pascal C. <pi...@gm...> - 2009-02-06 18:14:20
|
I don't go against the work previously done. I assume that if the DTD loading was left it's for a good reason.We could probably implement an option to disable schema loading, but I'm not sure it is the top priority anyway :) There is still some work to do to fix potential issues. I found several problems in string parsing and number to string conversion. These are maybe the next things to fix. A XAML renderer would also be a priority. Just as using a double-precision floating point values for internal computations. Cort, what kind of changes did you make to SVG#? Pascal. jabber/gtalk: pa...@ja... msn: pa...@cr... On Fri, Feb 6, 2009 at 19:05, Bryan Livingston <bry...@gm...>wrote: > What is the value of loading the DTDs? I cut out the DTD loading all > together in xamltune and it still ran fine for my test set of 8000 svg > files, just 2.5x faster. It was tricky to figure out but I can find > the line to change to do that if you'd like. > > Bryan > > On Fri, Feb 6, 2009 at 8:00 AM, Pascal Craponne <pi...@gm...> wrote: > > 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 > > > > > > > ------------------------------------------------------------------------------ > > Create and Deploy Rich Internet Apps outside the browser with > > Adobe(R)AIR(TM) > > software. With Adobe AIR, Ajax developers can use existing skills and > code > > to > > build responsive, highly engaging applications that combine the power of > > local > > resources and data with the reach of the web. Download the Adobe AIR SDK > and > > Ajax docs to start building applications today- > http://p.sf.net/sfu/adobe-com > > _______________________________________________ > > Svgdomcsharp-developers mailing list > > Svg...@li... > > https://lists.sourceforge.net/lists/listinfo/svgdomcsharp-developers > > > > > > > > -- > Bryan Livingston > |