Info From Mailing List
The core of the software is a file called adms.xml.
From this file most of the c code of adms is created.
This file describes the way adms saves internal data tree.
The root element is <element name="adms">.
This element is made of:
<element name="device" info="device">
...
In turn element 'device' is made of:
<pointer name="devicenode">
<pointer name="variable">
...
You can access all the nodes of the internal data tree
using xml transforms. For instance this code:
<adms:for-each select="device">
<adms:value-of select="name"/>
<adms:text format="name of device = %s\\n"/>
</adms:for-each>
will select the name of the device and prints it out.
(see adms.xml).
The xml scripts are using two languages (see http://mo=
t-adms.sourceforge.net/).
The first one is called admst (for adms xml transforms). For instance admst=
:text, admst:value-of and so on...
The other one is called admstpath. It is used inside the "". For instance s=
elect=3D"variable", format=3D"hello world".
NOTE that admst should actually be the xslt language and admstpath should a=
ctually be the xpath language.
(see very good intro on xslt and xpath at http://www.w3schools.com/default.=
asp)
In the currrent impl. of adms admst and admstpath are 'builtin'. I tried to=
use open-source libs
that implement xslt and xpath. However so far without success :-) (the resu=
lting code was far too slow.)
Consequence: the current implementation of admst and admstpath just cover w=
hat was required
to convert VLA code into C code for some electrical simulators.
However this week I plan to release a new version of adms with all the code=
that computes
the partial derivatives in xml language. Please tell me which new features =
you would like to have
in this new version? See http://www.w3schools.com/xpath/xpath_functions.asp=
for a list of xpath
functions. What you are requesting is called lower-case(...). I will see wh=
at I can do.
Thanks,
Laurent
I am trying to line up the admst language with xslt (adms-2.1.1).
I renamed the following constructs:
1- admst:apply-template to admst:apply-templates
2- admst:templates to admst:apply-template
3- admst:choice to admst:choose
In order to guarantee backward-compatibility I have two solutions:
Solution (1):
The old constructs will be valid but obsolete.
adms will issue a warning to STDERR if an old construct is used.
Solution (2):
Introduce a new shell environment - say 'adms_obsolete'.
adms will issue a warning to STDERR if an old construct is used.
AND if 'adms_obsolete' is defined.
If nobody complains I will implement (1).
Thanks,
Laurent Lemaitre
Freescale - Geneva
Hi Rajesh,
Please can you be more specific?
If in the va code you get: $strobe(...) then this item
is saved as a 'callfunction' node in the adms tree.
File
http://mot-adms.svn.sourceforge.net/viewvc/mot-adms/trunk/adms/admsXml/a
dms.implicit.xml
tells you how to use 'callfunction' in xml scripts.
Laurent
-----Original Message-----
From: Rajesh V [mailto:msrajeshv@...]
Sent: Monday, September 29, 2008 2:44 PM
To: mot-adms-users@...
Subject: [mot-adms-users] callfunctionhi
has anyone got idea to implement callfunctions for $strobe() etc..
Thanks
Rajesh