Rockbox

  • Status Closed
  • Percent Complete
    100%
  • Task Type Patches
  • Category Manual
  • Assigned To
    tomers
  • Operating System Cowon D2
  • Severity Low
  • Priority Very Low
  • Reported Version Release 3.4
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by tomers - 2009-12-12
Last edited by tomers - 2009-12-14

FS#10848 - Cowon D2 manual

The name says it all. There’s still a lot of work to be done.
Other touchscreen targets will greatly benefit from this patch.

I need a volunteer to provide images of the Cowon D2 for the manual (manual/rockbox_interface/images/cowond2-front.svg is copied from some other player).

The task blocks this from closing
ID Project Summary Priority Severity Assigned To Progress
10735 Rockbox  FS#10735 - Platform files for Cowon D2 manual  Very Low Low tomers
100%
Closed by  tomers
2009-12-14 20:19
Reason for closing:  Accepted
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

Committed in r23991.

Some more additions to manual. Also removed dummy images.

For those who don't want to compile and have a peek at the manual, I've attached a binary.
Cowon D2 users: I would appreciate if you review this manual and list the missing / invalid sections, so I can fix it. Concentrate on the key-mappings.

Work that left to be done:
- Create manual/rockbox_interface/images/cowond2-front.svg
- Add missing keymap entries, especially for plugins
- Review entire manual and validate proper keymapping
- Any D2's specific Installation instructions

Can you explain the reason for creating touch-actions? IMO it's overly complex – you define ActionTouchSomething actions only to redefine them later to ActionSomething. Or have I missed something here?

Can you explain the reason for creating touch-actions? IMO it's overly complex – you define ActionTouchSomething actions only to redefine them later to ActionSomething. Or have I missed something here?

This is done for the sake of reusing the touch actions among different touchscreen targets. They will share the same touch actions but might have different button actions.
Please let me know if there's a better way to achieve this requirement.

nickp commented on 2009-12-14 15:18

I've created a place holder outline image of a D2. I had a go colouring it in, but it looked a bit crap.

I'll experiment more with fills over the next few days, but if anyone more experienced fancies stepping in, feel free.

I noticed there was a picture of a Sansa on page 17 (3.1.1 The player's controls). Would you like me to have a go producing a top view with arrows showing the various controls?

I've created a place holder outline image of a D2. I had a go colouring it in, but it looked a bit crap.
It seems that a Cowon D2 image was already there :-) manual/rockbox_interface/images/d2-front.svg

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing