mtytel / echollage Goto Github PK

Maybe 8 too but not counting on it.

Just don't do it.

Kind of takes a while to load a full screen, I think it would look better if it loaded a whole bunch at the beginning.
Probably shouldn't query echo nest for it. Maybe some static data.

It would also be nice if it loaded in a spiral or something cool like that.

So the user knows what song is playing.

The playlist/methods are probably better designed for this type of app.
It will improve API performance and possibly produce better results. (we can get 5 tracks instead of 1 per API call)

Also maybe wait for: http://developer.echonest.com/forums/thread/770#post2997
Then the API calls would be super efficient.

Looks like soundManager is the culprit here.

It might be possible to do some cross site scripting attack if the Echo Nest 'response' is set up the correct way.
Look into the track-info section.

burn all mp3s.
not to cds, but to the ground.

SoundManager2 handles flash mp3 fallback for open source browsers.

So the user knows what their doing.

Set the base artist with a small button that is visible when hovering over album art.
New tracks are loaded from similar artists of the 'base' artist.

Ideally:
Faded default text if the user hasn't type in anything.
If the user types anything in, it's full color and the default text goes away.
If the user deletes all of their content, the default text returns.