I have few SSRS reports (with charts, gauges etc) deployed to the server and they all work fine but not so well when viewed as well worked upon on cell phones/tablets.
The users find difficult to choose the report parameters, selecting from drop downs and also presentation of data through charts, gauges etc.
I am thinking to modify the SSRS report for cell phones but not sure how to progress. I have searched and started reading some blogs but thought of asking suggestions of experts here who may already dealt this.
I have sample RDL files (deployed to the report server) that I can post here but they are any other typical SSRS Reports with various parameters, charts, gauges etc.
Many thanks.
Please share your thoughts.
Looking for an solution for the same problem, I have found this answer. I have applied it ant it worked!
My context is:
I'm using the ReportViewer Webform component:
Microsoft.ReportViewer.WebForms, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
It tested in Androind Asus Zenphone 2. Using the default browser and Chrome.
It worked at desktop chrome too.
The code change:
Replace:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
with the following tag:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Are the reports being delivered using Report Manager, SharePoint or a ReportViewer control in a web page?
You're using SQL Server 2008 R2, so the only supported browsers are Internet Explorer, Firefox and Safari and although it doesn't explicitly state it this almost certainly refers to the desktop versions of these browsers so there's no guarantee that mobile versions will work the same way.
So the SSRS technology you are using is not designed with modern day mobile devices in mind. That said you can still try to make this work: You need to ensure the users are using either Firefox (on Android) or Safari (on iOS). Note that Chrome (or related browsers) are not supported at all. You need to consider how the report security is going to work (e.g. only Basic authentication is supported with Safari).
In terms of layout and report components, you'll have to do some trial and error testing to see what works - and remember it may not work on all devices. You might want to consider providing links to render the reports as PDF files, which have much better support on most devices. There is a great blog post by Adam Aspin on some layout techniques for reports on mobile devices here: https://www.simple-talk.com/sql/reporting-services/mobile-bi-with-sql-server-reporting-services/
Generally though, if you're trying to design a solution for mobile devices you really want to consider an upgrade to a more recent version of SQL Server which has support for more browsers (including Chrome) and security options.
Related
What is the best way to test my website across various mobile browsers AND various versions of each of those browsers.
Additional Info:
Most of the online cross browser testing support wide range of desktop browser testing, and quite a range of mobile devices. But they don't seem to offer various versions of mobile browsers on those devices.
This similar question is quite old and it is surprising that in spite of the proliferation of mobile devices and focus on responsive designs, testing services for mobile is not catching up.
Major mobile browsers I would like to target : various mobile versions of Safari, Chrome, Firefox, Opera, Dolphin, UC Web etc
Just wanted to note this and this good alternative to online testing services for desktop browsers. Maybe something similar exists for mobile browsers too?
I'll suggest that both Opera's "device mode" is a really good for a first crack. But nothing beats actual device testing. I have found the odd case where Chrome's iPhone mode renders something different than what the actual phone does, but I would say it is about 90%. And the fact that it is so much easier to tweak code, and refresh using Chrome on the desktop rather than tweak, and refresh on phone, that I tolerate the 10% difference as long as I can. Then I just verify on an actual device after I am done with Chome's device mode.
I have not used Opera's device mode, but have heard it is good too.
There is a tool called as https://www.browserling.com/ which can be used for Desktop and Mobile testing(Android)
I don't think there is one way of doing cross browser testing across various mobile browsers and versions. It all boils down to what you want to do?
It is impossible to cover ALL browser combinations and versions. So my suggestion based on experience would be-
If you have too many combinations in mind, use a combinatorial tool (pairwise testing) from here - http://www.pairwise.org/tools.asp and reduce the number of permutations to get the best coverage.
Then go to Android and Apple website to see what the most commonly used phones and versions in the US, Europe and Asia region are based on where your customers are located. They have all these stats publicly available on their website
If you have google analytics see what browsers, versions and phones your users most commonly use to access your website
Now, you will have a list of devices and browser versions which is more focused.
Check what budget you have to invest in cross browser testing. Based on that I would recommend buying at least a couple of phones and tablets based on the usage statistics you got in the first 3 steps. Then, you can choose from a number of cross browser testing tools/services like
BrowserStack
Amazon Devices Farm
Saucelabs
Now atleast you have a more scientific way of doing cross browser testing :-)
I am using a jQuery plugin for allowing #mentions (tagging someone by inputing their name after an # symbol). The plug-in can be found here (http://podio.github.io/jquery-mentions-input/), and it has been working rather well. The only issue (which may or may not have to do with the plug-in itself) that I've come across is that on certain Android devices, and particularly on certain mobile browsers, these #mentions will not work. Interestingly, I discovered that if I turned Predictive Text off on these devices, it seemed to make the issue go away, but I am curious if there is a way to make it work without having to create a possibly poor user experience (i.e. forcing the user to turn predictive text off in order to tag). The github repo for the plug in has addressed that there are some issues on Android, but it does not specify if that is referring to an Android App, or the web browsers for Android. If anyone has come across a similar issue, I'd love to hear about possible solutions.
As responsive design and mobile web development become the norm, like others I suspect, I find myself testing and bug fixing on a wide range of mobile and handheld devices. Traditionally, errors in the CSS with layout or presentation were made substantially easier to fix using things like firebug or the chrome dev tools. Even JavaScript errors could be picked up and debugged in these tools.
However, the same sorts of errors are now significantly more difficult to isolate and fix. We no longer have the error console to see when JavaScript errors occur, we don’t have an inspector (god, I wish we had remote debugging on all modern mobile browsers). I’ve got an annoying bug in Opera (which I know can be remotely debugged: http://dev.opera.com/articles/view/remote-debugging-with-opera-dragonfly) and I’ve resolved others in the Android browser and Safari for iOS through brute force rather than any real technique, but I was just wondering what are the preferred tools, techniques and tips for debugging responsive issues on mobile devices?
Thanks
did you look into weinre? gives you a (limited) remote web inspector (after some set up)- solved some real problems for me!
Opera Dragonfly (I have an obvious bias here ;-)) and the indispensable Microsoft Fiddler HTTP debugger if the phone/device allows you to configure a proxy server. Fiddler helped me debug many problems before Dragonfly grew powerful enough, and is still a fallback if I have problems with Dragonfly.
How are you doing solving the annoying bug in Opera, BTW? :)
You can use Chrome's remote debugging feature on Android. For Android and iOS you should take a look at Adobe Shadow which gives you a remote inspector too.
And for iOS in the future: iOS 6 will have a built in remote inspector, easily accessible from Safari's debug menu.
Good article here also on how to use the Opera mobile emulatore and dragonfly remote debugger to debug Opera related bugs...
http://mobile.smashingmagazine.com/2012/08/30/responsive-designs-opera-mobile-emulator/
I got really confused of all the W3C specifications and implementations of different browsers.
I have a list questions:
I found this page from W3C's website: http://dvcs.w3.org/hg/webevents/raw-file/tip/touchevents.html
And I found this page from apple's website: http://developer.apple.com/library/safari/#documentation/UserExperience/Reference/TouchEventClassReference/TouchEvent/TouchEvent.html#//apple_ref/doc/uid/TP40009358
They are talking basically the same thing.
So my question is : did apple published all the multi-touch apis first then W3C followed apple to make all the specifications? or did W3C published the specifications first then apple followed the specifications to make a new version of Safari?
2.Is the Touch Events Specification a part of HTML5 specification?
3.If I write a web page that uses multi-touch to interact with users, can the users be able to use this web page in IPad, Android devices and Windows Phone 7(Mango)?
Or do I have to write different code for each different platform?
Thanks
The Touch Events Specification is based on events cloned from Apple Safari's implementation, although it adds significantly to it. It is not technically part of HTML5. The other platforms have also copied Safari's touch events. It should be possible to write code to the original Apple Safari reference documentation and have it work on iPad and Android. I don't know about Windows Phone 7 (Mango).
We have an existing web site, and I've been asked to test its compatibility with mobile browsers.
I've installed the Android SDK onto my desktop PC. I'm able to view my localhost site in the emulator, and I have identified a number of glitches in the page layout which occur in the Android browser.
But since none of these issues occur in any desktop browser, I've been struggling with how to debug them. For example, in Firefox, it's very easy to use Firebug to see what stylesheets have been appies and to adjust them on the fly to see how it affects the layout. But I haven't found a way to do anything similar on the Android emulator.
The question is, short of trial+error, how do I go about working out what is causing those layout issues? Does the Android browser (or the Android SDK) have any kind of tools that are useful for debugging CSS? If so, how do I use them?
[EDIT] I haven't found a solution to this, so I'm throwing open the doors to the bounty hunters...
Weinre is probably the closest to what you're looking for:
If what you're looking for is something that allows you to tweak layout in realtime it should make you happy.
https://chrome.google.com/webstore/detail/geelfhphabnejjhdalkjhgipohgpdnoc?hl=en-US
https://chrome.google.com/webstore/detail/cllkoedgiefnomcccogcalmjogjfcpji?hl=en-US
https://chrome.google.com/webstore/detail/cghdkdcepiflkhaddpomjehcmdojgobh?hl=en-US
I found several options that appear as though they should work for you if an emulator/simulator will suffice or at least get you started. The benefit to this is that the Chrome Developer Tools appear to work with the add-ons!
Personally, I would much prefer to do this on actual Android hardware. In usage a touch screen handset is quite different to even the most accurate emulator; things such as gamma, pixel density, performance, touch interaction (are your links big enough?), portrait/landscape orientation and even the fact you hold it in your hand makes it quite different to the desktop experience. If you want to see how well your site works on mobile/Android, get a cheap second hand device to test on!
As for the debugging; I always include my own "log" function which creates a div#console if the firebug/browser console is unavailable. This works reasonably well for debugging on a handset with the caveat that it covers part of the content. You can then print out the current style of an object with something like
log(window.getComputedStyle(document.getElementById("myobj"));
Note: The above will not work in IE.
You may have already seen this, but the SDK Documentation Site has some basic information on developing and debugging web apps on Android:
Web Apps Overview
Debugging Web Apps
Hope that Helps!
I don't know how you detect a mobile device but I detect a client with the user agent. Because of this I can simply send a different user-agent string to test CSS which works fairly well.
For Firefox I use User Agent Switcher. Additionally I use the Web Developer tool not only to view all settings but also the Resize option to simulate the viewport width.
Apple's Safari has a developer extension and within also a User Agent Switcher. You can add your own User Agent string.
Chrome provides tools for doing this now. Just visit:
chrome://inspect/
With your device connected and ADB running - you can then use all of the Chrome web element inspection tools. This works with the browser, but also with any app that renders in a WebView (e.g. Cordova).