4.0 wish list
Opened this issue · 8 comments
- Make new panel controls addable through API, not using hacks
- Make geocoder UI completely separate from
L.Routing.Plan - Organize code more like normal CommonJS/Node.js (see for example MapboxGL)
- Remove confusion regarding option
addWaypoints - Make i18n easier and clearer
- Better mobile support
- Put UI in separate elements, possibly outside the map (#135)
- Use DocumenationJS or similar for docs
- Make it easier to add custom functionality to lines (#117)
- Events while dragging (#114)
- Use delegated events where applicable (itinerary hover/click, for example)
- Better builtin error handling / reporting
- Use GeoJSON for communicating routes, waypoints, etc., rather than formats only used by LRM
- Hide control when no geocoder is used and no route is shown (#198)
- Add waypoints by dragging on the line (broken with Leaflet-master)
- Make it possible to maximize/minimize control, as well as hide/show it
3.0 will be developed on the develop branch.
Version 3.0 was released to support OSRM's new API, so I've updated the issue title. This ticket is really about "next major revision" of LRM's API.
Full support for Leaflet v1 is very important.
@sourc7 the develop branch has full Leaflet 1.0.0 support, AFAIK. Any help very welcome, though!
Would it be possible to add some sort of sorting functionality to the waypoint divs? For example, functionality similar to the jquery sortable.
@WilliamWalker hi there, if you mean making waypoints draggable to rearrange, I'm not likely to include it in the core of LRM. Having said that, it's really easy to add if you use for example Sortable (or maybe jquery sortable, never tried that one).
For an example, look at this issue and scroll down a bit to see some example code: #276
Perfect, that's exactly what I was looking for. Thanks again!