Open alanlivio opened 6 years ago
Maybe, another related project: https://github.com/danielsm/Lua2NCL
Just a question: is the ideia to parse directly from a Lua table? Or to convert from Lua table -> XML (or DOM) -> Execution Model.
I believe it would be easier (and would avoid duplicated code) if there is only one input format (or the XML or the Lua table). The other formats should be translated to it.
Just a question: is the ideia to parse directly from a Lua table? Or to convert from Lua table -> XML (or DOM) -> Execution Model.
Today, PaserLibXML does XML -> Execution Model The idea of ParserLuaTable is LuaTable -> Execution Model
I believe it would be easier (and would avoid duplicated code) if there is only one input format (or the XML or the Lua table).
Agree. We should discuss better about this.
The other formats should be translated to it.
One motivation of this work is integrate the DietNCL (internally use a LuaTable format) into ginga. It may enable do XML EDTV -> LuaTable RAW (from DietNCL) -> ExecutionModel.
To the tests generation, maybe, a simple LuaTable to XML convertion such as [1] could help.
[1] https://gist.github.com/robertogerson/eaca97e44dba8aad48f8cbdeb8cb1f76
Today, lib/PaserLibXML convert NCL EDTV in XML and convert it to an lib/Document object.
The lib/ParserLuaTable will load a lua table and convert it to a lib/Document object.
Possible usage: ginga -l main.lua
Benefits:
[1] https://dl.acm.org/citation.cfm?id=3126866