Closed jpic closed 12 years ago
I actually kind of prefer pre loading. When initially looking at this problem I thought of writing my own with geobytes, but to me the end user experience is better with indexed db tables than with calls to an external API.
If we needed to do extremely complex things (like django-cites enables) then it may be better to let their servers handle the processing and just give us the data, but as the app stands right now it seems more efficient to have these tables.
Actually Geobytes won't allow to make the autocomplete we want so it's out of the question for now...
... however I need support for the autocomplete to use an API, but we're going to keep the current pattern (using contrib, one project with restframework urls, another with remote autocomplete).
Thanks for your feedback !
We might as well include an autocomplete which uses geobytes free api:
http://www.geobytes.com/free-ajax-cities-jsonp-api.htm
Rather than, pre-loading a database with insane amounts of cities/countries.