Rockbox

Tasklist

FS#10848 - Cowon D2 manual

Attached to Project: Rockbox
Opened by Tomer Shalev (tomers) - Saturday, 12 December 2009, 21:39 GMT
Last edited by Tomer Shalev (tomers) - Monday, 14 December 2009, 20:19 GMT
Task Type Patches
Category Manual
Status Closed
Assigned To Tomer Shalev (tomers)
Operating System Cowon D2
Severity Low
Priority Normal
Reported Version Release 3.4
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

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).
This task depends upon

View Dependency Graph

This task blocks these from closing
 FS#10735 - Platform files for Cowon D2 manual 
Closed by  Tomer Shalev (tomers)
Monday, 14 December 2009, 20:19 GMT
Reason for closing:  Accepted
Additional comments about closing:  Committed in r23991.
Comment by Tomer Shalev (tomers) - Sunday, 13 December 2009, 20:31 GMT
Some more additions to manual. Also removed dummy images.
Comment by Tomer Shalev (tomers) - Sunday, 13 December 2009, 20:38 GMT
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
Comment by Dominik Riebeling (bluebrother) - Sunday, 13 December 2009, 21:04 GMT
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?
Comment by Tomer Shalev (tomers) - Monday, 14 December 2009, 05:24 GMT
> 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.
Comment by Nick Peskett (nickp) - Monday, 14 December 2009, 15:18 GMT
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?
Comment by Tomer Shalev (tomers) - Monday, 14 December 2009, 20:19 GMT
> 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...