Justin, your mention of the HTTP/RESTy API the revamped music app uses
and the endpoints at
https://github.com/mozilla-b2g/gaia/blob/master/apps/music/js/view.js#L10-L54
reminded me of a similar effort by the author of the amazing beets
"media library management system" (https://github.com/sampsyo/beets) to
create a standardized/univeral REST API for music libraries.
It's called AURA, the repo is at https://github.com/sampsyo/aura and the
existing routing table is at
http://auraspec.readthedocs.org/en/latest/http-routingtable.html and the
spec/docs in general are at
http://auraspec.readthedocs.org/en/latest/index.html.
Do you think it would be feasible to try and converge/help create such a
standard? (Noting that beets has not yet particularly moved forward on
implementing/conforming to the AURA proposal, so AURA could still change
based on guidance/feedback/etc. from Gaia Music.)
A while back I tried to scratch my own desktop music itch leveraging
beets (http://www.visophyte.org/blog/?p=875), and it would be amazing to
me if:
- I could use the existing Gaia Music Player to talk to beets on my desktop
- That if I made a cool new UI, I could use it on my device when beets
is not involved, plus with beets.
Andrew
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
