Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

4.0 wish list #187

Open
8 of 16 tasks
perliedman opened this issue Dec 28, 2015 · 8 comments
Open
8 of 16 tasks

4.0 wish list #187

perliedman opened this issue Dec 28, 2015 · 8 comments

Comments

@perliedman
Copy link
Owner

perliedman commented Dec 28, 2015 •
edited by curtisy1
Loading

  • 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 (Append interfaces to user defined HTMLElements #135)
  • Use DocumenationJS or similar for docs
  • Make it easier to add custom functionality to lines (Make adding listeners (for example click) to L.Routing.Line easier #117)
  • Events while dragging (Get route data 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 ([Graphical bug] White bar of the container #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
@perliedman
Copy link
Owner Author

3.0 will be developed on the develop branch.

@perliedman perliedman mentioned this issue Feb 11, 2016
Open
@perliedman perliedman mentioned this issue Feb 25, 2016
Closed
@perliedman perliedman changed the title 3.0 wish list 4.0 wish list Apr 26, 2016
@perliedman
Copy link
Owner Author

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.

@sourc7
Copy link

sourc7 commented Jun 13, 2016 •
edited
Loading

Full support for Leaflet v1 is very important.

@perliedman
Copy link
Owner Author

@sourc7 the develop branch has full Leaflet 1.0.0 support, AFAIK. Any help very welcome, though!

@perliedman perliedman mentioned this issue Jun 22, 2016
Closed
@WilliamWalker
Copy link

WilliamWalker commented Sep 12, 2016 •
edited
Loading

Would it be possible to add some sort of sorting functionality to the waypoint divs? For example, functionality similar to the jquery sortable.

@perliedman
Copy link
Owner Author

@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

@WilliamWalker
Copy link

Perfect, that's exactly what I was looking for. Thanks again!

@mstock mstock mentioned this issue May 2, 2018
Merged
@curtisy1 curtisy1 pinned this issue Sep 18, 2021
@curtisy1
Copy link
Collaborator

Development continues on the typescript branch. Once all the features (and a few more) are implemented, I'll merge those into 4.0 to create a beta release. Also see #637 for details and updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@perliedman @WilliamWalker @sourc7 @curtisy1