Difference between revisions of "Feature Wishlist"

From MythTV Official Wiki
Jump to: navigation, search
(In Development)
(Ideas with response)
Line 69: Line 69:
 
:''Very distro dependant, apt-get solves 99% of the problem for most folks (those who are *using* packages, maybe... --BayLink)''
 
:''Very distro dependant, apt-get solves 99% of the problem for most folks (those who are *using* packages, maybe... --BayLink)''
 
* [http://gossamer-threads.com/lists/mythtv/dev/6465 Action sound], a short confirmation 'blip' to say that a keypress was received and is 'being processed'
 
* [http://gossamer-threads.com/lists/mythtv/dev/6465 Action sound], a short confirmation 'blip' to say that a keypress was received and is 'being processed'
:This is difficult to achieve without impelemting and requring all audio devices to be routed through an ALSA mixer (which has it's own issues at the moment)  --- As a work around, look on the backend setup screen.  There is a config option for "Execute command when key pressed" (or something like thing) that you can configure to play a sound
+
:This is difficult to achieve without impelemting and requring all audio devices to be routed through an ALSA mixer (which has its own issues at the moment)  --- As a work around, look on the backend setup screen.  There is a config option for "Execute command when key pressed" (or something like thing) that you can configure to play a sound
  
 
=== Already implemented ===
 
=== Already implemented ===

Revision as of 07:27, 31 October 2006

Before making any feature requests to the MythTV developers, one first needs to understand the most basic truth about MythTV: "MythTV is a project by developers, for developers." If you look at things in that light, comments that get made by developers to users who submit feature requests ("Sounds good; I look forward to your patch") make a whole lot more sense.

The developers of MythTV work for free (obviously), in their spare time. Most/all of them write software for a living, where they work all day long on things that other people want them to work on. When they work on Myth they focus on what's important to them. A feature gets implemented because a developer wants it bad enough to spend his spare time writing it and testing it, and believes in it strongly enough to defend it from the other developers (which helps to avoid the feature creep common in some projects). Bugs, especially crash bugs, get worked on by all of the devs as they encounter them as those impact everyone.

That's not to say that the users don't matter, or that the developers never implement something that comes from a user. It's just that unless a developer says either "why didn't I think of that" or "I could knock that out in a couple hours" it will be a much lower priority.

Requests from people who have contributed back to the project in some way carry a LOT more weight. Developers by and large tend to be rather blunt. People often mistake being terse and to the point for being insulting. Then they start a flame war on the mailing list (which is pretty much certain death for a feature request) all because a developer either a) didn't take 3 paragraphs to tell them "I'm not going to work on this" or b) they think that the developer should drop whatever they're doing because *they* want it done. A lot of the devs are a bit defensive when it comes to requests, largely due to previous bad experiences.

And, finally, remember this: if there's something you want badly enough, you can always offer to pay someone to do it.

Editor's note: Even moreso than on most pages, if you add a note here that a wishlist item is now available or in process, please note which version that information applies to ('added in 0.19', for example). Remember: wiki pages live forever. --Baylink 17:00, 12 February 2006 (UTC)

How to make a suggestion

If you've got an idea for a feature that you'd like to see implemented here's some guidelines for submitting it:

  • Before anything else, check the Current Version release notes to make sure it's not already in there (yes, this happens).
  • Clearly indicate that it's a request, not a demand.
  • Indicate your understanding that code speaks louder than words. (i.e. "If I could I'd write up a patch that does this but I'm not a dev")
  • Be very clear with how you envision your idea working. The more details you have in your request the better chance you have hitting that magical "knock it out in a couple of hours" mark.
  • Make sure you're not repeating a previous request. (search the mailing list archives)
  • Do NOT be offended if a developer responds with "sounds good; I look forward to your patch".
  • Requests from people who have contributed back to the project in some way carry a LOT more weight.

In Development

There are many items which are in active development (people are writing code). Some of them are listed below, and others at the developers' Trac wiki page.


The Wishlists

Setup and Configuration

See Feature Wishlist (Setup).

Anything for the setup process including hardware support.

Backend Addons

See Feature Wishlist (Backend Addons).

Backend additions are things you want mythtv to do when you're not around

Frontend Addons

See Feature Wishlist (Frontend Addons)

Frontend additions are things you want to do while using mythtv

Plugins

See Feature Wishlist (Plugin Addons) for existing plugins
See Feature Wishlist (New Plugins) for new plugin ideas

Plugins are applications that not related to recording programs, but can be integrated into MythTV, e.g. viewing weather reports, watching DVDs, and playing games.

Ideas with response

this defeats the purpose of a PVR, add a menu item to launch a non-buffering tv program in place of Myths "watch tv" item - This is better stated as a request for "fast channel changing" or "no 2 second delay". Current workaround is to switch channel changing behavior to "browse mode", but actually having "fast channel changing" would really help new user acceptance of mythtv.
uhm... can you spell l-a-w-s-u-i-t?) NEVER going to happen with core Myth
Very distro dependant, apt-get solves 99% of the problem for most folks (those who are *using* packages, maybe... --BayLink)
  • Action sound, a short confirmation 'blip' to say that a keypress was received and is 'being processed'
This is difficult to achieve without impelemting and requring all audio devices to be routed through an ALSA mixer (which has its own issues at the moment) --- As a work around, look on the backend setup screen. There is a config option for "Execute command when key pressed" (or something like thing) that you can configure to play a sound

Already implemented

  • playlist queue - ability to manage a queue of recorded programs or videos for sequential playback
  • Ajax Based Mythweb for Speed up and more interactivity - added in 0.20
  • Ability to mask Media Library entries based on entering PIN to identify user. e.g. Kids can not see anything in a specific program group.
  • Mouse support. Would make it possible to use a touch screen to control MythTv. - added in 0.20
  • Add support for DVB radio - done? - 0.20
  • Screensaver for widescreen plasma/rear-projection TVs, to avoid burn-in when displaying 4:3 content --Anaerin
XScreensaver support is in Myth, all you need do is install it in your box
  • Sound feedback for received remote control commands. This would notify the user of a valid/invalid key press by the sound emitted.
See response under 'action sound' in the page above
  • Implement a frontend gui that is based on xosd for text display and display on top of xscreensaver modules running on root window - this would allow for cool 3d backgrounds in the mythtv frontend
there is a new GUI based on OpenGL in CVS ...
  • allow some capability to go directly to some menus via Remote control eg Watch Live TV or Guide etc..
I think this exists with jump points, see Edit Keys menu option under Utilities/Setup
Already in 0.19, check options under Utilities/Setup and TV.
  • Enable browse mode via mouse (ala ATI Media Center). I miss being able to press the mouse button on the remote up and it shows whats on the other channels without changing them. You then press enter to change to that channel.
This is already available in 0.19. Check the options under TV Playback. I think it's called Enable Browse Mode.