Elisa: Difference between revisions
m (→Goals) |
|||
Line 34: | Line 34: | ||
The following snapshots show the current interface. They are only indicative and everything is open for improvements. | The following snapshots show the current interface. They are only indicative and everything is open for improvements. | ||
[[File:elisa_header_20170221_225733.png|400px|thumb|left|Elisa New Header]] | |||
[[File:ElisaPlayListScreenshot_20161209_172455.png|400px|thumb|left|Elisa Playlist]] | [[File:ElisaPlayListScreenshot_20161209_172455.png|400px|thumb|left|Elisa Playlist]] |
Revision as of 22:00, 21 February 2017
Elisa
Elisa is a simple music player aiming to provide a nice experience for its users.
Goals
- being very easy to setup (ideally, the user would not setup anything before being able to use it) ;
- being fully usable offline (or in privacy mode) ;
- being open to leverage online services but not a development priority (the experience should not be degraded when you are offline) ;
- being usable in Plasma Workspace (MPRIS2, Baloo, ...) but also on other environments (Windows, Android, ...) ;
- being intuitive to use ;
- being focused on music player (managing your music collection is not a development priority). This means that it is not a direct fulfillment for people needing that ;
- being as much as possible bug free (meaning stability has higher priority than feature development) ;
- targets Linux Plasma Workspace, other Linux desktop environments, Android and Windows ;
- being able to leverage UPnP ContentDirectory and MediaRenderer in an easy and intuitive way.
Design Open Questions
The design of Elisa currently leaves open questions about the direction. At least the following points need an identified solution that could be implemented:
- Implement User Centered Design to help guide the development (definition of persona, ...) ;
- trying to combine an interface to be used with the mouse and with the touchscreen commonly found on laptops ;
- how to decide what is done by single click, double click or single long click.
Description of the Application Architecture
Currently music is retrieved from Baloo and put in an SQLite memory database. Live refresh from Baloo is not working.
The user interface is done in qml with Qt quick controls 1.
The UPnP support is probably broken right now.
Current Interface
The following snapshots show the current interface. They are only indicative and everything is open for improvements.