scifabric / app-flickrperson Goto Github PK

Problem: As a user I want to see bigger images in my browser, so I can answer the question much easily.
Solution: Use the image_b instead of image_m for the skeleton.

Page tries to load http://img339.imageshack.us/img339/9017/loadingo.png, which 404's, but it gets stuck trying to load it and doesn't load the next task because of it. Same task is displayed twice, or you get an error message.
Line is on template.html, line 68

This is a very minor issue that mostly concerns with vague wording. The question of "Do you see a human?" may be a little too simple and lead to some confusion. For instance, do I need to see a human face in the photo in order to say "Yes" or is just seeing a part of a person's body such as a hand or leg enough? If I see a photograph that focuses on trees and the natural scenery but I see a distant person in the background, should I consider this a photo with a human? Finally, if the photograph is a picture of some form of artwork (painting, statue, etc) that is made to portray humans, should I count that too? Again, this is a small issue regarding vague wording but I figured since it was never addressed, it could generate some confusion.

The example apps should demonstrate best practices so that these propagate to the children cloned from them. In a crowdsourcing app, efficiency is important, so it should be possible to quickly vote from the keyboard without having to navigate with the mouse.

Recommended mappings:

• Y, Left arrow == yes
• N, Right arrow == no
• Space bar, down arrow == don't know
• X, up arrow == invalid (e.g. the photo I got which was a rendered image of the Flickr message "this photo is not available")

Problem: As a user I get a broken photo, but I do not have a button to answer that there is no photo.
Solution: Add another button with the text: "There is no photo"

When following the instructions in the readme I could not get the app to work - it always had zero tasks. Investigated and got it working by setting task redundancy to be non-zero prior to updating the project. Should there be a step in the documentation for this?

BTW, this step IS on the webpage that describes how to get the app working.

Before this "/newtask" API call, the JavaScript at "template" needed to pull all the App tasks and choose itself one to show to the collaborator. This is not need anymore.