Wishlist: doable

[abettermap]

Summary

Some things that would make the app much better and are possibly more near-future than #78. Just with that issue, though, all of this should be broken out into smaller issues.

1. Table

Table - sooner

• Indicate selected record
• "Jump to top" on page change, page length change, search change, or filter change.
• Related: consistent table height regardless of how many results.
• Show symbols for Size, World Region. Country flags look cool but this would take it up a notch.

Table - later

• Click individual cell value to set filter (unless it's "View image" or Video). Would need to disable row click again, and add btn at far-left column for "View in map" again. Maybe useReducer for this?
• Reinstate the X close btn, but make it not weird/unexpected behavior. It's just too standard to leave out.
• Autocomplete in filters (instead of boring open-search text)
• Autocomplete in Search (waaaay harder since so many fields, and might not be logical/useful because of that)

2. Panels

Omnibox

• Fix/restore correct neighborhood sorting
• Magnifying glass adornment
• Darker background to stand out from panels behind it. And maybe no green text? Primary color most places in the UI represents an actionable thing.

Panels

• Three-position panels on mobile: currently we have closed and halfsies. The third would be maximized.
• Related: instead of "X" to close panels, use the horizontal bar like modern iOS apps (e.g. Google Maps) use. Make it draggable to "grab" the panel and pull it down
• Panel headers: fancy Ikon Pass style slanted borders. Neato!

Filters stuff

• A "Clear filters" btn would be nice w/o having to open the table
• Related: "Data table & filters" btn: indicate that filters are present

Details

• Details: marquis (???) animated text bg like this but not lame and not on hover, just once whenever a new feature is shown.

3. Map

• Set z-index (there's a differently-named MB property for this) for selected feature. Related: now that we are using only icon symbols, no circles, an alternative to the cyan background to indicate feature selection is needed.
• Popups: vertically center on mobile.
• Polygons: don't de-select currently selected feature on hovering over another feature.
• Zoom in/out/home icons: magnifying glass for each with a +/-/home icon inside (home example)

4. Other

• Welcome screen: use "logo" instead of title. Consider fancy animation since it's the first thing users see. Still need to show Ross's subtitle and this would be breaking the full reliance on WP, but at least the body of the welcome screen would still be WP-driven.
• Flip the open-source switch. Make it public!
• Sharing btns: add a "Copy link" btn to copy the current URL to clipboard.
• Omnibox: highlight the part of the text in each result that matches what has been typed, e.g. English when eng is typed.

[abettermap]

@rperlin-ela tell your friend good suggestion on the darker omnibox background, really stands out:

also i super-hackily got the omni menu to open consistently downward on iOS rather than up/down erratically based on how many items are in the result. it is hardcoded to 150 to fit, and 250 on screens that are not touch-enabled. so, worst case we have a reaaaally short non-touchscreen or a large touchscreen with physical keyboard (like modern laptops), the omni menu will just be a little stubby.

i tried to get the omni to stay open after you click Done on iOS keyboard, but it alllllways closes as soon as you close the keyboard. you can still scroll while the keyboard is open though, so minor annoyance overall, and the always-downward menu feels WAY better now.

[abettermap]

i got the sorting-by-neighborhoods to work again:

but not when one or more lacks a Neighborhood:

i could see this being an advantage but either way i'm throwing in the towel on sorting by Neighborhood AND Town for now. complex sorting in JS is reeeeally challenging!

[rperlin-ela]

Awesome, thanks!

…

On Sep 18, 2020, at 6:00 PM, Jason Lampel ***@***.***> wrote:  i got the sorting-by-neighborhoods to work again: but not when one or more lacks a Neighborhood: i could see this being an advantage but either way i'm throwing in the towel on sorting by Neighborhood AND Town for now. complex sorting in JS is reeeeally challenging! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.