Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Twitter Sign In with OpenID Sign In with Google

Sign In Sign Up

Categories

In this Discussion

Tagged

Jo Home Page
GitHub Repo
Welcome to the Jo support forums! Please Sign Up and join in the discussion. You can also Sign In instantly with Twitter, OpenID or your Google ID.
Update: 0.4.1 & Call for testers
  • davedave February 2011
    Posts: 415

    Swapped zip files from 0.4.0 o 0.4.1, be sure to download and update your projects. Thanks to all who found the weird iOS bug, which basically made scrolling and tapping worse the more you scrolled.

    As Jo nears its first formal release, I'd like to start gathering developers who are willing to test experimental versions to avoid this sort of thing in the future. Id you are interested, please send me a message and I'll add you to the list. Thanks!

    Dave Balmer, Jo Code Wrangler
  • FlockonusFlockonus March 2011
    Posts: 3

    Hi!


    I'm a real noob to Android applications. 
    As I was trying Jo, I made a little video abou my experience on Galaxy S.
    My overall video capability sux, but I try to point out a few points.


    Correct if I said noob stuff
  • davedave March 2011
    Posts: 415

    Thanks for posting this! Lots of great feedback for the Galaxy. Was that run in the browser or were you running it as an app with PhoneGap?


    I'm working on the tap sensitivity. The keyboard popping up at anything that looks like a field is a bug in that browser; hopefully a workaround is coming. Overall, I've had very mixed results between various Android devices. Definitely a harder platform to support than iOS and webOS. :)
    Dave Balmer, Jo Code Wrangler
  • FlockonusFlockonus March 2011
    Posts: 3

    I was running as Phonegap app, unchanged demo [ except for the phonegap include :-) ]


    The tapping is a great place to tune yeah.

    About the inputs in the form, I didn´t got to look at the code, but as a possible sugestiong to heavy workaround: what about you use the visual componets as div/spans that actualy change values at hidden inputs? That would not trigger the keybord, right?

    Appreciate your work man, wish the best for this project. As I free up some time I will try and help some
  • davedave March 2011
    Posts: 415

    I think the galaxy is pulling up the keyboard on anything with a tabindex, which is weird. Might have to pull that out of joControl, at least for mobile platforms, just to be safe. Strictly speaking, the tabindex only matters for desktop browsers anyway.


    As fo the event firing, I've noticed some issues even with webOS 2.x and iOS 4.x. Basically, the "click" events are becoming less sensitive, so I'm going to look into resolving that with touchstart/end (mousedown/up on webOS). So annoyoing. :)
    Dave Balmer, Jo Code Wrangler
Add a Comment