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.
-Aude
On Wed, Jun 24, 2009 at 7:00 PM, Audeaude.wiki@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.
On Wed, Jun 24, 2009 at 3:05 PM, Ævar Arnfjörð Bjarmason avarab@gmail.comwrote:
On Wed, Jun 24, 2009 at 7:00 PM, Audeaude.wiki@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:
http://www.mediawiki.org/wiki/Extension:SlippyMap/Development
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@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l
On Wed, Jun 24, 2009 at 7:25 PM, Audeaude.wiki@gmail.com wrote:
On Wed, Jun 24, 2009 at 3:05 PM, Ævar Arnfjörð Bjarmason avarab@gmail.com wrote:
On Wed, Jun 24, 2009 at 7:00 PM, Audeaude.wiki@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:
http://www.mediawiki.org/wiki/Extension:SlippyMap/Development
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.
I've started hacking on the extension:
http://www.mediawiki.org/w/index.php?title=Special%3ACode%2FMediaWiki&pa...
As well as filing some bugs in Bugzilla:
On Wed, Jul 8, 2009 at 9:47 AM, Ævar Arnfjörð Bjarmason avarab@gmail.comwrote:
I've started hacking on the extension:
http://www.mediawiki.org/w/index.php?title=Special%3ACode%2FMediaWiki&pa...
As well as filing some bugs in Bugzilla:
The changes look good. I saw that you added OpenLayers to the svn. With OpenLayers licensed under a BSD-style license rather than GFDL, is it okay to distribute the code with our extension?
I expect to have time to work on the code over the next few days. I might work on developing custom OpenLayers controls that work suitably when the maps are small, and work on how they are laid out. I can also work on the pop-up map and on the WMS support.
-Aude
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l
On Wed, Jul 8, 2009 at 3:19 PM, Audeaude.wiki@gmail.com wrote:
On Wed, Jul 8, 2009 at 9:47 AM, Ævar Arnfjörð Bjarmason avarab@gmail.com wrote:
I've started hacking on the extension:
http://www.mediawiki.org/w/index.php?title=Special%3ACode%2FMediaWiki&pa...
As well as filing some bugs in Bugzilla:
The changes look good. I saw that you added OpenLayers to the svn. With OpenLayers licensed under a BSD-style license rather than GFDL, is it okay to distribute the code with our extension?
Yes it's fine. We're just using it as a library but even if we weren't the GPL and BSD license are compatible.
I expect to have time to work on the code over the next few days. I might work on developing custom OpenLayers controls that work suitably when the maps are small, and work on how they are laid out. I can also work on the pop-up map and on the WMS support.
OK good stuff. I look forward to seeing it.
I've been seeing some strange issues with the conditional adding of the slippymap parser tag / the js/css headers. It might be that the parsercache reacts badly to conditionally including it depending on whether the article text includes "slippymap".
Hopefully this is something we can do away with completely once Christian Becker can implement conditional loading of OpenLayers. Then the JS required to display maps could just be included for the whole site (and would hopefully only be ~10-20 lines) and when a map was used in an article (and the user clicked on the map) the full OL library could be pulled in and cached.
B.t.w. Aude you should set your editor to indent with tabs instead of spaces, I fixed this in your most recent commit:
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/52919
This might help configure your editor correctly:
http://www.mediawiki.org/wiki/Manual:Coding_conventions
I don't care about coding styles one way or the other. But it should be consistent so it doesn't look bad when rendering tabs as something other than 8 spaces.
I've been making a lot more changes to it in the last 2 days:
http://www.mediawiki.org/w/index.php?title=Special%3ACode%2FMediaWiki&pa...
Some things are now off the bug list and some new things are there: