On Wed, 1 Aug 2007, Daniel Dalton wrote:

> So does anyone know how I should start when I download a patch and I find
> out it doesn't work?

Well, that's what all the magic about programming and debugging is about, and
it just takes effort and time. Get the code. Try it. Stare at it. Fix it.
Rebuild it. Try it again. Repeat.

> What else will I need to know to make the things I said above work?

You need to program. A lot.

> If I was to create a patch that put a music option in the main menu how
> would I do this?

Get the code. Add everything the way you want it. Run diff. Post the patch on
flyspray!

> How do I display text on the screen?

lcd_puts() and friends. Have a look in the existing code to find inspiration.

> Why can't plugins use the voice interface?

Because the infrastructure to make that work isn't done.

> Couldn't they just use the talk.c file and then use the functions from that?

No they can't. This is a subject for a separate thread so if you really feel
like venturing down the "voice for plugins" lane we should take it separately.

> When I try to create a patch the diff file comes out with about 23000 lines.
> Is there away I can fix this?

Yes, don't modify whitespace/newlines on lines that you don't change!

-- 
  Daniel Stenberg -- http://www.rockbox.org/ -- http://daniel.haxx.se/