Notes on the modified Jade demo

XML format of the Jade data structures

There is no strict schema definition yet, but the structure is made to appear as if it is similar to this example:

<instance module="primitives:nfet-scaled" name="$12">
	<property name="$NAME" value="$12" />
	<property name="SW" value="2" />
	<terminal name="G">
		<property name="i" value="NaN" />
		<property name="v" value="NaN" />			
	</terminal>
</instance>
<wire name="wire1">
	<property name="i" value="NaN" />
	<property name="v" value="NaN" />
</wire>

Note: Wires should only be accessed if they have a name.

Note: setValue on a property will have the same effect as setValue on that property's "value" attribute

Note: The name attributes of properties, terminals and instances cannot be altered. To rename an instance, alter the value attribute of its name property instead.

Note: The module attribute on the instance is not accessible yet.

XML-RPC

XMLRPC support is provided through ClientControllerApplet. This applet, as well as being an XMLRPC client, expects to receive the XML of an XMLRPC call as the response from the server. The client is designed to communicate with the server via XML-RPC. However, it should be noted that because this is run as an untrusted applet, the server cannot send an unsolicited XML-RPC to the client. To get around this, the client expects an XML return object from every XML-RPC it makes to the server. This XML return object is in effect a kind of XML-RPC itself. For example:

<?xml version="1.0"?>
<methodCall>
	<methodName>jade.setValue</methodName>
	<params>
		<param>
			<value></value>
		</param>
		<param>
			<value>/instance[@name="$12]/terminal[@name="g"]/property[@name="i"]</value>
		</param>
		<param>
			<value>2</value>
		</param>
	</params>
</methodCall>

Other functions are being added...