Comments (10)
@sergeydolgov1 @jacobmclaws Re dragging to reposition; is there any concern that users will accidentally reposition points, while dragging the map for example? I believe moving points once they've been added will be very rare; in that case, should we require users to do something first to enter an "editing" state. One option could be a button "Edit position" on the feature details page that will show crosshairs for the user to relocate the point. This would also bring the edit flow closer to add flow.. Any thoughts?
@gino-m @jacobmclaws I think that is a valid point. Perhaps the flow can be 1) Click on a "Edit position" button --> 2) drag point to reposition --> 3) Click "Save changes" button (there may also be "Cancel" button that resets point location to its initial position)
from ground-platform.
@gino-m @DaoyuT
Sharing the latest mocks (see attached)
Question: What are the actions that are available to users when they select "Edit" mode? Are they able only to rename points/features? If that's the case, perhaps we should change "Edit" to "Rename"?
Reposition Feature Flow.pdf
from ground-platform.
Hi @DaoyuT! As this is related to the map, could you take this one on?
@jacobmclaws, what would a potential flow for editing the location of an existing pin look like?
from ground-platform.
Latest UXD Suggestions:
A) Point Hover State:
from ground-platform.
Latest UXD Suggestions:
B) Point Drag State:
from ground-platform.
@sergeydolgov1 @jacobmclaws Re dragging to reposition; is there any concern that users will accidentally reposition points, while dragging the map for example? I believe moving points once they've been added will be very rare; in that case, should we require users to do something first to enter an "editing" state. One option could be a button "Edit position" on the feature details page that will show crosshairs for the user to relocate the point. This would also bring the edit flow closer to add flow.. Any thoughts?
from ground-platform.
@jacobmclaws wdyt?
from ground-platform.
@sergeydolgov1 @jacobmclaws Since we won't have a "Features List" per se at the moment, where should the "Move" button be placed? Would this go in the panel header when the feature is selected and we're showing the observation list? @DaoyuT is about to start working this.
from ground-platform.
@gino-m @jacobmclaws @DaoyuT
Sharing the latest Mocks:
-
Selected point becomes bigger and triggers pop-up menu with "Reposition" button
-
User drags Point to a new location and clicks on "Save Changes" in the upper right corner when they're done
Additional comments:
-
For the MVP we enable only "Add Point" functionality, meaning only "Point" icon will be available the lower left corner. Should be like this:
-
"Save changes" button in the upper corner should be augmented with "Cancel". If user clicks on "Cancel" during repositioning, Point location resets to the initial one and user exists "Reposition" flow
from ground-platform.
Hi @DaoyuT, let's consider this as done, with additional changes as enhancements. Great work!
from ground-platform.
Related Issues (20)
- WHISP data missing on new plots HOT 1
- MultipleChoiceSelection Condition Proto is missing task ID field HOT 1
- [Code health] Add lint check for proto style
- [Import GeoJSON] Report cause of import failure to user HOT 1
- [Import GeoJSON] Survey organizers cannot import, but data collectors can HOT 1
- [Edit survey] ACLs not written using new format
- [Create/edit survey] ACLs updated immediately when edited HOT 1
- [Create survey] OwnerId is not saved
- [Proto] Tasks in /job proto don't update on initial configuration HOT 4
- [Code health] Move `to*Pb()` from `functions/import-geojson.ts` into `lib/geojson.ts`. HOT 2
- [Code health] Throw exception instead of returning Error on relevant conversion functions
- [Export CSV] Also export altitude and accuracy when exporting captured locations
- Allow survey organizers to delete LOIs
- [Code health] Emit OK HTTP status in callbacks instead of onHttpsRequestAsync
- [Proto] LOI Metadata is swapped HOT 1
- [Proto] Capture location proto doesn't serialize because `minAccuracyMeters` set to null
- [Code health] Regenerate Demo Survey for local emulator
- [Proto] Time task is serialized with BOTH_DATE_AND_TIME type (implying both date and time input) which is not supported on the app
- [Code health] Fix end-to-end testing after proto migration
- [Conditional Tasks] "If the answer to" font rendering can be improved
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ground-platform.