Yeah, this is more like thousands of lines and polygons of multiple (color) categories, some needing transform matrices to get the right coord values… it was fine with XML.jl just way more work than I would like.
@fattender guess I assumed you were getting GeometryBasics.jl objects but I don’t really know Makie internals.
Having Julia approved/installed is not the same thing as having Julia + all packages approved. A secure environment would not let you reach out to the internet to update the General registry, download packages, etc. A JLL is still an external dependency, it’s just that Pkg makes it super easy to install.
Edit: To further clarify, I’ve worked with several customers who had no problem moving text files (Julia code) into their environment, but moving in an executable binary would require an approval process. This is the situation I am describing.
I noticed that the parse in XML.jl has a different order of argument compared to Base.parse:
It’s not a big issue but slightly confusing when I attempted to replace the EzXML codes.
Is it useful to define more utilities for searching? For example
function Base.findall(xpath::AbstractString, nodes::Vector{Node})
findall(x -> tag(x) == xpath, nodes)
end
function Base.findfirst(xpath::AbstractString, nodes::Vector{Node})
findfirst(x -> tag(x) == xpath, nodes)
end
In EzXML, these are provided via Xpath query
In Base, findall returns indices while in EzXML it returns elements.
Actually I put both orderings in there (it’s one of those things I always get backwards…), but a typo is making the line you highlighted not work. I’ll get it fixed ASAP.
Yes, searching utilities would be good to have, although it’s pretty easy to write fast ones yourself that use LazyNode. I don’t have a lot of experience with XPath myself, but I’d certainly review some PRs.