Hi,
Thanks for all your help.
Just a couple more questions.
Daniel Stenberg wrote:
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.
I am using cygwin on windows. So it takes me about 15 minutes to build
rockbox when compiling.
If I am just editing a couple of files what is the best way to do this?
What else will I need to know to make the things I said above work?
You need to program. A lot.
Ok but what do I need to know in c.
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!
And just to get me started where abouts should the code go?
What file should I look at first?
How do I display text on the screen?
lcd_puts() and friends. Have a look in the existing code to find
inspiration.
Ok
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!
And how do I do that?
All I am doing is the following:
1. Open main_menu.c
2 I arrow around through the code and I also use the find function in my
text editor.
3. I add my code.
4. I save.
5 I open english.lang.
6. I arrow around a bit and I use the find function in my text editor.
7. Once I have found the spot where my code should go I add my code
there. All I did was fill in the disk size voice string.
--
Daniel Dalton
