DSpace.API.Xxx & DSpace.UI.Xxx [former: GeoFeed & Overlay - document conceptual distinction]

[elf-pavlik]

at this moment i see in overlayType definitions {writable: true} which seams to me more of a property related to GeoFeed which particular Overlay simply presents

i would like to discuss and document conceptual distinction between GeoFeed model and Overlay view

[elf-pavlik]

@chron0 @nilclass @alice-wl let's do sprint on splitting DSpace.API and DSpace.UI as i mentioned in #35 (comment)

i can help avoid confusions and all UI related issues can stay in a repo of particular version of UI

[elf-pavlik]

@jrbaldwin I would also like to check out your work on https://github.com/opentechinstitute/TidePools-Mobile

while currently we focus on Backbone we could also coordinate with your work on Angular, we could align at least data schema and try to keep domain logic in sync as much as possible :)

@jnny we'll get chance to chat about DSpace & Tidepools in Berlin soon \o/

[elf-pavlik]

@chron0 in issue linked above i started chatting with @LuizArmesto who works on Backbone.Leaflet (maybe soon Backbone.Geo ;) about ways of staying agnostic to mapping library so different implementations of what i refer here to as DSpace.UI can use Leaflet, Modestmaps, you name it and pick it :)

we could then adapt to pull in Backbone.Geo.Model and Backbone.Geo.Collection as dependencies of DSpace.API ...

@nilclass we may really need your expertise here 🎱

[elf-pavlik]

I've just set labels on issues with API and UI + created next milestone in 2 weeks to take care of this major change + cherry-pick from https://github.com/elevate-festival/neokarto-party

[elf-pavlik]

@nilclass i consider not using $ in API part and just overwrite all backbone sync request with something like: https://github.com/substack/hyperquest see: http://www.vimeo.com/62988591?t=12m30s