Dominik Riebeling wrote:
On 5/10/07, Martin Arver [EMAIL PROTECTED] wrote:
Do you think we should use this approach for all features not
supported by a certain target? Like sw/hw-codec stuff, color display
hmm, I think that would make the manual somewhat torn, which isn't
good either.
I like that way too. We could have separate chapters for Radio,
Recording etc. The only drawback is the fact that the manual chapter
numbers will then vary between the targets, and as users tend to name
only the section number instead of its name this might cause some
misunderstandings. Not sure
I like that way too. We could have separate chapters for Radio,
Recording etc. The only drawback is the fact that the manual chapter
numbers will then vary between the targets, and as users tend to name
only the section number instead of its name this might cause some
misunderstandings. Not sure
On 5/10/07, Jerry Van Baren wrote:
...or you have a not supported chapter for the units that don't
support a particular feature. In the above example, for a unit
incapable of recording, Chapter 5 would become:
--
Chapter 5
On 5/3/07, RaeNye [EMAIL PROTECTED] wrote:
A little OT here, but what do you think about a flash (or other semi-video
thingy) ~30 seconds promotion clip for RB?
That would be fun, but to be a little more on-topic, wouldn't an
(interactive) animation showing what happens after you have
After the main menu hit the repos and the fact that this is now the
first contact with Rockbox, I don't think I am alone in thinking that
the manual could use some restructuring.
A lot of problems users had in the past, was to understand the nature
of rockbox. E.g. that the filebrowser is the
