Database Info

jquery drag actions on android browser

I'm trying to figure out how the android browser handles click and drag actions with jquery.
Here is an example of what I'm talking about:
http://interface.eyecon.ro/demos/sort.html
The site works with a mouse but not with your finger in Android.
I want the same effect inside the android browser.
I searched these forums, but did not see anything. Can someone point me in the right direction?

That sortables demo does not work on my iPod touch either.
I wanted to see if something like this was possible in the android browser:
http://www.sitepen.com/blog/2008/07/10/touching-and-gesturing-on-the-iphone/
If you go to the demo site http://tinyurl.com/sp-iphone in your desktop browser it doesn't work but on the iPhone/iPod touch it does. This is because the iPhone Safari browser can handle the special touchstart, touchmove, touchend JavaScript events. The Android browser doesn't handle these.
I wonder if it would be possible to modify the Android browser to handle them?

Yah I've been browsing a couple jquery groups and it looks like they got this about working on the iPhone. I found how to move items using click-to-click but that is not what I'm going for.
I'll post here again if I get a response to anything.

Ok sounds good

Android vs iOS Browser Display

I have a theory that Android uses the CPU exclusively to display a webpage, while iOS loads the rendered result of the current window into the graphics buffer. This would explain the checkerboarding that you get on iOS that you don't on Android, why zooming on Android doesn't blur like iOS does, and why slow scrolling on iOS is so smooth.
Does anyone know if I'm right about this?

iOS display every Website in the same way. Visit a website that is not mobile and u see Android is faster!
iOS display not the whole website so its get good performance.
Edit me if i am wrong

It's actually the other way around. Visit a website that is not mobile and you'll see the Android default browser crawl. The checkerboard pattern on iOS is precisely as you described it: the CPU is not keeping up with page rendering, and it hasn't loaded that part of the web page into the GPU buffer yet. But it only happens to really large web pages with a lot of contents (a tech blog).
The Android UI lacks any sort of GPU acceleration possible, and it's been an ongoing issue for a while. The Android team responded that it wasn't done earlier on because earlier hardware just wasn't enough for it. All current Android devices are effected...
On the bright side, if you want smooth browsing on your Android phone, you can use Opera Mini. I'm using it myself.

Stock browser vs the rest

What browsers are u guys using ?
THUNDERBOLT

dolphin mini for regular browsing...dolphin HD for when i wanna watch HULU..

Default
-Monky_1

I like the default browser. Haven't had any problems yet.
Sent from my ADR6400L using XDA App

Using regular browser here, but I have Opera Mobile installed, gonna be giving that a try.

I think the regular browser is great but I just started using Miren and like it a lot so far.

I am using firefox 4, and it is pretty nice. I wish it were snappier, but it's feature set is so nice and the fact you can swipe right to see open tabs and swipe left for back/forward/bookmark, it's super convenient.

Xscope
Sent from my ADR6400L using XDA App

Been on dolphin hd for a few months now. I would use firefox more if pictures didn't look so bad.
Sent from my ADR6400L using XDA App

Xscope here
Sent from my ADR6400L

I use stock for most normal browsing. Have Dolphin hd setup as a desktop profile for hulu and the like.
Sent from my Thunderbolt using Perfect Storm xda app.

Miren Browser, for sure.
Sent from my ADR6400L using XDA App

Normal browser. I really like the pinch-zoom-out gesture used for opening new windows. Really spiffy and easy.

So, rally any of them then.. LOL No real distinct one is better than another..

Everyone has their own choice of browser as you can see. However, that doesn't mean a particular browser wont have features or semantics that wont appeal to you more than others, so try them all and see.
For the record though, I prefer Opera Mobile, but I also use Opera on my desktop as the main browser as well. However, some browsers do certain things better than others. I prefer firefox (for firebug and dynatrace http://www.dynatrace.com/en/) when I develop and SrwIron (chrome) is my fallback browser on the desktop if Opera wont work on a site.
Opera probably has the longest development track record (starting years ago with windows phones and symbian) for a mobile browser (and one of the longest for support on ARM processors in general). All but a wrapper that calls the code libraries (.so files or for those that stick with windows, .dll files) in Android's dalvik vm are compiled natively for ARM in c++ (since they use these libraries on windows phones and symbian as well), so they have the ability to run faster than the code that must be interpreted through the dalvik virtual machine. See http://my.opera.com/operamobile/blog/the-components-of-opera-mobile-11-on-android for more details on that.
Opera will also allow you to sync your browsing history, bookmarks, search history, favorite pages (the speed dial), etc to the desktop version if you use it. http://my.opera.com/desktopteam/blog/my-opera-synchronization-explained
Opera also has a pretty good track record for security and patching exploits. I'm leary of trusting any browser other than Opera or the native one built into Android, which has similar libraries as chrome (firefox mobile is probably okay as well, but it's still in the development phase so there could be bugs or things not patched quite yet). The rest of the mobile browsers other than firefox mobile (built on gecko) and opera (built on presto) are all mostly close to vanilla webkit clones (excluding the built in android browser similar to chrome) that aren't overly proven to be secure or have a long history of development. Since they're webkit clones (since webkit is currently the only stable open source platform choice for phones until the release of a stable firefox mobile), they're all going to tend to look somewhat alike and have similar speeds. That's not to say they are not secure, but they're mostly rookies to the game compared to Chrome/FireFox/Opera. Webkit rendering engine itself is well designed (with a history of being used on mobile phones long before android via nokia's built in symbian os browser), but how companies take that code and implement is is the problem. In the pwn2own hacking competition, chrome (the desktop version) was the only webkit based browser not to be susceptible to a major exploit.
Opera has its little annoyances like any browser. Mostly things like being ignored by bad web developers in the past that only cared about IE. However since firefox and chrome follow web standards like opera now and have a significant market share, this rarely happens nowadays. Though, sometimes I will stumble on a site using the desktop version that forgets Opera is also a desktop browser and gives me the mobile page, haha. For quite a while, McDonalds.com would do this.
Any of the more popular browsers should be good enough if you use good judgment, but if you're ever leary of a site, at least pick a browser you can disable plugins (flash and pdf readers) and javascript if needed, since those are the 2 main ways you might get hacked via a web browser. In opera mobile, you can type "opera : plugins" (without quotes and the spaces) in the url and you can disable any plugins you do not want to use. With that it's generally harder to monitor the system internals and connections on your phone versus a desktop pc (and the wonky permission control system [or lack thereof] in the graphical interface of android), it's better to be a bit more cautious.

I like dolphin HD

I use Firefox and the default one. For some reason Firefox has problems for me on facebook when i try to send a message
Sent from my ADR6400L using XDA Premium App

Opera Mobile is currently my browser of choice.

@yareally: a simple "I prefer Opera Mobile" would've sufficed. We get it, you like it.

[Q] looking for a better set up - how are you doing it?

Hi guys, I'm hoping to hear some better setups than I have come up with, so let me have um!
Here is the deal, I would like to start using my transformer1 and dock much, much more - and hopefully leave my laptop behind.
What I'm looking to do- I program in various languages, some heavy, some light, but I spend all of my time in linux and most of it on remote systems editing in vi. Seeing as how there are multiple ssh apps, and vi-ISH editors, one would think this would be easily accomplished.... not so much for me. I have found that developing on the tablet is a major pain, and sometimes there are cases I can't find a work around for. It has been over a month since I've tried, but from what I remember, various vim editors and ssh apps give me problems with the shift key, the escape key, typing numbers in various spots, and some instances the Control key..
I realize the more time that passes the easier all of this will become, but have any of you found a setup that allows you to leave your pc behind to get some work done in the command line?
Thanks in advance for the ideas

What I do
What I do when I need to use the command line is remote desktop into one of my servers and then putty from there. The remote desktop keyboard overlay works just fine for everything that I do.

Have you tried a normal keyboard via BT?
I do know they make software Programmer Keyboards that have the function keys (F1-F12) and CTRL, ALT, etc.
I don't know what that would translate to a hardware keyboard or VI

Can remote desktop work useable with Adobe products like Photoshop? Adobe suite is the ONLY tie I require with a Windows PC these days and would love to cut that too lol

Android phone powered Desktop

Android devices are so powerful today, and the hardware is becoming so powerful that I don't think that the software is utilising that.
We already have much of the technology in devices of today to enable a desktop environment to be streamed from our phones.
Display output: Chromecast (wireless display), MHL (Wired display & charger), etc.
Input methods: Bluetooth Keyboard & mouse, Accelerometer (to emulate mouse input), etc.
UI: Separate Launcher for the desktop UI.
With Microsoft bringing Windows 10 later this year as one OS for both the Phone & Desktop, surely that will allow them to work better in sync with one another, but that will still require a separate desktop computer and phone to create this kind of experience.
But Google now has the chance to simply output a separate UI from the same device that can display a phone UI all at the same time.
If we look at past launches of major Android builds then this coming Google I/O would be the perfect time to announce something like this, since they say that they usually deliver one major build that focuses on UI, and then one that focuses on major feature integration.
And not only would this allow for us to take our desktop with us everywhere in our pocket and connect wirelessly to any compatible display but also it could enable people in poorer economies to buy one device which could give them better access to the internet with a portable display integrated into the device, and also they could connect to the larger displays to browse the web or work on office documents with apps such as 'Google Docs'.
This could really be useful for people who wish to use their device in the work place too.
With Android mobile now offering multiple user profiles on their phones, surely they could create one profile for work, with all of their work apps available in both their phone and desktop UI's, but also a personal profile with all of their media applications & games available when out of work.
The desktop tower may still be useful for a few years to enable support for legacy applications whilst we are waiting for those applications to be ported over to Android/Android Desktop, but that shouldn't take too long considering how quickly we are see'ing apps becoming available to Android offering the kind of services that many of us desire, and if the developers only need to create one application back end for both the Desktop mode & phone mode, then it will be much quicker to bring apps to market with a small bit of time required to make a UI which can be scaled between the phone & desktop mode well.
There are multiple projects trying to create this very experience, but if it was a major part of the Android OS then finally people will get the experience that many people are waiting for, you only have to look at the comments on the developer pages of these projects to see that many people want this kind of experience.
With 64-bit now supported in Android too there is less of a reason to hold back this kind of experience.

I agree totally. Is this the only thread on this subject? Was going to setup Chromecast for video and Bluetooth for keyboard, mouse and audio. Doing this on a Jiayu S3A which is very powerful. Would like one place to discuss what works and what doesn't. Launcher options also need to be discussed.