RE: [Svgdomcsharp-developers] Conversion conventions

[<AW...@UR...>]

I think the c# style is the way to go. 

I made most of changes to the w3c\css\**.cs files (still a work in
progress...). 

What about removing/changing fields to enums e.g. LexicalUnit_Fields.cs??
Don't the underscores need to go?  


Andrew

-----Original Message-----
From: Donald Kackman
To: svg...@li...
Sent: 2/17/2002 11:55 AM
Subject: [Svgdomcsharp-developers] Conversion conventions

Now that it sounds like we're all in agreement about using .NET naming
conventions I think we need to create some guidelines for how exactly to
convert the Java interface syntax to C#.

As Don already mentioned prepending a capital "I" to each interface
would be
the first step.

My main question is what do we do with Java getter and setter methods?
Since
Java doesn't have C#'s property syntax they use a lot of getProperty and
setProperty(value) methods.

Namely should this member:

	string getNamespaceURI();

be left as is or converted to this:

	string NamespaceURI { get; }

This goes a little beyond mere naming issues as C# properties slightly
change the smemantics of property accessors.

I would vote we switch to the C# style as it will again feel more
natural to
.NET programmers.

Do we need a guidelines document for this project? Both to inform those
of
use who will be doing the conversion and those who will eventually be
consuming the library and will need to know how exactly our stuff
compares
to the w3c defined stuff.

don kackman

-----Original Message-----
From: svg...@li...
[mailto:svg...@li...]On Behalf Of
Don XML
Sent: Saturday, February 16, 2002 8:24 PM
To: svg...@li...
Subject: [Svgdomcsharp-developers] C# Source Code



Here's a zip file with the converted Batik interfaces (plus a couple
classes), along with the UML for Visio Arch (I think there is a free
viewer
if you don't have Visio).  I started to go thru the DOM interfaces and
compare them to the W3C.  If anyone else wants to grab another section
of
code and start fixing, go right ahead.  I think we all agree the
changing
the interfaces slightly to me .Net naming conventions is the "right"
thing
to do.  BTW, I found a Java binding example in the W3C Core DOM
documentation, and there are naming standard changes, so I guess it is
alright.

DX


_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com


_______________________________________________
Svgdomcsharp-developers mailing list
Svg...@li...
https://lists.sourceforge.net/lists/listinfo/svgdomcsharp-developers