andrew67 / ddr-finder Goto Github PK

Unfortunately, self-hosted Piwik is too difficult to maintain.

No good reason for the "About" embedded page to be pulling in all of MetroUICSS, fonts, etc.

Should provide a simpler CSS for this page for the needed components (and native-looking font).
Bonus points for native-looking components.

User may end up bookmarking locator.html, which in non-exceptional cases will have no obvious pointer back to the main/options page.

The zoom restriction was originally created for map/box clients that could end up defaulting to a wide view, pull in a large list, and exceed reasonable resource usage and view utility.
Also, as a mechanism for a server to say "no, I don't want to pull this much data in".

For a server that's ok with this, and a client that can handle it (client-side pagination or pin aggregation), add a flag for it to say so (defaulting to off for old clients).
Good non-breaking optional addition for v3.1.

A nice-to-have to let the users know their GPS data isn't being sold off, and to provide a Piwik opt-out screen for Analytics.

See https://css-tricks.com/how-to-animate-the-details-element/ for a great guide on how to animate these.
This allows removing the accordion library and its jQuery/MetroUI CSS dependency, as well as more semantic HTML.
Note: ensure print styles still work.
Bonus goal: inline-block with media queries to show side-by-side results on larger screens.

Currently, deployment consists of uploading the "web" directory.
Could add an optional step for minification of JavaScript and CSS resources.

See https://developer.chrome.com/multidevice/android/installtohomescreen

With upcoming iOS 14 and the "coarse GPS" feature, accuracy may become as low as 9km.
Bring back the code from a previous release which displayed this value on screen.

The current server has been grandfathered, however the code should integrate a key for explicit usage tracking, and so that anyone who wishes to deploy their own version can more easily do so.

Use <meta theme-color to set color branding like on the app.

For dense areas such as Tokyo, the 1º by 1º box is quite excessive, and will produce a large list. Results should be capped around 10-20, as this is not meant to be a comprehensive search engine.

• compress-cli -> unzip
• purify-css -> purgecss + minify

As $.getJSON() was only providing a success callback, failures with the request were not handled (UI remains in permanent loading status).
Based on documentation: http://api.jquery.com/jQuery.getJSON/
We can attach promise style, using .done() and .fail().

2022 copyright footer
Credit OpenStreetMap for locations

PDO would output strings for all results by default.
Evaluate whether DreamHost has mysqlnd driver available and switch to it, for proper numeric types in API output.

See: http://stackoverflow.com/questions/1197005/how-to-get-numeric-types-from-mysql-using-pdo/1197041#1197041

Currently, the "dump" API will hand over entries that were created/updated after a certain timestamp.
If there were a case of a deletion, the client would not be properly notified of this.

Requirements for implementation:

• Add a deletion log (up to code doing the DELETE to add an appropriate INSERT here) table containing source name, source id and timestamp.
• Add a flag to arcade entries, present in "dump" mode, to flag it as a deletion (avoids creating a whole new entry type).
• "dump" mode code will read the deletion log table in addition to the arcades table, to create flagged entries.
• Clients read this flag and delete the entries from their caches.

This is a candidate for future marking as API v3.1.

From user feedback:

• Move button icons to the left.
• Remove redundant buttons for going to external data sites.
• Move GitHub button to footer.
• Convert options button-set to dropdown, and move below action buttons.

https://dev.mysql.com/doc/refman/8.0/en/spatial-convenience-functions.html#function_st-distance-sphere

Potential challenges include making sure all API endpoints have sufficient input validation for user's latitude/longitude, and ensuring locations in DB are also properly bounded.

Support a tile system like Bing Maps Tile System: https://learn.microsoft.com/en-us/bingmaps/articles/bing-maps-tile-system
This lets the world be divided into blocks, so clients can request block by block, and responses become cache-able.

Can use window.devicePixelRatio and &scale=X (1,2) on the Static API to bring in a nicer image on hiDPI displays.
Can add the abstraction to the constructor or prototype.
Will have to add width= height= to <img> as well.

6 digits is enough for quite accurate location, and having more clutters the UI.
Can use JavaScript's Number.toFixed

The legacy WebUI is quite stable.
Replacing the icons with individual Material Design SVGs would reduce the page size by only loading the few icons we need, instead of the entire 82KB icon font.
Icons can be set up to match the native app, and to have long-term caching.

The demo server hosted on DreamHost is not taking advantage of gzip/deflate etc. in order to deliver a smaller payload to clients.

Preliminary searches concluded this can be accomplished via the .htaccess file.