Epseelon
This is a Release Candidate of MobiMap and a few known issues need to be fixed before we get to 1.0 final release.
Most map data provider expose their maps cut down into tiles measuring 256x256 pixels. This might be suitable for the web Javascript API, but for mobile applications, it is not really optimal because most of the time, the screen is only big enough to display 2 or 3 tiles, with a lot of waste, that is data that is loaded but never displayed.
Given the current data rate charged by most mobile carriers, we need to optimize data loading and one strategy is to use smaller tiles in order to load less data. Google obviously has such smaller tiles somewhere since they're using them for their Google Maps Mobile application, but it is not documented anywhere. So a solution would be to have some sort of a proxy server cutting tiles on the fly, provided that this is legal.
For now, the cache mechanism we're using is very simplistic: it's just a First-In-First-Out cache where tiles exceeding the cache size are deleted automatically.
We need to have a cache that takes into account the way the user moves around the map.
