I am developing a mobile web app targeting Android, IOS, BB.
In order to be able to do remote debugging I have found Adobe Edge Inspect, Google Developer Tools, Web Inspector on Safari,
Is there a better way of doing remote inspection?
Thanks
I found WEINRE really helpful.
weinre is a debugger for web pages, like FireBug (for FireFox) and Web Inspector (for WebKit-based browsers), except it's designed to work remotely, and in particular, to allow you debug web pages on a mobile device such as a phone.
If you aren't familiar with FireBug or Web Inspector, weinre isn't going to make too much sense to you. weinre reuses the user interface code from the Web Inspector project at WebKit, so if you've used Safari's Web Inspector or Chrome's Developer Tools, weinre will be very familiar. If you're not familiar with Web Inspector, the links above to Google's and Apple's documentation will be useful.
Related
I want build site using Sitecore(7.2) and also make it offline. Our requirement is not to use headless CMS. Is there any way to build or make it offline?
Internet websites cannot be delivered 'offline' without having all possible data delivered to the device so that it no longer needs to connect to the internet. This sounds less like a website, and more like an app that somebody would install?
If so, you probably DO need to look at headless and building an app that connects to the APIs for updates.
You might need to be more specific about the business use case because it seems contradictory to want to use a web application software that delivers web content, without using headless, and works without the web.
As already suggested that internet websites cannot work offline so either you have an app or intranet website.
Considering as an app you can consume sitecore OData apis for Content/Media however it will not work for Presentations and you have to implement your own mobile designs based on Xamarin or native.
For odata related information you can refer below link:
https://doc.sitecore.com/developers/90/sitecore-experience-manager/en/the-odata-item-service.html
Once you get the response from api, you can locally store it in your local db of app
I'm trying to get Google authentication working against Azure App Service from a web site and later hopefully from Cordova. There is a lot of information related to the old Azure Mobile Services, but not much on App Services. Microsoft did exclude tutorials on how to do it from web.
I included <script src="http://ajax.aspnetcdn.com/ajax/mobileservices/MobileServices.Web-1.2.7.min.js"></script>, don't know if this is still current?
Any pointers on how to handle authentication are appreciated!
This is possible using the Authentication/Authorization feature. Refer this article for more information: https://azure.microsoft.com/en-in/blog/announcing-app-service-authentication-authorization/
https://azure.microsoft.com/en-in/documentation/articles/app-service-mobile-how-to-configure-google-authentication/
AFAIK, there is no native support for Cordova in Azure App Service Mobile App. You will have to implement this yourself.
I'd like to understand if there's any cookie downloaded in the Desktop/Mobile browser, while browsing the MobileFirst Platform's Mobile Site.
Is there any information written inside it ?
Thanks in advance.
Typically, yes, there will be a cookie called WL_PERSISTENT_COOKIE used for working with authentication realms - you can find out more here.
In general, it's not too hard in most browsers to see if a cookie is set by any particular site, including the MFP mobile web environment - for example, here are some instructions on how to do that in Chrome.
I just started learning web services. In bottom up approach, I have found some examples without being deployed in any application server. I mean a standalone web service application.
Here is an example of such type.
I have also given a try and done a walk-through of deployable simple web service examples.
So far to my learning of web services, I got to know that firstly, bottom-up- approach is not recommended. Now, in bottom-up approach, this standalone web service. When is it applicable to follow standalone web service procedure?
Endpoint.publish();
I guess, this approach is provided just for beginners and not to follow as a real-time practice. Is my interpretation correct?
I would make my application as a standalone web service if it will have multiple clients like:
Web Client via a web browser
Mobile App Client
Desktop Client
Then I could build every one of them alone using whatever the technology I prefer, and make it consumes my standalone web service.
For example, You could imagine the guys behind Twitter started developing it by building their core system as web service, then they build an independent web interface application for it, then they built the Twitter Android and iPhone APP, and another one came and introduced a Twitter Desktop client like Tweetbot and TweetDeck ... etc
i've searched the site for this answer but couldnt find a good answer.
My client has a computer with Windows7 Home Basic Installed in his workstation (Thank you HP).
and i need to install a web service on IIS. Web service is written in c# (.asmx). When i installed IIS into that windows, i've realized that there is no IIS comsole available in windows7 home basic machines.
is there a way to register web service from the command prompt? this web service is a middleware for communication several mobile devices with the sql server on the machine so it has to be able to connect form outer ip's too.
I've tried IISExpress but it only lets connectiong from localhost.
I cannot format his harddisk, also my client doesnt really want an edition upgrade.
Thanks for spending your time.
I did a quick google search on hosting a web service (*.asmx) without IIS, and found this article: Run ASMX Without IIS. A quick glance at it looks like you'd wind up writing your own host and implementing your own web server.
If this is the only solution available, I think you'd be far better off to rewrite your ASMX web service as a WCF web service, and then either self-host it or host it in a Windows Service.