Not by much. Do you know, without thinking, that FFFFFFF is opaque white?
Can you tell what color are 5453245, 4543262?
As you see, the text-based format does not make this more confortable to
edit, in the case of colors. It is more readable/modifiable than a binary
blob, but why would you need to modify it directly?
For sending them over the network there is little point in using XML. You
can use BArchivable and put them into a BDataIO in binary format, which
will be more efficient.
And for debugging, you can write an appropriate tool (there is "message"
to dump BMessages archived to a file, probably it can be used with netcat,
or we could make a wireshark plugin, etc).
XML is supposed to be readable easily both by humans and computers, and it
failed. It is complex to parse, both for humans and for computers, when
compared to other formats, either binary (protobuf, ASN.1, ...) or
text-based (JSON, ...).
There is not yet a standard DTD for converting BMessages into XML. We
could decide on base64, check if the data can be represented as utf-8 and
use that, use CDATA, use uuencode, or some more compact encoding.
* On the other hand, parsing "any" XML file and representing it in some
useful and easy to handle format. XmlNode does this, for example, but it is
probably simpler to use the existing and industry-standard ways: SAX and
DOM. And to use these, we can rely on libxml or a similar existing library.
Is there really a need for a BeAPI-ish wrapper on these?
will really want to edit the file manually?
build your color palette, than manually enter hex-digits in a text file.
I think it is one of the worst examples you could have chosen, sorry :)