roarbar is designed to rely a lot on plug ins for functionality. So it's based on 3 components.
- plug ins
The main application.
Library which provides the shared functionality.
Individual functionality divided into sub categories.
- User Interface Plug in
- console output Pane
- album art
- database viewer
- Sound Output Plug in
- gstreamer output under linux
- probably direct sound output for windows
Source Control Management
Currently roarbar is stored public in a Subversion Repository, but I actually use git to work on the roarbar source code. I may switch totally to git in the near future, because working with git is very productive.
A documentation of roarbar library can be found here: