Conversation

Notices

  1. Hey... I'm Fluttershy. I saw this site and made an account. I hope you don't mind...

    Tuesday, 05-Apr-11 01:06:59 UTC from web
    1. @rotation Nobody uses buttons any more. Touch screens are the future, man.

      Thursday, 19-Apr-12 10:30:04 UTC from web
    2. @rotation Windows Phone mandates 3 buttons. Only one of them is any use though.

      Thursday, 19-Apr-12 10:30:46 UTC from StatusNet Desktop
    3. @rotation whut

      Thursday, 19-Apr-12 10:31:30 UTC from web
    4. @rotation Six? Home, Back, Search, Menu and the roller makes 5 interface buttons by my count.

      Thursday, 19-Apr-12 10:32:37 UTC from StatusNet Desktop
    5. @rotation Nonsense. My sausage fingers operate it just fine.

      Thursday, 19-Apr-12 10:33:06 UTC from web
    6. @rotation @ceruleanspark My old one had 11 buttons. Just on the front.

      Thursday, 19-Apr-12 10:33:35 UTC from web
      1. @scribble What phone was THAT

        Thursday, 19-Apr-12 10:34:50 UTC from StatusNet Desktop
        1. @ceruleanspark http://en.wikipedia.org/wiki/Samsung_Galaxy_5

          Thursday, 19-Apr-12 10:37:13 UTC from web
    7. @rotation Or the full keyboard hidden behind the screen.

      Thursday, 19-Apr-12 10:34:33 UTC from StatusNet Desktop
    8. @rotation Except they're just moving into software, with the option still there to do them in hardware and hide the on-screen bit. And the core functions (home/back/menu) are staying for good, though the last, if no physical buttons, becomes a dropdown rather than a regular button.

      Thursday, 19-Apr-12 10:34:57 UTC from IdentiCurse
    9. @rotation Which is why the option for manufacturers to do them in hardware remains. If a manufacturer both makes bad touchscreens, and insists on doing it the software way, you can simply avoid them.

      Thursday, 19-Apr-12 10:37:51 UTC from IdentiCurse
      1. @bitshift This is every android manufacturer.

        Thursday, 19-Apr-12 10:41:52 UTC from StatusNet Desktop
        1. @ceruleanspark Except that it isn't.

          Thursday, 19-Apr-12 10:42:46 UTC from IdentiCurse
          1. @bitshift @redenchilada Android Touchscreen response has always been less-than-stellar for me, even on higher end handsets. I don't know if this is a software driver thing, or a touchscreen thing, or what. All I know is that using android software keyboards left me with the idea that software keyboards THEMSELVES are bad. I also find web-navigation much more finicky on Android than iOS (Or even WebOS), requring either ludicrous zoom levels or fantastically precsie taps.

            Thursday, 19-Apr-12 10:45:27 UTC from StatusNet Desktop
            1. @ceruleanspark Yeah, I've had that issue. I've had it just as bad on iOS, though. It's mostly a matter of web layouts not being designed for the average sausage finger.

              Thursday, 19-Apr-12 10:50:45 UTC from web
        2. @ceruleanspark >implying the Galaxy's touchscreen is bad. Yeah you have no idea what you're talking about.

          Thursday, 19-Apr-12 10:42:51 UTC from web
    10. @rotation Sounds like a bad touch screen?

      Thursday, 19-Apr-12 10:38:21 UTC from web
    11. @rotation I don't know what to tell you then. It works insanely well for me.

      Thursday, 19-Apr-12 10:53:00 UTC from web
    12. @rotation Hahaha, no. I've got that phone, and it is _definitely_ not a bad touchscreen.

      Thursday, 19-Apr-12 10:53:52 UTC from IdentiCurse
    13. @rotation I'm telling you, I have some of the biggest hands out of people I know. You just have to _aim_ your taps.

      Thursday, 19-Apr-12 10:54:28 UTC from web