Crashes when the repo name is wrong about star-history

[timqian]

@kachkaev It has been 25 days, and I have made some updates of this repo. The alert box is changed to a notie. See the new version.( But the "displaying repos not existed on github" feature is not added.)

Updates includes:

2016-6-30: Alert to notie

2016-6-28: Add clear btn

2016-6-28: Better view for "many star" repos(use current star number as the last point on the graph)

2016-6-26: Store repo info into url hash

2016-6-26: multiple kinds of input styles(eg: github.com/timqian/star-history, ...)

2016-6-26: Better view for less star repos #28

2016-6-14: Toggle search by hit enter #26 , prevent crash while searching for not existing repo

[timqian]

Hi, @kachkaev Sorry for the late apply and thanks for your advices, they sounds reasonable. Hopefully I will find time to add the first two advices in the next week(as I am busy building something else recently)

1. prevent 'crash'
2. multiple input style

As for the UX perspective, I don't see much necessity to display repos not existed on github(maybe an alert information will be enough). So it might won't be added. What do you think?

[kachkaev]

Hey @timqian, thanks for your reply and for willing to implement the new stuff!

I'm not quite sure that an alert is a good solution from the UX perspective. It blocks useful parts of the UI and requires a user to move the mouse, then carefully stop on top of a button, click it and finally move the mouse back. All this without a reason, because pressing that button in an alert does not tell the interface perform any action. Such case of a modal window are well-described in literature on interfaces, e.g. The Humane Interface by Jef Raskin. An error can be reported much easier and without causing a distraction. E.g. the input's background can temporary change to red, the input can shake (like in OSX login screen) or a gentle notification can appear next to a field. This is in case if we have a one-liner.

The reason why I suggested to keep the non-existing repos too is because I see the list of them as a single multi-line input rather than an array of the individual ones. This way it is much easier for a user to control what they want to display in a chart. A person just types whatever he or she wants and the image updates either on each key press, after hitting enter / shift+enter / control+enter or after pressing some "accept" button. The app does not control what is in the multi-line input, it just reacts to the changes in it.

Therefore, if you paste a poem into the text field, the interface will just show [×] next to each line, because none of the lines will match the expected regexp. No requests will need to be made to check whether the repos with such names exist. In a normal situation, people will just be typing or pasting real repo names, either one by one or in bulk. If there is just a single multi-line input with some status icons on the side, a user will have to perform the smallest number of actions ever possible to get to their result. They can easily swap, remove or change the names of individual repos without having to press custom controls and without you having to implement these controls. The app gets a lot of features for free an the UX is as simple as typing stuff in a Notepad.