On 29.05.2007, Daniel Stenberg wrote:
> On Tue, 29 May 2007, Antonius Hellmann wrote:
>> I would then store the disassembler to:
>> utils/arm-disassembler/.
> I would prefer 'utils/disassembler' as then we can leave it
> open for future improvements to other archs without changing
> directory na
On Tue, 29 May 2007, Antonius Hellmann wrote:
I would then store the disassembler to: utils/arm-disassembler/.
I would prefer 'utils/disassembler' as then we can leave it open for
future improvements to other archs without changing directory name! ;-)
Does 'svn add utils/arm-disassembler/ar
On 5/29/07, Paul Louden <[EMAIL PROTECTED]> wrote:
>But for me the core is only cursor movement, menu, select, play.
I hate to say it, but you're either contradicting yourself with that
statement, or not understanding me: The 'menu' button, as you
mentioned, isn't honored on the Sansa because i
I would like to add the arm disassembler to rockbox svn.
The tools directory may be reserved for real rockbox development.
So are there any objections to adding a new utils directory on the
topmost rockbox level (i.e. apps, firmware, tools, ..., +utils)?
I would then store the disassembler to: util
I don't see a short vs long press as being any easier, so to me it
comes entirely down to the positioning, and the select button is
certainly in a better position than the 'context menu' button. It even
makes more sense to me that it be on the select button, in terms of
pure interface, because you
On 29/05/07, Paul Louden <[EMAIL PROTECTED]> wrote:
And to me, even just within the context of the Sansa, the current
controls are in no way convenient when operating with my left hand.
But context menu button is less convenient than if it were on
"Long-Select" (and this applies to righties as we
My brother recently got a Sansa and I put Rockbox on it for him this weekend.
There are some different things that I find inconsistent with other
targets, but it is not a bad choice of use for the buttons. I expected
the context menu on a long press of Select, too. But the Sansa has a
second menu
And to me, even just within the context of the Sansa, the current
controls are in no way convenient when operating with my left hand.
But context menu button is less convenient than if it were on
"Long-Select" (and this applies to righties as well, I think), and the
main menu is less convenient th
Paul Louden wrote:
I think a very, very minor inconvenience (as I think this is) is not a
high cost for actual consistency of the interface.
If you only own one Rockboxed device, you couldn't care less if it is
consistent with other Rockbox targets. You want it to work in the best
and most co
I think a very, very minor inconvenience (as I think this is) is not a
high cost for actual consistency of the interface. I find it much,
much easier to operate the device with just my thumb now relative to
how it was before, and I think a right-handed person will find it only
very very slightly l
I assume you're talking about the "Power/Menu" button on the Sansa. It
has two labels, Power, and Menu. I suggest we use it as the "Power"
button is used on other targets, because there's also a second "Menu"
button on the Sansa that serves the purpose of the Menu button on
other targets perfectly
It also affects those buying a new target. As I said, when you move to
a new software, you expect changes. When you move to the same
software, you expect consistency. If a button does something in one
screen, you expect it to be the "same" button in all the other
screens, as the button that does t
I agree,
however, I think it should be a higher priority to have the button do
what it says, which is exactly the reason the REC button does nothing
on most targets yet.
Most users would have one rockbox target, so why do they care if the
buttons are no consistant with a different target?
The on
I agree wholeheartedly.
FWIW, when I (occasionally) respond to a question regarding a target that
I'm unfamiliar with - most of them - then I always use generic button names
(directions/MENU/SELECT,/PLAY/STOP) in the hope that these will be
translatable by the end user.
--
Steve B
This seems to be a point I find myself arguing more often than I'd
like, so I'd like to bring up some discussion of it here so that maybe
some more abstracted decisions can be made (both for moving forward
and for revising some existing targets).
In my opinion it's very important that certain fun
On 29 May 2007, [EMAIL PROTECTED] wrote:
>>> came up in IRC that the pitch screen isnt enabled on the sansa, does
>>> anyone know why? I did a quick test compile and apart from the wheel
>>> not being used in the screen it works fine.
Enabled in SVN at 2007-05-28 12:33:44 -0400. The scroll wheel
On 5/28/07, Christian Gmeiner <[EMAIL PROTECTED]> wrote:
2007/5/28, Jonathan Gordon <[EMAIL PROTECTED]>:
> hey all,
> came up in IRC that the pitch screen isnt enabled on the sansa, does
> anyone know why? I did a quick test compile and apart from the wheel
> not being used in the screen it works
17 matches
Mail list logo