Extension:Semantic Maps/Future

Future work on Semantic Maps

Feel free to add new feature requests to the new proposals section. Please review the turned down proposals first. Adding your vote or objection to proposals will help determining which ones will get the priority. If you have any comments on the already accepted or turned down proposals, please add them to the talk page, but refer from adding them to the lists themselves.

Accepted to-do's
Items that have strikethrough have been completed/fixed.

Refactoring

 * Restructure the Query Printer classes


 * Make form input classes weakly typed

Bug fixes

 * Mapping formats get added multiple times, as can be seen in the dropdown in Special:Ask - see here


 * Yahoo! Maps and OpenLayers should handle the "icon=" parameter that can come from Semantic Compound Queries, as Google Maps already does


 * Map queries with no results show a blank map in Google Maps, and white space in Yahoo! Maps - they should probably display the "default=" value if that's passed in the query, or nothing if there's no default value


 * Setting a map form input to 'mandatory' doesn't work, and leads to a Javascript error; it appears that the map input and span IDs require the use of the "$sfgFieldNum" global variable, instead of the current "elementNamePrefix" setup

New features

 * Ability to define custom overlays for OpenLayers


 * Functionality similar to Tetherless Map (list of points next to maps and same for layers in case of an OpenLayers map). Example.


 * Multi geocoder integration with the semantic map queries

Bugs

 * Marker popups in Yahoo! Maps show up with a white background under them (probably a CSS issue)
 * The Google Maps form input should zoom in when the user looks up an address - see here, and enter any value. This seems to work fine for Yahoo! Maps, though.