On Wed, Jun 24, 2009 at 3:05 PM, Ævar Arnfjörð Bjarmason
<avarab(a)gmail.com>wrote;wrote:
On Wed, Jun 24, 2009 at 7:00 PM,
Aude<aude.wiki(a)gmail.com> wrote:
The SlippyMap extension code has been updated on
the MediaWiki svn.
It's very much a work in progress, but the code is now split up into
class
files:
* SlippyMap.class.php - a general slippy map class
* SlippyMap.worldwind.php - extends the general slippymap class; this is
still in development
* SlippyMap.hooks.php - put the hooks here
* SlippyMap.php - the main extension file; configuration options can be
put
here
Other files:
* SlippyMap.js
* SlippyMap.css
I'm also working on some special pages:
* One is Special:MapServices - It's not ready to commit, but it allows
configuration of what map types are allowed on a wiki, and which sources.
For Wikipedia, it will be restrictive, probably just to our own OSM
servers. For other, smaller wikis, one might like to include maps from
other WMS sources. On one of my own projects, I have GeoServer and
PostGIS
setup, generating my own custom maps and want to
include them in my own
wikis.
* Another could be Special:CreateMap to allow users to determine the map
parameters (e.g. bounding box, center point, zoom level) and generate
wiki
code. Or this could be done as a popup window or
some other
implementation. I know there already is a "get wiki code" button on the
SlippyMap, but that requires one to add a slippy map to the page, then
zoom/pan around, get the wikicode via the button, then update the
wikicode.
I don't think that's the best approach.
Also to be done is configuration of OpenLayers, to include just the
JavaScript files that are needed for the particular map types we are
using,
rather than the entire OpenLayers code.
There are plenty of other things to be done.
You're doing a great job. I haven't had time to contribute until now
but now some other hobby projects I was doing are mostly finished.
What's the best list of tasks that need to be done currently? The
buglist on Google code (and can I move it over to bugzilla?:), or
something else.
At this point I think we might want to do more documenting and agree on
features we want and how we want them implemented. It could be done on a
wiki page, such as this:
It helps me to think through things like this, determine what features,
parameters, and pieces of code are general and apply to all slippy maps,
regardless of type of map (e.g. OSM, satellite, other WMS). Other things
should be put into subclasses, and handled differently depending on map
type.
Same sort of idea applies to other features that the extension will have.
I suppose a general to-do list could go on the wiki, and then when we have
specific bugs or feature requests, then they could go in bugzilla.
-Aude
_______________________________________________
Maps-l mailing list
Maps-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/maps-l