Backbone.Geo for models and Backbone.Leaflet for views?

[elf-pavlik]

Howdy!

If models only have GeoJSON specific features I don't see need to call them Leaflet. In a future they could still work using any other map libraries like http://modestmaps.com

For views it seams to make lots of sense if they introduce Leaflet specific concepts...

We use Backbone for #geo stuff with modestmaps in:
https://github.com/apollo-ng/dspace-client

and with leaflet in:
https://github.com/elevate-festival/neokarto-party

Soon we should merge those code bases but i would like to keep models agnostic to which mapping library we use in views!

I'll try to take a better look at your code and maybe we cold collaborate a bit on it...

Cheers :)

[LuizArmesto]

Hi, thanks for your suggestion.

That makes sense. The idea is to keep GeoModel and GeoCollection agnostic and decoupled from any map lib, so using another namespace without a reference to the map lib will make this more clear.

What do you think about the changes below?

Rename the main namespace (and maybe the project) to Backbone.Geo (I found no other project using this namespace)

Backbone.Leaflet.GeoModel will be Backbone.Geo.Model
Backbone.Leaflet.GeoCollection will be Backbone.Geo.Collection
Backbone.Leaflet.MapView will be Backbone.Geo.LeafletMapView

This way, will be possible to reuse Geo.Model and Geo.Collection with other libs.

Cheers

[elf-pavlik]

I like your suggestion of using map library agnostic namespace like Backbone.Geo 👍

We may do major changes to DSpace code and maybe already take advantage of your work, some relevant discussion: apollo-ng/dspace-app-apollong#103

I must admit that still not having clear idea how to approach Leaflet, Modestmaps etc. namespacing
maybe Backbone.Geo.Leaflet.Map and other direct mappings to http://leafletjs.com/reference.html ?

BTW I have on my TODO list investigating http://mapstraction.com and hopefully connecting with people developing it!

[megawac]

👍