-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 3 Feb 2006, Lalo Martins wrote:
It's partially complete; it's only a loader now, not a saver, and some features (specially ACL) are missing, mostly because XOD is still undocumented. So if someone can point me to what those features are and how XOD does them, I can happily add them (preferrably send me a XOD example).
Yes, XOD does need to be documented, in terms of both a schema and programmer/user docs. The ACL stuff is a little bit complicated because it follows an inheritance scheme where child vobjects take the ACLs of the parent vobject, unless declared otherwise. I'll push it into the growing queue of VOS tasks...
This format is intended for config files and things meant for humans to edit.
This is definately more readable for config files. I think you are on to something :-) I do think I would like to use this (or a variation thereof) as the preferred omnivos config format.
In defense of XOD, the decision to go with XML was made on the basis of interoperability moreso than aesthetics. So the two file formats really serve different purposes and if you write a saver, then we can easily convert between the two.
You can `bzr get` the code from http://lalo.revisioncontrol.net/bzr/sod/ (And yes, I know the acronym is weird. Sue me.) ;-)
Well, the original text format was going to be "tod" so maybe you can change the name ;-)
[ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFD5u8kaeHUyhjCHfcRAuaMAKCN1Mo5fVzWX+fLnU9oXeFRvO46PgCgig4T l8mwy+xec5PCP4IyEfign2I= =tnhE -----END PGP SIGNATURE----- _______________________________________________ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
