When results contain both images and coordinates, GUI should enable selecting either image grid or map.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Allow to hook up to display values while displaying them in table. | wikidata/query/gui | master | +91 -47 |
Related Objects
- Mentioned In
- rWDQG73997ab203e7: Final NoteDb migration updates
rWDQG08c24283ec80: Allow to hook up to display values while displaying them in table.
rWDQGca3a5e9d7ff0: Allow to hook up to display values while displaying them in table.
rWDQG9192c965dee1: Allow to hook up to display values while displaying them in table.
rWDQGc589a604c6e3: Allow to hook up to display values while displaying them in table.
rWDQG8e428d9b9865: Allow to hook up to display values while displaying them in table.
rWDQG5b27de139b7f: Allow to hook up to display values while displaying them in table.
rWDQG4a2151f4b48f: Allow to hook up to display values while displaying them in table.
Event Timeline
The algorithm used for detecting availability is currently only examining the first row.
We could increase the number of rows being examined, but I think we should always make the link clickable.
BTW: I was thinking about having 'magic' SPARQL comments that change the default selected view.
We process the result anyway for display, right? Can't we use that to also figure out if there are any coords or images there?
The result is only being fully processed when rendered. We could create some feedback loop from the table result browser to the app, but I am right now not sure how we could do this in a clean way.
I think we might want to disable the magic detection for now.
Change 276081 had a related patch set uploaded (by Smalyshev):
Allow to hook up to display values while displaying them in table.
Change 276081 merged by jenkins-bot:
Allow to hook up to display values while displaying them in table.