You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For anyone that knows Mapnik's XML styling language, what mess.js does is total black magic. So, for the potential audience of current Mapnik users it would be great to offer an XML preview window. This is key because the combo of sticking compiled XML in a hidden cache and obscuring the name with base64 encoding means that actually finding the file you have created is going to be non-starter.
If we implement this it would ideally be done not by reading the xml written directly by mess.js but rather by serializing the XML off the mapnik.Map object so that the XML is properly pretty printed. I've just exposed the ability to do this here: mapnik/node-mapnik@1d22fac
The text was updated successfully, but these errors were encountered:
Yes, I agree, I think I should overhaul node-mapnik to expose a CamelCase api. for now I've fixed just the to_string method since this is new and I doubt anyone has found it yet: mapnik/node-mapnik@cc719b2
For anyone that knows Mapnik's XML styling language, what mess.js does is total black magic. So, for the potential audience of current Mapnik users it would be great to offer an XML preview window. This is key because the combo of sticking compiled XML in a hidden cache and obscuring the name with base64 encoding means that actually finding the file you have created is going to be non-starter.
If we implement this it would ideally be done not by reading the xml written directly by mess.js but rather by serializing the XML off the mapnik.Map object so that the XML is properly pretty printed. I've just exposed the ability to do this here: mapnik/node-mapnik@1d22fac
The text was updated successfully, but these errors were encountered: