Structured Configuration Language

[zapta]

As a side note, having a structured configuration language would eliminate most of the confusion with the archaic gcode base configuration. E.g.

probe {
  ...
  dive_height = 20
  ...
}

[fcwilt]

@zapta said in Nothing but trouble with Nozzle as Probe and Mesh Bed Comp:

As a side note, having a structured configuration language would eliminate most of the confusion with the archaic gcode base configuration. E.g.

probe {
  ...
  dive_height = 20
  ...
}

Trading clarity for compactness.

You sound like some kind of rebel.

Frederick

[zapta]

@fcwilt said in Nothing but trouble with Nozzle as Probe and Mesh Bed Comp:

You sound like some kind of rebel.

Yes, it's a radical idea. We are only 20 years into the 21st century.

[fcwilt]

@zapta said in Nothing but trouble with Nozzle as Probe and Mesh Bed Comp:

@fcwilt said in Nothing but trouble with Nozzle as Probe and Mesh Bed Comp:

You sound like some kind of rebel.

Yes, it's a radical idea. We are only 20 years into the 21st century.

Would you consider using simplified XML?

That's what I ended up using for Windows application programming when I wanted to be able to import/export data, including config data.

Frederick

[zapta]

@fcwilt said in Nothing but trouble with Nozzle as Probe and Mesh Bed Comp:

Would you consider using simplified XML?

XML used to be a hot format, but I think that these days formats such as jASON are more popular because of their simplicity.

Here is one example
https://duet3d.dozuki.com/Wiki/Object_Model_of_RepRapFirmware

[T3P3Tony]

@zapta @fcwilt moved your conversation here to keep the original user's request for help on topic.

[fcwilt]

@t3p3tony

Thank you.

[fcwilt]

@zapta said in Structured Configuration Language:

XML used to be a hot format, but I think that these days formats such as jASON are more popular because of their simplicity.

It uses curly braces!

Makes me wonder about the mental state of those that devised it.

Frederick