Recent

Author Topic: New versions of lazarus use JSON instead XML  (Read 4983 times)

edgarrod71

  • New Member
  • *
  • Posts: 22
New versions of lazarus use JSON instead XML
« on: February 20, 2016, 04:08:23 am »
I've been learning about JSON, and it would be a great idea to change the forms files into this format instead xml, and svg graphic support.

skalogryz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2284
    • havefunsoft.com
Re: New versions of lazarus use JSON instead XML
« Reply #1 on: February 20, 2016, 04:43:53 am »
JSON! yay! ... wait. what's the benefit?
Patron Cocoa Widgetset development https://www.patreon.com/skalogryz

edgarrod71

  • New Member
  • *
  • Posts: 22
Re: New versions of lazarus use JSON instead XML
« Reply #2 on: February 20, 2016, 06:41:52 am »
It's more readable, it's more lightweight, and maybe it can improve lazarus in compiling...

Leledumbo

  • Hero Member
  • *****
  • Posts: 8112
  • Programming + Glam Metal + Tae Kwon Do = Me
Re: New versions of lazarus use JSON instead XML
« Reply #3 on: February 20, 2016, 08:01:29 am »
I've been learning about JSON, and it would be a great idea to change the forms files into this format instead xml, and svg graphic support.
Form files are in .lfm format, a variant of object type definition in Pascal. XMLs are only used for configuration files. There's no clear benefit for Lazarus if they're replaced with JSONs. It doesn't affect anything in the IDE (do you think the IDE's less-than-1-second load time is slow?), nor user projects, let alone the compiler.

Thaddy

  • Hero Member
  • *****
  • Posts: 9191
Re: New versions of lazarus use JSON instead XML
« Reply #4 on: February 20, 2016, 09:18:24 am »
JSON! yay! ... wait. what's the benefit?

There is a small benefit in that serializing/deserializing components becomes a little more standard.
I have been using custom code for years to populate Delphi or FPC components over a network based on dfm/lfm format whereas I use json for other objects, even in between different languages (deserialize to ecmascript or C++ objects).
So, yes, I can see a point in using json. But it is not that important.

As for SVG support: I'd rather see html canvas support. (I am working on that off and on, btw, nothing publishable yet)
« Last Edit: February 20, 2016, 09:27:45 am by Thaddy »
also related to equus asinus.