another iPad thread

[Zach]

There was a thread earlier about this, but now that the iPad is out
I'd like to ask about what people are running into when testing apps
out. The issues I'm experiencing personally are:

1. Javascript timeout: The iPad processor is simply too slow to load
my app sometimes so the javascript times out and you are left at the
loading screen. This may however be specific to my app, because it is
very javascript intensive. Not really an easy solution to this
problem.

2. Three and nine part images appear with 1px gaps between each part.
This was reported here: http://groups.google.com/group/objectivej/msg/139e64a945779abe

3. CPScrollViews show the custom scroll bars and are not scrollable
via flicking -- the only way to scroll is to actually touch the scroll
bar and, with much effort, try to move it with your finger. So both
their look and operation are out of place.

I've already been planning on rewriting my app with something like
iWebkit to make it iPhone-optimized, but now I think it may be
worthwhile to do the same using whatever iPad-specific web frameworks
come about, because right now it's pretty unusable on the device.

--
You received this message because you are subscribed to the Google Groups "Cappuccino & Objective-J" group.
To post to this group, send email to objec...@googlegroups.com.
To unsubscribe from this group, send email to objectivej+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/objectivej?hl=en.

[Brad Hutchins]

Hopefully this won't be much of a problem in 12 months when the real iPad is unveiled.  This first one, a lot of people were kinda like ... Disappointed, it really did not do that much.  Intentionally so (or so my theory is)  this makes it easier for iPhone developers to make the jump over to iPad.  Then after a year or so.  The real iPad HW comes out... especially this time unlike the iPhone where it took the competition 18 months to try to catch up to the iPhone, everyone and there grandmother is ready to pounce on being the one with the iPad killer.  So I think Apple will be forced to step up quickly on this.  iPhone OS 4 (minus statement 3.3.1 of course) is the first step.

The second, and in particular for you, is when the jump from high speed JS interpreters will be made to JS LLVMs.  Now I don't know if this is even a valid thing to do, what is involved and if it is even worth it.  Latest JS interpreters are pretty impressive compared to what was before.  But at least 1 more significant leap in JS benchmarks across the board (30-70%) needs to be done to address true web app performance to compete with that of Desktop apps.  That and HTML 5 and the browser's rendering engine also taking one more significant leap in performance too.