As I said earlier, what’s lacking to make an awesome XMMS2 GUI client is a common vision.
We need a dream!
I have a dream that one day this community will rise up and live out the true meaning of its creed: “when the music is end xmms power of the pc.”
I have a dream that one day on #xmms2, the sons of former GTK+ developers and the sons of former Qt developers will be able to work together on the code of a GUI client.
I have a dream that one day even the state of Microsoft, a state sweltering with the heat of instability, sweltering with the heat of dull interfaces, will be transformed into an oasis of freedom and music.
I have a dream that XMMS2 clients will one day live in a community where they will not be judged by their GUI toolkit but by the content of their user experience.
I have a dream today!
(Kudos to Martin Luther King for the original draft.)
In the end, all we want is an awesome music player.
But do we all share the same definition of what an awesome music player is? Probably not. In fact, I don’t think most of us even knows what an awesome music player is; if there were one, we wouldn’t have to build one, right?
So the goal here is to gather qualities that we expect of such a project, and refine them into a common vision. I won’t start dropping design mockups or fancy feature ideas until we have established what we all want, conceptually.
What I expect of this GUI client, and the vision for the project, is that it should be:
- Clearly focused