These jquery.mobile-1.4.2.min.js and jquery-1.10.2.min.js are auto included in all of my HTML pages, while developing the UI screens using jquery mobile.
But this Auto-added JS files causes a delay/sluggishness while navigating between the multiple screens.
Is there any way to improve the sluggish behaviour?
I've used the Worklight 6.1 project you've emailed me, added the Android environment to it and ran it in the Android Emulator(!) (with API level 19 - Android 4.4) and did not observe any sluggishness.
In fact, your application does not even contain any animations. The pages simply switch from one to another. So, no slowness even in the emulator...
You'll need to create a test case application demonstrating what you are referring to because right now it is not reproducible. Also mention if you are testing it on a device or not - which device model and which Android version.
Related
I am just wondering what is the best approach for web development for across all devices.
I just want to know if it is better to have 1 css file for all devices or a css file for individual devices?
Because of http 2 it can load multiple files on one TCP connection rather than using multiple connection which http 1.1 did.
The reason why I am asking this question is that when you go into amazon or linkedIn for example (even stack over flow). if you click "inspect" the site, click on "toggle device toolbar" and using an iphoneX or galaxy s9 setting (for example again). Hit refresh and turn "toggle device toolbar" off.
You would notice that the css looks like its still remembers the mobile phone as if they detect the device and load a css for that device rather than having a single css that fits for all device.
Unless you need to create a completely different design for seperate devices (meaning your site is somewhat complex, and even then not always the best idea), you should not think of designing for "devices" but rather device attributes like screen sizes, which is done via media queries. These can all be in the same CSS file, or you can split them into separate files to improve load time.
I am reaching out because I feel like we can't be the only ones who are experiencing this problem, however right now based on my research I feel quite alone!
Last night I got the android update (4.3) on my HTC One which I installed right away. Now the app we developed with Sencha Touch + Cordova hardly functions at all. This is after a successful submission to the app store and successful testing in multiple android devices.
Some of the issues we are experiencing:
Back button in list view no longer responds
Page transitions (left->right and right<-left) functioning bizarrely. For example the title transitions right to left while the body left to right, simultaneously.
The title on our home screen suddenly reverting to "undefined."
I know probably all we need to do is get back to the emulator and just start debugging, but we really would like to know whether anyone else has experienced problems like this and could help point us in the right direction on some solutions.
Also the problems persist after updating to the very latest version of Sencha Touch 2.3 which has Cordova integrated.
The following patch resolves the issue!
http://www.sencha.com/forum/showthread.php?273492-Back-button-broke-in-navigationview-Sencha-Touch-2.3-Android-4.3&p=1009111&viewfull=1#post1009111
Looking forward to seeing this implemented in the next Sencha Touch update.
I'm developing a win8 / winrt xaml app. In my app I need to know if the orientation of the tablet is vertical or horizzontal..
Where can I find this information? I tried to use ActualWidth and ActualHeight properties but without any success.
I try to take a look at:
Frame
Application
Window
But I can't find what I'm looking for!
Any suggestion?
static property Windows.UI.ViewManagement.ApplicationView.Value will return the following values.
FullScreenLandscape
Filled
Snapped
FullScreenPortrait
Actually, since the ApplicationView.Value is deprecated in Windows 8.1, I'd recommend not using that for your app now. DisplayProperties provides some data here in their API. Also, depending on your scenario you may not want to think only about the device orientation but the Window size itself that your app is in. In Win8.1 since you can have 50/50 split, your app may be in a "taller than wider" viewport which effectively is a portrait view as well.
If your app relies on knowing portrait to make assumptions about edges of the physical device, then that is different, but consider looking at Window size and determining if "taller than wider" is a good indication for your app and use that to trigger any changes.
I am working on a web app that will be run off a local server on Windows 8 on Chrome. Unfortunately, Chrome doesn't seem to handle touch events very well. For example, often instead of clicking on a button, it will select it instead. Is there any way I can make it behave more like native touchscreen apps do?
I can't make it a metro app because I need to talk to a Python service.
I've done some testing in Chrome with a touch screen and don't seem to run into this issue (of course not doubting you are though!). If you have a site I'd be more than happy to check it out.
One option is to try scaling the content larger, I'm wondering if your touch surface is very sensitive to tiny movements upon touch and treating it as a touch/scroll ie select. Try a simple test in the browser to start by increasing the size before trying any css scaling transforms (which I'm not sure how in this how well that approach would even work)
What type of hardware is it being tested on?
Can you elaborate a bit more on the python service? What part of the service makes it so you can't interact with it? Is it just an http service object or something else?
I want to create an application that has multiple touch surfaces, preferably using the Metro/WinRT APIs. However, much of what I've read indicates that Metro is confined to a single (primary?) monitor. Is that true?
Metro style applications are full screen, single screen only. There is no way to have a dual-screen application.
I have tested Win8 with multiple monitors. The metro interface is only ever available on a single monitor, with the othe always displaying the 'traditional' desktop. You can switch which monitor displays the metro UI, but cannot render it on both.
Microsoft heard this request and added multi-monitor support to Windows 8.1. See the Windows.UI.ViewManagement namespace, specifically the ProjectionManager and ApplicationViewSwitcher classes. There's also a Projection sample for this.