Ctx & XML

Lukáš Procházka

10 Dec 2014 10 Dec '14

10:08 p.m.

Hello, I'm having problem using LuaXml library with Ctx, both using Lua ver. 5.2. LuaXml works fine with Lua standalone programs/scripts; but something weird occurs when used from within Ctx (e.g. a .xml file can be read successfully from standalone Lua with LuaXml lib; but the same code doesn't give the desired result when used in combination with Ctx; a problem might be version mismatch - I'm still using both Lua 5.1 and 5.2 including 3rd party modules in my scripts - but my latest tests with Ctx & LuaXml should have avoid this; or namespace mismatch...?). Anyway, does native Ctx XML API (has it its own namespace, like 'context.xml'?) provide a function to load a .xml file and to return its XML tree as a table, with nodes (as a table with node attributes as table members) in a proper sequence... something like LuaXml's 'xml.load("file.xml")' does? Or how to achieve this in a best way under Ctx: XML file -> Lua table/tree? Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038

Show replies by date

Hans Hagen

11 Dec 11 Dec

1:24 a.m.

On 12/10/2014 11:08 PM, Lukáš Procházka wrote:

...

Hello,

I'm having problem using LuaXml library with Ctx, both using Lua ver. 5.2.

LuaXml works fine with Lua standalone programs/scripts; but something weird occurs when used from within Ctx (e.g. a .xml file can be read successfully from standalone Lua with LuaXml lib; but the same code doesn't give the desired result when used in combination with Ctx; a problem might be version mismatch - I'm still using both Lua 5.1 and 5.2 including 3rd party modules in my scripts - but my latest tests with Ctx & LuaXml should have avoid this; or namespace mismatch...?).

I don't know (and as we have quite some code on-board I don't care too much either about clashes in namespaces).

...

Anyway, does native Ctx XML API (has it its own namespace, like 'context.xml'?) provide a function to load a .xml file and to return its XML tree as a table, with nodes (as a table with node attributes as table members) in a proper sequence... something like LuaXml's 'xml.load("file.xml")' does?

I assume that you also want the content of elements, not just the attributes.

...

Or how to achieve this in a best way under Ctx: XML file -> Lua table/tree?

It all depends on what kin dof table you want (if the content is an indexed table and attributes keys then you have the problem that the element cannot be a key too as it can clash) .. anyway, it's no big deal to provide a stupid table, so I can provide something because after all the loaded xml file is a table already. local x = xml.load("file.xml") local t = xml.totable(x) where x is an index/hash mix plus _tag, _type and _namespace fields as well (after all I assume that you need to know that too). (btw, I bet that you can do what you want with the existing functionality as well, so there is not much benefit in such a table) Probably in the next upload, Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Procházka Lukáš Ing. - Pontex s. r. o.

7:33 a.m.

Hello, On Thu, 11 Dec 2014 02:24:24 +0100, Hans Hagen wrote:

...

On 12/10/2014 11:08 PM, Lukáš Procházka wrote:

I assume that you also want the content of elements, not just the attributes.

Yes...

...

...
Or how to achieve this in a best way under Ctx: XML file -> Lua table/tree?

It all depends on what kin dof table you want (if the content is an indexed table and attributes keys then you have the problem that the element cannot be a key too as it can clash) .. anyway, it's no big deal to provide a stupid table, so I can provide something because after all the loaded xml file is a table already.

It would be great.

...

local x = xml.load("file.xml")

local t = xml.totable(x)

where x is an index/hash mix plus _tag, _type and _namespace fields as well (after all I assume that you need to know that too).

(btw, I bet that you can do what you want with the existing functionality as well, so there is not much benefit in such a table)

Probably in the next upload,

... Means - some functionality (for me to test or to play with) might be available tomorrow morning?

...

Hans

BTW, I prepared a really-simple-XML-test which shows XML -> Lua table/tree conversion, which I'd like to achieve (and which (approx.) provides LuaXml lib). ---- XML <a aaa="AAA"> c </a> ---- ---- Lua representation { [0] = "a", -- Element name { [0] = "b", -- Element name -- No nested members bbb = "B1", -- Atts }, { [0] = "b", -- Element name { "c", }, -- Nested member bbb = "B2", -- Atts }, aaa = "AAA", -- Atts } ---- Thanks again. Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038

Hans Hagen

9:10 a.m.

On 12/11/2014 8:33 AM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:

...

Hello,

On Thu, 11 Dec 2014 02:24:24 +0100, Hans Hagen wrote:

...
On 12/10/2014 11:08 PM, Lukáš Procházka wrote:

I assume that you also want the content of elements, not just the attributes.

Yes...

...
...
Or how to achieve this in a best way under Ctx: XML file -> Lua table/tree?

It all depends on what kin dof table you want (if the content is an indexed table and attributes keys then you have the problem that the element cannot be a key too as it can clash) .. anyway, it's no big deal to provide a stupid table, so I can provide something because after all the loaded xml file is a table already.

It would be great.

...
local x = xml.load("file.xml")

local t = xml.totable(x)

where x is an index/hash mix plus _tag, _type and _namespace fields as well (after all I assume that you need to know that too).

(btw, I bet that you can do what you want with the existing functionality as well, so there is not much benefit in such a table)

Probably in the next upload,

.... Means - some functionality (for me to test or to play with) might be available tomorrow morning?

...
Hans

BTW, I prepared a really-simple-XML-test which shows XML -> Lua table/tree conversion, which I'd like to achieve (and which (approx.) provides LuaXml lib).

---- XML <a aaa="AAA"> c </a> ----

---- Lua representation { [0] = "a", -- Element name { [0] = "b", -- Element name -- No nested members bbb = "B1", -- Atts }, { [0] = "b", -- Element name { "c", }, -- Nested member bbb = "B2", -- Atts }, aaa = "AAA", -- Atts } ----

that already makes assumptions that it's just data ... the context xml parser is a roundtrip one so a bit more control is provided: local str = [[ <?xml version="1.0" ?> <a one="1">  c > d </a> ]] I've added some flags: inspect(xml.totable(xml.convert(str))) table={ { "xml version=\"1.0\" ", ["_type"]="instruction", }, "\ ", { "\ ", { " rubish ", ["_type"]="comment", }, "\ ", { ["_tag"]="b", ["_type"]="_element", ["two"]="1", }, "\ ", { "\ c > d\ ", ["_tag"]="b", ["_type"]="_element", ["two"]="2", }, "\ ", ["_tag"]="a", ["_type"]="_element", ["one"]="1", }, ["_type"]="root", } inspect(xml.totable(xml.convert(str),true)) table={ { "xml version=\"1.0\"", ["_type"]="instruction", }, { { "rubish", ["_type"]="comment", }, { ["_tag"]="b", ["_type"]="_element", ["two"]="1", }, { "c > d", ["_tag"]="b", ["_type"]="_element", ["two"]="2", }, ["_tag"]="a", ["_type"]="_element", ["one"]="1", }, ["_type"]="root", } inspect(xml.totable(xml.convert(str),true,true)) table={ { [0]="a", { [0]="b", ["two"]="1", }, { [0]="b", "c > d", ["two"]="2", }, ["one"]="1", }, } The last one is yours. Of course in all cases you loose info that is present in the original representation (where you can also access the nodes via expressions). Don't expect additional helpers for this 'totable' variant. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Procházka Lukáš Ing. - Pontex s. r. o.

11:25 a.m.

Hello Hans, On Thu, 11 Dec 2014 10:10:16 +0100, Hans Hagen wrote:

...

that already makes assumptions that it's just data ... the context xml parser is a roundtrip one so a bit more control is provided:

local str = [[ <?xml version="1.0" ?> <a one="1">  c > d </a> ]]

I've added some flags:

inspect(xml.totable(xml.convert(str)))

table={ { "xml version=\"1.0\" ", ["_type"]="instruction", }, "\ ", { "\ ", { " rubish ", ["_type"]="comment", }, "\ ", { ["_tag"]="b", ["_type"]="_element", ["two"]="1", }, "\ ", { "\ c > d\ ", ["_tag"]="b", ["_type"]="_element", ["two"]="2", }, "\ ", ["_tag"]="a", ["_type"]="_element", ["one"]="1", }, ["_type"]="root", }

inspect(xml.totable(xml.convert(str),true))

table={ { "xml version=\"1.0\"", ["_type"]="instruction", }, { { "rubish", ["_type"]="comment", }, { ["_tag"]="b", ["_type"]="_element", ["two"]="1", }, { "c > d", ["_tag"]="b", ["_type"]="_element", ["two"]="2", }, ["_tag"]="a", ["_type"]="_element", ["one"]="1", }, ["_type"]="root", }

inspect(xml.totable(xml.convert(str),true,true))

table={ { [0]="a", { [0]="b", ["two"]="1", }, { [0]="b", "c > d", ["two"]="2", }, ["one"]="1", }, }

The last one is yours. Of course in all cases you loose info that is present in the original representation (where you can also access the nodes via expressions). Don't expect additional helpers for this 'totable' variant.

this is great. I'll try it... Thank you. BTW: In your example, you are using the following enum of "_type": "instruction", "comment", "_element", <-- REALLY UNDERSCORE here? "root", Best regards, Lukas

...

Hans

-- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038

Hans Hagen

1:09 p.m.

On 12/11/2014 12:25 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:

...

BTW: In your example, you are using the following enum of "_type":

"instruction", "comment", "_element", <-- REALLY UNDERSCORE here? "root",

of course, as you can have an attribute with name 'element' Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

3663

Age (days ago)

3664

Last active (days ago)

List overview

Download

5 comments

3 participants

participants (3)

Hans Hagen
Lukáš Procházka
Procházka Lukáš Ing. - Pontex s. r. o.

Ctx & XML

Lukáš Procházka

Hans Hagen

Procházka Lukáš Ing. - Pontex s. r. o.

Hans Hagen

Procházka Lukáš Ing. - Pontex s. r. o.

Hans Hagen

tags

participants (3)