-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON parsing? #22
Comments
I considered it at one point. At the moment the xml parsing is very explicit, and generalising the parsing could be a bit of work. But I agree that it ought to also read JSON. I'll try a more serious attempt to get it working. Thanks for raising the issue. |
One very easy (but lame) solution is to convert the JSON to XML and then parse it internally :). |
No problem. I'm not sure how well that would work, and to be honest, I'm not sure how it would work if I did this anyway. I have custom fields in my maps and I don't know how well that'd transfer. |
I don't think custom fields would even be picked up... which I suppose highlights that this class is not much more than an XML wrapper with some convenient datatype casts :). I will keep this issue open though, JSON should be handled somehow, even if it's just as a thin wrapper to XML. |
Will this support the JSON export of Tiled as well?
The text was updated successfully, but these errors were encountered: