[mythtv] Proposed MythMusic Interface Improvements
thor
mythtv at lamedomainname.com
Sun May 2 20:09:59 EDT 2004
> How much of Thor's work is on the frontend?
Enough to debug the backend (ie. the mfd) and fiddle with a few
thoughts about UI.
> mfd seems to be where the bulk
> of his efforts has gone, and mfe is by his own admission going away.
Yup, although it's a nice place to experiment with hack'ed versions of
UI changes. The current mfe, for example, uses pop-up menus for
browsing.
>
> Should efforts on an updated MythMusic be targeted to an mfd world? Peaceful
> co-existence with the current model? Or perhaps get the UI right first, then
> figure out mfd integration at a later date? Should we be thinking about
> adaptor design?
Get the UI right, either as code against current mythmusic or current
mfe or standalone mockup.
Few thoughts on things I think have been missing in the conversation so
far:
* Typing stuff in with a remote sucks. Whether you are naming a new
playlist or entering a "search phrase", it will still suck.
* The mfd/mfe is client server (among other things). I have a suspicion
that we will head towards a state of affairs with two different kinds of
clients. One would be a desktop client for constructing playlists,
arranging content, storing queries, and so on (with keyboard, mouse, et.
al). This client might be web based. The other would be a TV client,
where you would basically browse the albums/playlists/search
patterns/hierarchies etc and select them.
* It's very hard to follow what people mean in describing UI's without
seeing some running code. At least, I find it very difficult to follow.
If at all possible, code is preferred to descriptions. Where that's not
possible, very clear explanations would be helpful.
- thor
More information about the mythtv-dev
mailing list