You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document is a draft, imagine the best codebase possible, all the features you'd like, best back-end/front-end implementation, everything... and let's discuss it here. I'm locking the discussion for now to avoid some pollution, and let's talk about it on specific issues/Gitter.
If the whole codebase has to change to have a nice software, I don't see any problem (Whole app IPC Q/A for example, external binaries... Everything can be discussed)
Put a +1 on the first post of any issue if you'd like to see it included.
Disclaimer
The first goal of Museeks is to focus on music, not tons add tons of heavy add-ons.
The focus of Museeks is:
Simplicity
Elegance
Decent features
What we (understand "I") don't want is:
Tons of features slowing down things that nobody uses
Ultra-specific features you can find in your niche favorite player
Essential features
These features must be done before Museeks 1.0 is released.
Almost essential features, but not as important. They'd better be done to have a serious piece of software. They may need serious specifications though.
Does that includes the ability to sort by clicking on them? If not, we should add it.
Use the Web Audio API instead of the Audio API #128
I think this is needed for 1.0. Doing this change in 1.x can be risky. Also, it is kind of prerequisite for #114, in which I'm personally really interested.
Kind of stalled on work needed to be done in mpris-service module. /cc @emersion ?
I doubt we want to interact with dbus directly.
But we can at least add Tray icon.
Ok, let's talk about serious business now 😝
Museeks 1.0
This document is a draft, imagine the best codebase possible, all the features you'd like, best back-end/front-end implementation, everything... and let's discuss it here. I'm locking the discussion for now to avoid some pollution, and let's talk about it on specific issues/Gitter.
If the whole codebase has to change to have a nice software, I don't see any problem (Whole app IPC Q/A for example, external binaries... Everything can be discussed)
Put a +1 on the first post of any issue if you'd like to see it included.
Disclaimer
The first goal of Museeks is to focus on music, not tons add tons of heavy add-ons.
The focus of Museeks is:
What we (understand "I") don't want is:
Essential features
These features must be done before Museeks 1.0 is released.
Reorderable playlists Reorderable playlists #175Installers Create installers #100Great to have
Almost essential features, but not as important. They'd better be done to have a serious piece of software. They may need serious specifications though.
Good to have
Would be good to have them, but they are not "absolutely" mandatory.
FLAC support .flac support #53TracksList
Sort columns in TracksList #62Better system integration on Ubuntu/Gnome Integrate mpris #93Bonus
The development will not be focused on theses issues, and/or these issues need discussions first, but they remain good ideas.
m3u support m3u support for playlists (load/save) #146Minimizable windows to tray System Tray Icon #219To be discussed
2.0 ?
The text was updated successfully, but these errors were encountered: