-
Notifications
You must be signed in to change notification settings - Fork 385
Propose name changes #30
Comments
Named needs to be named - modestmaps looks for renderer could be valid, though it does refer to the factory pattern markers.features refers to the
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 |
|
|
Ah I see. Yes, renderer |
Technically it's like an |
We're supporting camelCase in v1 and such. |
These are upstream but I wanted to discuss them here:
map
layer.named -> layer.name
Named in the past tense just seems weird - even for what it does.
markers
markers.factory
->markers.render
factory to me is a pretty internal name. "Render" qualify's what it does: renders the object out as html
or re-renders them out
markers.features -> markers.data
Features is such a geojson spec name. "data" seems like a more appropriate name for how we are using features.
markers.addCallback -> markers.onEvent
This feels more clear to me on some event specified in the first argument, do something (callback)
markers.removeCallback -> markers.removeEvent
interaction.hide_on_move -> interaction.hideOnMove
underscores just dont sit right with me .. we should camelCase right?
interaction.formatter -> interaction.template
Debatable change.
ease
ease.t -> ease.toPoint
More clear
The text was updated successfully, but these errors were encountered: