search

mkalam-alami / ludumdare-feedback-friends

A (defunct) incentive to comment on games, initially made for LD36
http://feedback.ld.intricati.com
MIT License
12 stars 5 forks source link

[Feature request] A quick way to play through 'the games deserving feedback the most' queue #38

Open Geruhn opened 8 years ago

Geruhn commented 8 years ago

A site that looks like the entry page, but has a next game button which takes you to the next game deserving feedback the most, skipping the game you already commented on. It could be implemented as an overlay/bookmarklet (I'd have a look into it myself, if I knew how the API worked ( is there any documentation I missed?)) or as an actual site with all the LD-FF information

ttencate commented 8 years ago

Sounds useful. As a workaround, I tend to use Ctrl+click on several entries to open them in tabs, then go through each in turn.

mkalam-alami commented 8 years ago

@Geruhn If you want to try implementing that, feel free to try changing the Feedback Friends code itself!

If I were to do this, the easiest approach I could see would be to have the main page automatically store in localStorage a set of games (UIDs) to recommend, based on what the user is searching.

Then the detailed view could feature some more JavaScript to read localStorage and add a little button to the next game on the list.

Geruhn commented 8 years ago

@mkalam-alami Is there any documentation for your API?

ttencate commented 8 years ago

Is there an API, even? I guess I just called that file api.php because it felt... API-ish, but it's an internal API at best. We don't have any docs, as far as I know, so you'll have to make do with the source, sorry. Then again, you'll probably need to edit it anyway.

The way the overview page works is by fetching a JSON object containing all entries (?action=eventsummary), and from there on all the sorting and rendering is done client-side. The details page, however, is still an old-fashioned server-side rendered page.

So if you stored the current page parameters (sort, filter, search query, etc.) in local storage, the details page could simply request that JSON again (from browser cache, ideally), sort/filter it in the same way, look up the current game, and render a button to the next one.