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.

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

client-side image ordering interface #116

jywarren opened this issue Feb 18, 2015 · 3 comments


Copy link

commented Feb 18, 2015

this will take some pretty careful interface design work.

  • the active image would "highlight" in the Images tab
  • a "move to top" button on the in-map image popup or in the tab
  • or drag and drop (but that might be overkill, hard to know)

Ideal result: the user can specify which image is on top of a "finished" map.

Will this be tracked separately in each map? Probably, otherwise we'd have to store global order as a decimal in the db, and allow endless subdividing. Also, would "bring to top" just bump it one integer higher than the highest image in the current map, but lower than the next-highest image globally? That could create some odd behaviors.

@jywarren jywarren changed the title image ordering client-side image ordering interface Jul 22, 2015

This comment has been minimized.

Copy link

commented Jul 27, 2015

The problem: It used to be that in Mapknitter1 after you reloaded the browser, the smallest image would draw on top. In Mapknitter2 this is no longer reliable. The smallest and highest-res images become inaccessible under larger images -- they can't be "clicked" on them in the graphic interface.

The suggested solution: Use the list of named images in the image tab to select / activate / bring-to-top-of-draw-order-in-the-map. The Green button next to image names on the image tab does this sometimes -- is this available to all users?

screen shot 2015-07-27 at 12 26 51 pm


This comment has been minimized.

Copy link
Contributor Author

commented Jan 8, 2018

Opening an issue for this in Leaflet.DistortableImage: publiclab/Leaflet.DistortableImage#84


This comment has been minimized.

Copy link
Contributor Author

commented Jan 8, 2018

We'll also need a way to store the order on the server side; this means:

  1. a new field in the map table to store a list of ordered image ids, something like order: 45,15,27,57,888
  2. a way to translate that stored order into a correctly-displayed set of images when opening a map page
  3. a way to update the order each time someone changes the order of an image

So this is a multi-part issue in need of breaking up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.