i guess i know what you're thinking of: making the power button
something which
messes up semantics.
i believe that any computer must be turned on or off, and that this
function is distinct from actual use. i don't think merging
functionality into the power button is doing anything but en-bloating
a very, very primal function of the system.
i understand why its being done now, and i think its cute as anything
else that might come along in the openmoko tree. it just feels ..
ick .. to be using powerbutton, button #1, for anything other than
off or on. ;) i hope it does not actually become a standard, or
that at least a sys-config option approach is developed to handling
the issue, so we can switch the buttons at will..
yet, this can be quite easily solved: think of the power button as
"negative action" instead of "power"
yeah, a gradient scale of power. sure. i could get into that with,
for example, a knob that goes up to 11.
eg long hold, two-tap, one-tap
yes, perfect for those who can time the taps as needed, but usability-
wise, thats just a little # of people compared to those who can
handle a lightswitch.
i havent given that system too much thought though and as you know
im currently
not even into openmoko dev. just my 2c.
i think you're onto something ..
;
--
Jay Vaughan
