<br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style><br>
<div class="gmail_quote">2010/3/19 Mulone <span dir="ltr"><<a href="mailto:mulone@rome.com">mulone@rome.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
In relation to mapscript, would it be possible/interesting to isolate the<br>
classes dealing with the mapfile leaving all the trick bindings out?<br>
<br>
I mean, in the end what a lot of developers need is a simple tree to handle<br>
and generate valid mapfiles, without messing with other things. I'm finding<br>
the java binding quite tricky to integrate because I'm working on a<br>
framework (Grails) and I don't know how to make the DLL work in my set up.<br>
<br></blockquote><div><br>Mulone,<br><br>I don't exactly understand, what you mean. The mapscript functions are invoking the functions exposed by those dll-s (including mapscript.dll, libmap.dll, proj.dll and many more), therefore having those dll-s installed is required for the interface to operate.<br>
<br><br>Best regards,<br><br>Tamas<br></div></div><br>