I've developed a web application which uses jWebSocket.
I've put it together on an Apache Server and accessing the site with a desktop browser works fine.
But it's not working on mobile browsers, that is, I can see the static website but no dynamic changes are made (using WLAN; on a laptop using the same WLAN everything works). The required ports can be reached but no connection is being established with the jWebSocketServer.
I've tested it on iPhone with Safari 6 and on Android phone 2.3 with WebKit browser and Opera 12.
At least Safari and Opera natively support WebsSockets, so I wonder if there's a general difference between mobile and desktop browsers regarding this functionality?
(On the Internet, I found nothing about mobile web apps with jwebsocket, there are clients for native apps but this doesn't suit my need.)
Thanks in advance!
Related
I'm trying to build a live video streaming application from a usb camera to an application running on a remote desktop. I've researched protocols like RTMP, RTSP, WebRTC. According to my understanding I can't use webRTC since it's only compatible in the browser and I'm not building my application for a browser here. Please help me choose the right protocol and also the media server.
You can, and many applications do, use WebRTC outside the browser. WebRTC implementations are available for many different platforms including iOS, Android and embedded systems.
You can even use Headless Chrome if you want to use the Chrome APIs without the visual parts of the browser.
We are implementing a javascript library that uses the camera of the device on mobile web browsers. It was working well on Android using Chrome and some versions of the default Browser app. Since iOS 11 and Safari 11, we are able to access the camera on iOS too.
I was wondering if we can use this API to turn on the LED flashlight of the device. And in what platforms and browsers would that work.
How does Google Chrome make a hybrid app (i.e. one that works on the desktop and one that works out of the Modern UI, and that are switchable)? What new Windows API do they call?
The only applications that can be "hybrid" are browsers. See here (link to Microsoft whitepaper on making a browser desktop and metro enabled).
What would be a good workflow on OS X for testing client-side code (HTML/JS/CSS) for browser compatibility and other issues across all major browsers?
I do my web development with Textmate (HTML and JavaScript), CSSEdit (CSS), and use Safari's Web Inspector, mainly for checking the JS console. I do have Parallels with Windows XP on it, but haven't tuned it for web development at all.
We develop on Macs too so what we usually do is testing and debugging in Firefox with the help of the Firebug plugin and the Web Developer toolbar. We then cross-check stuff in Chrome/Safari using Chrome's built-in Inspector in case of any discrepancies.
For testing on Windows we use a dedicated Windows machine that we can access through Remote Desktop which has some Virtual Machines running various versions of Internet Explorer (one VM for each would be nice, but we just use one for IE6, one for IE 7 and use the IE version that's installed on the remote machine as the third option).
A colleague of mine has a setup with VMWare and running IE right off his Macbook in a VirtualMachine.
As far as I can tell debugging in IE 6 is pretty hard, but some of the newer IE versions have a pretty decent Inspector similar to the ones in Safari and Chrome.
So I am developing a Sencha Touch application in Windows. I want to test how this is going to behave on iPhone/Android/BlackBerry phones.
I'd rather not make it public just to test it by navigating to it from each OS physically, although I will be doing that before our official release. How can I emulate the phones on windows. Is there anything I can use to emulate Blackberry/iPhone on a windows machine just to test how the web page is going to be rendered in those devices?
I know the Android emulator I can run through Eclipse, but what about the other two?
You need a Mac to run the iPhone/iPad simulator. Blackberry can be done on windows though: http://www.blackberry.com/developers/downloads/simulators/
You might also consider delivering them to these devices as apps using phonegap, which plays nicely with sencha touch.
If you just want to see how the app would look and behave while developing, just use Google Chrome. You can enable the very good 'developer tools' to do various checks.
Install and run on Ripple Chrome Extension
Check out the number of devices / platforms it supports
...
...
iPhone 3G / 4
iPad
Nexus One
Nexus S etc..
In order to start developing applications using Sencha Touch, it is highly
recommended that you have a working web server where you can host your
application. It's possible to develop Sencha Touch applications, viewing local
folders with your web browser. Without a web server you won't be able to test
your application using any mobile devices.
You can run the application on your web browser by using:
http://localhost/your_app_folder
Using Safari web browser to examine your Sencha Touch application during
development, and the Safari Web Inspector is a huge part of that. Both Chrome
and Firefox have similar tools (Chrome Developer Tools and Firebug for Firefox),
but as iOS devices use Safari for their web browser.