Support FIX50 about fix-decoder HOT 4 OPEN

Q: Both of these really need to involve generating the data.js content from XML dictionaries (e.g. https://github.com/quickfix/quickfix/tree/master/spec). @drewnoakes How did you seed the very first data.js ?

from fix-decoder.

How did you seed the very first data.js ?

I don't remember unfortunately. Most likely I cobbled something crude together to convert XML to JSON.

Having a file-per-version makes sense. Perhaps we have a build step to do this conversion in a repeatable fashion.

from fix-decoder.

OK. The linked quickfix repo already contains XSL for converting the dictionaries into bindings in multiple languages so there's a quickstart right there. Actually... we could use git submodules to pull in their spec directory (or some more canonical version) instead of yet another copy of the files.
I've made decent progress on this (and a host of tidying) already but it will be many months before I can externalise this from my employer.

from fix-decoder.

The submodule idea is a good one.

I've made decent progress on this (and a host of tidying) already but it will be many months before I can externalise this from my employer.

Whatever you're able to share will certainly be appreciated by the wider FIX development community.

from fix-decoder.