Hi Max, well, using up all the added processor power to keep the user interface responsive is indeed a bad idea that leads nowhere, except for drained batteries. On the other hand, WM5 is also not exactly responsive, so maybe Android is at least some improvement in allowing more complex user input via MT, eliminating sequencees of actions by replacing them with a single gesture. It's funny that the faster input gets, the more annoying gets waiting for the machine ...
If you run XCSoar on Android, wouldn't you need to use the OS provided interface to have XCS communicate with the device? I guess that no matter how fast XCS internally is, if you have to wait for the OS routines to detect a tap or determine whether the tap is just becoming a swipe, well, then you just have to wait, wouldn't you? Also, it appears scrolling in Android works on a per text line, not a per pixel line basis. I could not get a pixel by pixel scroll, which I can get on this iPad here I'm just typing on. Could that have an impact on map scrolling? Anyway, I'll watch the market for upcoming Android devices. The great advantage over iPxx devices is that there are more choices and they all want to find their niche by offering unique features such as sunlight readability. Viele Grüße, Martin Kopplow Mobil +49 171 7984740 --- Am 01.02.2011 um 20:04 schrieb Max Kellermann <m...@duempel.org>: > On 2011/02/01 19:45, "martin.kopp...@gmx.de" <martin.kopp...@gmx.de> wrote: >> So my questions, regarding the Streak: Is the touch interface as responsive >> as Apple's? I played around with some Android tablets last weekend and most >> felt kind of jerky when scrolling and zoomimg. Also, it appears that zoom >> was only available in certain moments, when the content displayed was >> 'meant' to be zoomed, such as pictures, but not when on the OS UI or >> application UI. Did you notice that? > > That is still Android's achilles heel: it is not as responsive as iOS. > I blame Java for most of that, iOS applications are compiled to native > machine code. Java is a bad choice for real-time applications, and > adding a JIT to Dalvik didn't improve much. Newer Android devices try > to make that problem disappear by using faster CPUs, but that is just > tinkering with the symptoms. > > XCSoar is native code, not Java, so it does not suffer from Java's > disadvantages. On the other hand, XCSoar may be the most complex > Android application that exists so far. > > Making XCSoar more responsive is one of my big goals, and you may have > noticed that version 6 is already a giant leap ahead of the old > version 5 (and therefore also LK8000). Still, there is much room for > improvement, XCSoar's map renderer is still very clumsy and wastes too > much CPU power. > > We're working on it! > > Max ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
