This project has a lot of overlap with mine (Gemba). Comparison:
Pros:
kcMapViewer - Threading (Planned for Gemba)
kcMapViewer - Native GUI Component
kcMapViewer - Temporary Memory cache of tiles
kcMapViewer - Supports more map formats. (Possible in Gemba, but TOS disallow caching).
kcMapViewer - More Object oriented.
Pros:
Gemba - GeoLocation via PlaceEngine (Mac/Windows) or Core Location (Mac Only)
Gemba - Working on support for OpenCellID location in cooperation with certain mobile 3G routers. (ETA 1 month)
Gemba - Libraries more neatly separated
Gemba - Disk Caching of tiles
Gemba - Tested and working on Mac OS Win32.
Both projects use Synapse, and both plan on LGPL for the libraries, so I think we should combine efforts. kcMapviewer is more of a component, while Gemba is an application which requires a lot of libraries - but there is still a reasonable amount of overlap.
Testing kcMapViewer on Mac OS I found the following trivial issues:
1. Windows unit should be commented out.
2. cthreads needs to be added a lot of places to prevent runtime error 211.
And possibly more major issue:
Tile never seem to load, usually I see a black screen.
Source code to Gemba and Sample application will be posted shortly to:
http://www.galapagossoftware.com/developer-tools/gemba-libraries