RE: [Svgdomcsharp-developers] More Conversion conventions

[Don X. <do...@ho...>]

Your suggestions are along the same lines as I was thinking.  The only other 
thing I was going to do was to build the DOMException in Visio UML (they 
have an Exception signal) and then take a look at the generated code.  I 
figure it will look like your bullet number 2.

As for the Visio Viewer problem, It probably doesn't work with the VS Arch 
version, or maybe the UML.  There is a save as Web feature, but since I 
don't have any drawings (just the UML) it doesn't help much.

DX


>From: "Donald Kackman" <do...@it...>
>To: svg...@li...
>Subject: RE: [Svgdomcsharp-developers] More Conversion conventions
>Date: Sun, 17 Feb 2002 15:49:50 -0600
>
>Here's what I propose:
>
>1) All SVG exceptions inherit from DOMException.
>2) DOMException inherits from ApplicationExpsetion and adds the error code
>field
>3) All exceptions that inherit from DOMException implement at a minimum the
>following constructors:
>	public EventException(short code) : base( code )
>	{
>
>	}
>
>	public EventException(short code, string message) : base( code, message )
>	{
>
>	}
>
>	public EventException(short code, string message, Exception 
>innerException)
>: base( code, message, innerException )
>	{
>
>	}
>
>I have attached a rewrite of DOMException and EventException following this
>proposal.
>
>Comments?
>
>don kackman


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