Amarok/Development/RoadMap: Difference between revisions
| Line 31: | Line 31: | ||
=== Remove comment fields from like and dislike === | === Remove comment fields from like and dislike === | ||
People keep using it for support request, remove the temptation. Could be replaced by radio button group with fixed choises | People keep using it for support request, remove the temptation. Could be replaced by radio button group with fixed choises | ||
''As soon as we know which choices, this is quite easy and quick to do, a day or two tops.'' | |||
=== Generate statistics for amarok-devel === | === Generate statistics for amarok-devel === | ||
Since we mention it's only to be used for statistical purposes, let's use it that way. There should be summery mail send to [email protected] every week. | Since we mention it's only to be used for statistical purposes, let's use it that way. There should be summery mail send to [email protected] every week. | ||
Revision as of 18:34, 30 September 2012
TODO
Meta System Rewrite
Step 1: prevent circular dependencies
Matêj: 5 days
Step 2: Simplify Compilation: Genre, Label, ...
Matêj: ? days
Step 3: Multi-label, -genre, -trackArtist
Matêj: ? days
Playback::{Queue, Controller}
Basic functionality and simple QML based UI
Bart: 15 days
Dynamic Playlist refactor to Meta::Playlist and Queue
Ralf: ? days
Feature compatible with 2.6 The::Playlist
Team: ? days
KPlugin -> QPlugin
Mark: 2 days
Likeback improvements
These changes are to improve likeback as a team tool. The alternative is complete removal, but we feel it can be very useful.
Fix dialog layout
It's not properly resizing. This is usually fixed by using the UI file more/properly.
Should be fairly trivial but tedious, likely just playing with QBoxLayout margins, size policies and stretch factors.
Send comments to forums
The user forums is a much better place to handle these. They are properly monitored and admined.
Remove comment fields from like and dislike
People keep using it for support request, remove the temptation. Could be replaced by radio button group with fixed choises As soon as we know which choices, this is quite easy and quick to do, a day or two tops.
Generate statistics for amarok-devel
Since we mention it's only to be used for statistical purposes, let's use it that way. There should be summery mail send to [email protected] every week.
Organize Dialog
Refactor
Ralf: ? days
With extra preset dialog
Ralf: 2 days
Export playlist from PlaylistFileProvider
Ralf: 3 days
Services
Basics, desktop UI
Bart: ? days
Cool stream refactor as simple test case
Mark: ? days
GPodder refactor as complex test case
Lucas: 2 weeks
Ampache & ownCloud Service
Lucas: 3 weeks
CollectionManager Refactor
Slim Down (- ServiceCollection and assoc. mess)
Matêj: ? days
Move into core
Matêj: ? days
Individual Services/Collections
Matêj: ? days
Git user test team organization
Myriam: ? days
Directory Structure & CMake targets
Team (lead by Mark and Matêj: ? days
PopUpDropper simplification & UI tweaks
Mark: ? days
Release Planning
2.7: GSoC projects
Statistics is ready to go in, Spotify and Nepomuk need some polish, tomahawk is unknown, QML is not supposed for immediate inclusion.