Looking at treeView.rev it looks as though a stack can be traversed and rendered into 
an XML 
tree.

Using vers. 2.01 this sample stack also seems to be faulty - when loaded it has a 
default xml 
document that is located in drive "S:\....", clicking on the top right button marked 
with a 
question mark does not do anything (I was expecting some instructions), and clicking 
on any 
of the stacks produces an error ("xml err, bad document id").  I even had a look 
through the
script in the stack but could not find anything that sugggested its purpose.  In fact, 
it looks
like it was written by another company ("the Attainment Company") and included with 
Rev without 
proper integration or clarification.  (I'm not moaning - I'm imagining what someone 
reviewing Rev
2.01 might say!)

These problems aside:  am I right in thinking that a stack can now be converted into 
XML? 
How far does this conversion go?  (I tested it and the contents of fields are 
converted, and
button design elements e.g. location are converted, but scripts seem to not be 
converted.
Could a stack be written as XML and then transformed using XSL into a Rev stack?

Is there some overview explanation of the purpose of XML in relation to Rev?  I've 
searched
the docs and all I found was references to each specific 'revXML...' command.  A Google
search of this list for "xmltree-view" did not provide anything useful either.

Regards,
Bernard
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to