Markup Language vs. Binary format for ESX files

[ezzetabi]

Sure thing. But just with few man-hours of system design it would be better.

[Greendogo]

So what do you guys think about a readable markup-language (XML) for the ESXs or some kind of converter? yes, no?

[Zini]

No. Way too much work for way too little benefit. Manually fiddling around with ESX files doesn't sound like a good idea anyway. Quite easy to break something, since almost everything in an ESX file is somehow connected to almost everything else. Delete an ID that still has references? Plugin broken. Remove a local variable from a script, that is referenced from a dialogue? Plugin broken. I could continue like this for an hour.
Manipulating ESX files without the verification functionality of an editor (and ours will certainly have much more than the original CS) will only lead to broken plugins. Also, if the editor is becoming as efficient (UI wise) as I am imagining it, there will be no need to manipulate ESX files directly. For manual editing tasks you can use the editor directly and for batch tasks you can write a Python script.

[Greendogo]

Alright, that's fine. The editor is already going to be more feature complete than Morrowind's original. Just make sure there is good documentation for the ESX format for developers, I guess.

[ezzetabi]

It is open source... the code is the ultimate documentation as it explain exactly how the program will use the stuff.

[sirherrbatka]

With the python interface separate tools like landmass mover will be obsolete so honestly no gain from text files.

[xXShaddowTXx]

This discussion was an interesting read.