> Monte Goulding wrote: > > > There was an mcRipper to save a stack as XML but I think it > crashes 2.x. It > > shouldn't be too hard to modify though. I'd be very interested > in a system > > that created individual XML files for each object with > references to each > > other. That way it would be possible to muck around with the > relationships > > between objects to improve reuse & maintainability. For example > you could > > use the same card on two stacks and maintain the one source. > > Yeah, lots of advantages. I looked at the code in Application Browser > and it all looks doable, though I am not sure you can get all of the > properties of an object (at least, this is what the docs say for > "properties"). I guess XML is as good a format as any. >
Whatever properties that aren't in the properties array could be requested individually. Unless we can get a list of them from RunRev it would be trial and error to work out exactly what properties are listed under 'Others'. but the properties array is a great place to start. In addition, customProperties and customPropertySets would be needed. _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
