svgdomcsharp-developers

Revival!

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

Hi everyone,
The project is alive again, with me as main reanimator :)
I already did a few changes:
- switched from CVS to SVN
- switched to Visual Studio 2008 (still targetting .NET 2.0, but using C#
3.0)

My current job is to perform a few fixes (I'm working with wikipedia SVG
flags database,where links can be found at
http://en.wikipedia.org/wiki/ISO_3166-1).<http://en.wikipedia.org/wiki/ISO_3166-1>

After this, I'd like to perform the following changes:
- merging assemblies (at least SharpVectorsBindings, SharpVectorCss,
SharpVectorDom, SharpVectorUtil and SharpVectorObjectModel).
- moving all unit tests to a separate assembly (for reasons I don't
understand, some tests are in the main assemblies).
- conforming assemblies settings so the classes namespaces match the path
(ReSharper sends me a lot of warnings about this).
- documenting (with a little help from GhostDoc).

Any comments, suggestions?

Thanks,
Pascal.

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

Re: Revival!

[Jeff R. <jef...@gm...>]

Hi Pascal,

Sorry I didn't get a chance to reply earlier, but I think this is  
great and am really excited to see the project coming alive. The  
reason that everything was split into separate assemblies was to make  
it easy and quick to determine where something would be. Apart from  
that the Bindings was used separately by projects like the scripting  
interfaces (which iirc were not completely finished with regards to  
timing).

Please feel free to ask any questions you have (and include code  
samples along the way).

All the best,
Jeff Rafter

On Feb 4, 2009, at 5:19 AM, Pascal Craponne wrote:

> Hi everyone,
>
> The project is alive again, with me as main reanimator :)
> I already did a few changes:
> - switched from CVS to SVN
> - switched to Visual Studio 2008 (still targetting .NET 2.0, but  
> using C# 3.0)
>
> My current job is to perform a few fixes (I'm working with wikipedia  
> SVG flags database,where links can be found at http://en.wikipedia.org/wiki/ISO_3166-1) 
> .
>
> After this, I'd like to perform the following changes:
> - merging assemblies (at least SharpVectorsBindings, SharpVectorCss,  
> SharpVectorDom, SharpVectorUtil and SharpVectorObjectModel).
> - moving all unit tests to a separate assembly (for reasons I don't  
> understand, some tests are in the main assemblies).
> - conforming assemblies settings so the classes namespaces match the  
> path (ReSharper sends me a lot of warnings about this).
> - documenting (with a little help from GhostDoc).
>
> Any comments, suggestions?
>
> Thanks,
> Pascal.
>
> jabber/gtalk: pa...@ja...
> msn: pa...@cr...
>
> ------------------------------------------------------------------------------
> 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

Re: Revival!

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

Hi Jeff,
pleased to meet you, I saw you name in a large number of CVS commits :)
Apparently a lot of developpers (well, at least two :)) collapsed the five
assemblies mentioned below, this is why I think this is a requirement.
I think of SVG# as a set of 3 assemblies:
1. The core
2. The tests (all tests: some unit tests are currently in the core and I
don't understand why)
3. The GDI renderer

Pascal.

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



On Wed, Feb 4, 2009 at 18:41, Jeff Rafter <jef...@gm...> wrote:

> Hi Pascal,
> Sorry I didn't get a chance to reply earlier, but I think this is great and
> am really excited to see the project coming alive. The reason that
> everything was split into separate assemblies was to make it easy and quick
> to determine where something would be. Apart from that the Bindings was used
> separately by projects like the scripting interfaces (which iirc were not
> completely finished with regards to timing).
>
> Please feel free to ask any questions you have (and include code samples
> along the way).
>
> All the best,
> Jeff Rafter
>
> On Feb 4, 2009, at 5:19 AM, Pascal Craponne wrote:
>
> Hi everyone,
> The project is alive again, with me as main reanimator :)
> I already did a few changes:
> - switched from CVS to SVN
> - switched to Visual Studio 2008 (still targetting .NET 2.0, but using C#
> 3.0)
>
> My current job is to perform a few fixes (I'm working with wikipedia SVG
> flags database,where links can be found at
> http://en.wikipedia.org/wiki/ISO_3166-1).<http://en.wikipedia.org/wiki/ISO_3166-1>
>
> After this, I'd like to perform the following changes:
> - merging assemblies (at least SharpVectorsBindings, SharpVectorCss,
> SharpVectorDom, SharpVectorUtil and SharpVectorObjectModel).
> - moving all unit tests to a separate assembly (for reasons I don't
> understand, some tests are in the main assemblies).
> - conforming assemblies settings so the classes namespaces match the path
> (ReSharper sends me a lot of warnings about this).
> - documenting (with a little help from GhostDoc).
>
> Any comments, suggestions?
>
> Thanks,
> Pascal.
>
> jabber/gtalk: pa...@ja...
> msn: pa...@cr...
>
> ------------------------------------------------------------------------------
> 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
>
>
>

Re: Revival!

[Cort S. <cor...@gm...>]

I have been using SVG# for quite some time to drive a few projects.  We have
actually made a number of changes both to functionality as well as to
performance.  I would be more than happy to share those back with the
project.
We had made several inquires to the project and never got any responses back
so we considered the project dead and later reformatted the source to match
our standards --- which will make trying to isolate the diffs interesting.
 We had upgrade to VS2008 as well.

Cort

On Wed, Feb 4, 2009 at 6:19 AM, Pascal Craponne <pi...@gm...> wrote:

> Hi everyone,
> The project is alive again, with me as main reanimator :)
> I already did a few changes:
> - switched from CVS to SVN
> - switched to Visual Studio 2008 (still targetting .NET 2.0, but using C#
> 3.0)
>
> My current job is to perform a few fixes (I'm working with wikipedia SVG
> flags database,where links can be found at
> http://en.wikipedia.org/wiki/ISO_3166-1).<http://en.wikipedia.org/wiki/ISO_3166-1>
>
> After this, I'd like to perform the following changes:
> - merging assemblies (at least SharpVectorsBindings, SharpVectorCss,
> SharpVectorDom, SharpVectorUtil and SharpVectorObjectModel).
> - moving all unit tests to a separate assembly (for reasons I don't
> understand, some tests are in the main assemblies).
> - conforming assemblies settings so the classes namespaces match the path
> (ReSharper sends me a lot of warnings about this).
> - documenting (with a little help from GhostDoc).
>
> Any comments, suggestions?
>
> Thanks,
> Pascal.
>
> jabber/gtalk: pa...@ja...
> msn: pa...@cr...
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>

Re: Revival!

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

Hi Cort,
that sounds great. I've fixed some bugs today, and I'm now experiencing
random rendering problems. I suspect that some matrix computing is wrong
somewhere, but it's hard to tell where.
I'd love to see you changes committed to the project.
Are you a registered contributor?

Pascal.

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



On Wed, Feb 4, 2009 at 19:11, Cort Schaefer <cor...@gm...> wrote:

> I have been using SVG# for quite some time to drive a few projects.  We
> have actually made a number of changes both to functionality as well as to
> performance.  I would be more than happy to share those back with the
> project.
> We had made several inquires to the project and never got any responses
> back so we considered the project dead and later reformatted the source to
> match our standards --- which will make trying to isolate the diffs
> interesting.  We had upgrade to VS2008 as well.
>
> Cort
>
> On Wed, Feb 4, 2009 at 6:19 AM, Pascal Craponne <pi...@gm...> wrote:
>
>> Hi everyone,
>> The project is alive again, with me as main reanimator :)
>> I already did a few changes:
>> - switched from CVS to SVN
>> - switched to Visual Studio 2008 (still targetting .NET 2.0, but using C#
>> 3.0)
>>
>> My current job is to perform a few fixes (I'm working with wikipedia SVG
>> flags database,where links can be found at
>> http://en.wikipedia.org/wiki/ISO_3166-1).<http://en.wikipedia.org/wiki/ISO_3166-1>
>>
>> After this, I'd like to perform the following changes:
>> - merging assemblies (at least SharpVectorsBindings, SharpVectorCss,
>> SharpVectorDom, SharpVectorUtil and SharpVectorObjectModel).
>> - moving all unit tests to a separate assembly (for reasons I don't
>> understand, some tests are in the main assemblies).
>> - conforming assemblies settings so the classes namespaces match the path
>> (ReSharper sends me a lot of warnings about this).
>> - documenting (with a little help from GhostDoc).
>>
>> Any comments, suggestions?
>>
>> Thanks,
>> Pascal.
>>
>> jabber/gtalk: pa...@ja...
>> msn: pa...@cr...
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>

Re: Revival!

[Bryan L. <bry...@gm...>]

Hey there Pascal,

Good to have you on board.  Such a coincidence meeting you here after
working together on the dbLinq project.

I've been working with a fork of SharpVector at
http://www.codeplex.com/XamlTune.  They've got a xaml renderer to do
svg->xaml conversions.

Bryan

On Wed, Feb 4, 2009 at 6:19 AM, Pascal Craponne <pi...@gm...> wrote:
> Hi everyone,
> The project is alive again, with me as main reanimator :)
> I already did a few changes:
> - switched from CVS to SVN
> - switched to Visual Studio 2008 (still targetting .NET 2.0, but using C#
> 3.0)
> My current job is to perform a few fixes (I'm working with wikipedia SVG
> flags database,where links can be found
> at http://en.wikipedia.org/wiki/ISO_3166-1).
> After this, I'd like to perform the following changes:
> - merging assemblies (at least SharpVectorsBindings, SharpVectorCss,
> SharpVectorDom, SharpVectorUtil and SharpVectorObjectModel).
> - moving all unit tests to a separate assembly (for reasons I don't
> understand, some tests are in the main assemblies).
> - conforming assemblies settings so the classes namespaces match the path
> (ReSharper sends me a lot of warnings about this).
> - documenting (with a little help from GhostDoc).
> Any comments, suggestions?
> Thanks,
> Pascal.
>
> jabber/gtalk: pa...@ja...
> msn: pa...@cr...
>
>
> ------------------------------------------------------------------------------
> 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

Re: Revival!

[Niklas G. <ni...@pr...>]

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

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
>

Re: Revival!

[Bryan L. <bry...@gm...>]

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

Re: Revival!

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

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
>

Re: Revival!

[Cort S. <cor...@gm...>]

I think we fixed some of the number parsing, as well as some performance
issues.  We did fix some problems with the DTD caching, which was a big part
of performance.  I don't know what I would remove the validated reader and
just assume that the document is well formated -- that would potentially
lead to other code having to do validation and/or error handling if that was
not the case.  I unfortunately got bit a few times on poorly formed SVG
documents.
I have not had a chance just yet to isolate my changes -- I did get the new
code though, so that was step 1.

Cort

On Fri, Feb 6, 2009 at 11:14 AM, Pascal Craponne <pi...@gm...> wrote:

> 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
>>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>

Re: Revival!

[Cort S. <cor...@gm...>]

Another comment -- just because the simple SVG files are all using common
DTD, doesn't mean that there won't be others referenced that are not common
-- i.e. when a document is exported from Adobe Illustrator, if they want to
keep the Adobe specific information for their UI, it adds other references
and a lot of other "stuff".  :)
Cort

On Fri, Feb 6, 2009 at 11:14 AM, Pascal Craponne <pi...@gm...> wrote:

> 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
>>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>

Re: Revival!

[Cort S. <cor...@gm...>]

Another issue that I have just lived with and hit me again today, is a
problem with the polygon element.  When one is read in and I then obtain the
path for it -- the path is incorrect (scaled to small).  I might be able
able to identify a test case, but have instructed those creating the
documents to simply them first so that we just don't have that element.
Cort

On Fri, Feb 6, 2009 at 11:14 AM, Pascal Craponne <pi...@gm...> wrote:

> 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
>>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>

Re: Revival!

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

I fixed a matrix problem recently (related to a number parsing problem). Did
you try using the latest SVN version?

On Fri, Feb 6, 2009 at 20:32, Cort Schaefer <cor...@gm...> wrote:

> Another issue that I have just lived with and hit me again today, is a
> problem with the polygon element.  When one is read in and I then obtain the
> path for it -- the path is incorrect (scaled to small).  I might be able
> able to identify a test case, but have instructed those creating the
> documents to simply them first so that we just don't have that element.
> Cort
>
>
> On Fri, Feb 6, 2009 at 11:14 AM, Pascal Craponne <pi...@gm...> wrote:
>
>> 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
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>

Re: Revival!

[Cort S. <cor...@gm...>]

No, my current production code is still based on my 'forked" version.  I
will be sure to check that though at that point.  I will see if I can
identify a test case to verify that it is or use as a basis to get it fixed.

On Fri, Feb 6, 2009 at 12:52 PM, Pascal Craponne <pi...@gm...> wrote:

> I fixed a matrix problem recently (related to a number parsing problem).
> Did you try using the latest SVN version?
>
>
> On Fri, Feb 6, 2009 at 20:32, Cort Schaefer <cor...@gm...>wrote:
>
>> Another issue that I have just lived with and hit me again today, is a
>> problem with the polygon element.  When one is read in and I then obtain the
>> path for it -- the path is incorrect (scaled to small).  I might be able
>> able to identify a test case, but have instructed those creating the
>> documents to simply them first so that we just don't have that element.
>> Cort
>>
>>
>> On Fri, Feb 6, 2009 at 11:14 AM, Pascal Craponne <pi...@gm...>wrote:
>>
>>> 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
>>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>>
>>>
>>
>