I've suddenly had an influx of interest from many new developers wishing to
help out with GMap.Net control. I'm now trying to get a much more formal
and comprehensive Task list, as well as encouraging bug reports - hopefully
this will aid communication amongst our small community of GMap.Netdevelopers.
There's plenty of areas that require work at the moment, please feel free to
help out with anything. (listed in order of importance)
1- Reverse engineering obfuscated Google Map API Javascript classes (see my
latest blog post on the project website)
2- Custom javascript toString methods for each class (requires the reverse
engineering, 1), and the parsing of these strings by the .Net classes. [I'm
working mainly on this problem at the moment]
3 - Databinding. Earlier versions of the control only accepted basic
GMarker data through the main GMap2 class. I expanded this to all GOverlay
classes, using a sort of factory pattern and custom Databinding classes -
see OnDataBinding(EventArgs e) in GMap2.cs.
And now it is broken.
4 - Ajax. A couple of people have reported a bug with other Ajax controls -
see the bug tracker.
5 - NUnit testing. it would be great to see unit testing to ensure quality
code.
6 - FxCop. Framework conformance, there are some 300 nonconformance issues
with the code. It would be great to see these reduced by cleaning up the
.Net code.
There is indeed tons to do, I hope the massive list hasn't scared you off!
Just upload your patches to the sourceforge.net project page, and I'll
review them and add your changes to the SVN.
Good luck,
Iain (sprocketonline)
|
