Introducing a second HL library?


Re: Introducing a second HL library?
#36
Steffen Wrote:XML to me always appeared too overheading.

..


I write this to argument against XML. I have to deal with it a lot elsewhere, and despite the fact that parsers
for it exist a lot etc. pp., its syntax overhead always is ineffective and annoying.
JSON would be something much better IMHO. Parsers for it exist as well a lot.

I too have to deal with it daily at work Smile Here's an example of how a 3d geometry can be expressed in json (just an example, we can put whatever format of course):


Code:
{
    "metadata": {
        "version": 3.1,
        "type": "geometry",
        "generator": "GeometryExporter"
    },
    "vertices": [50,50,50,...],
    "normals": [1,0,0,...],
    "uvs": [[0,1,...]],
    "faces": [56,0,2,1,0,1,2,0,0,0,0,...]
}

(taken from here)

Boh machine and human readable. JSON can take advantage of array definitions which XML has not.
Reply
« Next Oldest | Next Newest »



Messages In This Thread
Re: Introducing a second library? - by Nicola - 2015-02-23, 16:19
Sergio Reano passed away - by Steffen - 2014-11-14, 23:10
Re: Introducing a second HL library? - by Nicola - 2014-11-14, 22:38

Forum Jump:


Users browsing this thread: 1 Guest(s)