| | 1 | = MapServer Toronto Code Sprint 2009 = |
| | 2 | |
| | 3 | == Agenda == |
| | 4 | |
| | 5 | == Minutes, Actions, Decisions == |
| | 6 | |
| | 7 | === 1. XML mapfiles === |
| | 8 | |
| | 9 | * A draft RFC is at http://mapserver.org/development/rfc/ms-rfc-51.html |
| | 10 | * There are concerns about the use of the CWXML library and the benefits of a binary encoded format |
| | 11 | * The need we are trying to address is the ability to build MapFile Editors that would be facilitated by the existence of a XML mapfile format (since the current mapfile format makes it impossible to write a forward-compatible parser) |
| | 12 | * There are concerns about having to support another set of parsing functions. Just keeping the existing mapfile.x read/write functions in sync is already a challenge, so adding another set of reader/writer functions for XML will just make this worse. |
| | 13 | * Conclusion: After discussion, it was decided that for the time being we should '''develop a XML schema and a XSLT to convert from XML to text mapfile'''. If the new XML format takes off then we may consider implementing support for it directly in MapServer in a future release. |
| | 14 | |
| | 15 | |
| | 16 | |
| | 17 | === 2. Graphical rendering === |
| | 18 | |
| | 19 | * Thomas presented the approach of rendering plugins |
