Propose name changes about mapbox.js HOT 6 CLOSED

Named needs to be named - modestmaps looks for .name as a property, and as such it can't be a function without very dangerous code, or a modestmaps tweak.

renderer could be valid, though it does refer to the factory pattern

markers.features refers to the features member of a GeoJSON feature collection, and markers.js aims to continue to support GeoJSON type objects internally, even if it supports other 'converters' to/from that format. data also could be confused with the data member in TileJSON.

addCallback and removeCallback are made to mirror modestmaps; I'd rather keep these continuous; they mirror addEventlistener in HTML and have been established for a while.

Hide on move, sure, works for me.

Template - no; this isn't templating, really: it doesn't take a template as an argument.

easey.toPoint I'd rather not use Point because it could be easily confused with MM.Point, which this has nothing to do with. open to other namings though

from mapbox.js.

• Perhaps setPosition ? instead of toPoint ?
• I know factory refers to the factory pattern but I feel like an api shouldn't bear its name - internally yes but not outwardly. the word, "render" attributes more closely to what it does I think.

from mapbox.js.

render is also a verb; you would expect markers.render() to render the markers. it would have to be markers.renderer() right?

from mapbox.js.

Ah I see. Yes, renderer

from mapbox.js.

Technically it's like an x value in http://en.wikipedia.org/wiki/Interpolation . Position is also kind of an overloaded term; unless we can find something that's accurate and specific, I don't really want to change this (plus it's a pro feature anyway)

from mapbox.js.

We're supporting camelCase in v1 and such.

from mapbox.js.