<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
The reason I was thinking of SVG image format is the connection points
could easily be defined as an ID# of the SVG image. So if you had a
rectangle as a connection point, like this,<br>
<br>
<hr size="2" width="100%"><br>
<rect<br>
style="fill:blue;fill-rule:evenodd;stroke:black;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"<br>
id="rect1872"<br>
width="34.285713"<br>
height="16.71428"<br>
x="288.57144"<br>
y="320.93362" /><br>
<br>
<hr size="2" width="100%"><br>
then in the XML you would have,<br>
<br>
contact1 = "rect1872"<br>
<br>
And so on.......<br>
Obviously I don't know anything about OOP and all this, but if my ideas
help to distill good methods that's all I want!<br>
<br>
<br>
<br>
Alan Grimes wrote:
<blockquote cite="mid46F0A2FF.7070809@speakeasy.net" type="cite">
<pre wrap="">ugh.
I'm looking at what it would take to make a "load component from XML"
method for class component and I'm reminded that I had made a bunch of
robustness enhancements to something in that part of the source tree but
I forgot which class it was in. something about removing a cached
pointer in favor of an accessor method to eliminate the possibility of a
certain type of pointer bug and in order to make the debugging output
more readable.. where'dIputthatcode....
I've also started sketching out a prototype XML format.
</pre>
<pre wrap="">
<hr size="4" width="90%">
<?xml version='1.0' encoding='UTF-8'?>
<electronic_part xmlns="electronics" inherits_from="somePartName" part_description="foobarnator" >
<Description contacts="2" parameters="1" nodes="1" >
<contact1 input="" />
<node1 foobisity="3" />
<!--General description of the part, for allocating simulator resources,
elements may specify information about pins/elements, always assumes nodes = nodes + contacts
--> </Description>
<theory>
<!--equations of operation -- may just inherit from parent
--> </theory>
<limits>
<!--limiting parameters and some function which generates them, could be constant.
--> </limits>
</electronic_part>
</pre>
<pre wrap="">
<hr size="4" width="90%">
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
<a class="moz-txt-link-freetext" href="http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/">http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</a></pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Ktechlab-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ktechlab-devel@lists.sourceforge.net">Ktechlab-devel@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ktechlab-devel">https://lists.sourceforge.net/lists/listinfo/ktechlab-devel</a>
</pre>
</blockquote>
</body>
</html>