JP, Thanks for your response! I've downloaded 1.1_r1 and done a little bit more testing and:
#5, #6. This is something that seems to ONLY happen on the Android system. In Chrome it screams along like a scalded dog. Stuff pops up, hides, fades etc like it was a native application. #2. There's some work going on over in the GWT stack to have Gears/AIR/ HTML5 native storage/workers/caches abstracted in GWT. This is a pretty exciting project and will hopefully lead to some truely awesome android ports. #4. Farts. Still there. Maybe a TICK faster, but not really. #1. Still weird. #3. ditto. iPhone has implemented a mouse drag event framework that looks pretty cool. No love for Android yet though. I'd love to try a nightly build, but as I'm on Windows I can't do a image compilation from source. E On Apr 8, 9:10 pm, JP <joachim.pfeif...@gmail.com> wrote: > I've done someGWTwork in 2007 so I've fired up the site and checked > it withAndroid'sbrowser(for the first time, it never occurred to me > to try this out. I also tried Opera Mini but it wouldn't even start > loading). > 1. I cannot confirm your layout issues. I need to add however that the > web developer who provided the HTML framework used HTML tables for > layout purposes (his task, not mine). > 2. Gears wasn't around back then (;->) > 3. I can confirm this, and it renders some of my web site's > functionality mostly useless (table-based slider). I think some fine > work inGWTwould be in order here (Note: I am onGWT1.5.3 as no > maintenance is performed). Or, as you hope, the newer Webkit may help > you out. > 4. I can confirm this also. In my book, this is cosmetic, in > particular considering all the other issues. > 5. From your description - I've seen this effect with Firefox 2.x over > an Internet connection. Never in a LAN environment and also not with > IE 6 (both LAN/Internet). So this problem may not be specific > toAndroid'sbrowseronly. > 6. Likely connected to 5. > > I would cross check your web app against other WebKit-based browsers > as well as older and newer and other browsers in various environments > so you can find some patterns that you can research/report on theGWT > side of things. To answer your question where these questions > belong... over toGWTIMHO, because it is a declared goal ofGWTto > handlebrowser"quirks" for you - the developer. > I hope you're not in a time crunch here... Good luck. > > JP > > On Apr 8, 10:53 am, Evan Ruff <evan.r...@gmail.com> wrote: > > > Hey guys, > > > Little stream of conciseness here, sorry if this is a bit long/ > > disjoined. > > > I was wondering if anyone had done any work withGWTand theAndroid > >Browser. While I'm getting basic functionality to work, the general > > speed, responsiveness and user experience seem very sluggish and, > > well, sorta bad. Another issue I'm having is locating a group to go to > > for support, examples and help. While I'm interested inGWTwith > >Android, it seems thatAndroidDevelopers Group is really only > > interested in native apps. Where to go forBrowserspecific help? > > > Anyways, some of the particulars I've run into: > > > What group to go to? > > > 1. Issues Controlling the viewport: No matter what I do, I can't seem > > to get proper control of the viewport. Editing the meta data, overflow > > CSS properties, insuring that the window's objects are small, etc. I'm > > continually getting white space borders and stuff like that. This > > causes weird finger behavior, especially allowing the user to browse > > into the white space. > > > 2. HTML5/Gears Wrappers: I was wondering if the Gears API has an > > implementation to support HTML5 storage/cache issues in case of a non- > > gears enabled client. If not, is there a library anywhere that > > supports the encapsulation forGWT? > > > 3. MouseListeners: The OS seems to swallow up the MouseUp event in > > order to do detection of scroll/drag type stuff. I guess I understand > > why it does it for the drag type thing, but it never fires MouseUp > > even after the drag is done. Ehh... fair enough, I guess. > > > 4. Focus Panel ClickListeners: When I click a focus panel, a orange > > circle shows up in the upper/left corner with what seems like a cursor > > in it? (http://i243.photobucket.com/albums/ff2/gte619n/ > > selectBubble.png) Also seems like a non-trivial delay between the > > press and then a following action. Makes the app seem especially > > sluggish. > > > 5. Image Loading/Display: Seems really slow. Even when doing > > background repositioning to flip sprites. Additionally, the images > > don't seem to load in any fixed order and method. Also seems to hang > > when loading images (http://i243.photobucket.com/albums/ff2/gte619n/ > > selectBubble.png) I've attempted to get around this by doing Prefetch > > and such, but nothing seems to work. Seems like it needs to talk > > itself into refreshing the screen after loading finishes (even in > > localhost in the emulator) > > > 6. Visibility hide/show: Very sluggish in general. > > > 7. Scroll inside divs: Flat out doesn't support this. I guess the > > Cupcake release, bringing thebrowserup to Nov 2008 Webkit, should > > fix this but I still don't have any visibility into that release. > > > Has anyone compiled some best practices to use when building an > > Application forAndroid? Maybe even some widgets or JSNI breakouts to > > better manage the behavior and performance of the app? > > > Thanks! > > > Evan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
