- Clojure 96.1%
- Sass 2.8%
- JavaScript 0.7%
- HTML 0.4%
c8849810db* Add dark sidebar * Add generated covers for items that have none * Fix small spacing issue with generated covers * Set up different sidebar sections and improve styling of bottom bar * Add open-iconic and use icons for playback control buttons * Make sure sidebar always extends to complete height * Simplify album listing view function, add text-overflow to thumbs * Use better identifier for generated covers Makes sure that covers look the same, no matter if generated from an album or individual track * Move shadow-cljs to devDependencies * Display all album titles in a table * Make progress bar take up all available space |
||
|---|---|---|
| src | ||
| test/cljs/airsonic_ui | ||
| .gitignore | ||
| .travis.yml | ||
| karma.conf.js | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| shadow-cljs.edn | ||
Airsonic Web Client 
This is just meant for exploration. If you want to see something more serious, take a look at airsonic-ui.
Implemented so far
- Login
- Welcome screen (most recently played)
- Artist detail
- Album detail
- Play Track w/ next and previous
- Currently playing notification
Development
The project is written in ClojureScript and uses re-frame for structure and peace of mind. The build tool is shadow-cljs, which offers nice editor integration and interoparibility with the whole JavaScript ecosystem. If you haven't worked with re-frame: I highly recommend it. Good resources are the project's docs and a post about its building blocks.
To build the project make sure you have Node.js (v6.0.0), npm and Java 8 installed in your system.
# after cloning the project, first install all dependencies
$ npm install
# start a continuous build with hot-code-reloading and continuous testing
# first build takes a while. open http://localhost:8080
$ npm run dev
Note: In dev mode this project comes with re-frame-10x. You can hit Ctrl + h to display the overlay and have a time traveling debugger.
Tests
This project uses karma for tests. Make sure to have Google Chrome installed, otherwise the watcher will time out. If you want to run tests continuously in the background, you may want to have Growl installed to show notifications (see setup instructions).
# run tests once
$ npm test
Note: If you want nice console output in your tests, make sure to (enable-console-print!). You can call println afterwards like you're used to.
Deployment
# build and optimize the code once for production
$ npm run build
# runs npm run build and publishes everything via gh-pages
$ npm run deploy
All build artifacts will be output in /public. Don't change anything in there as changes will be overwritten.