Our pages, who are in cache,
Hello be thy name.
Thy external libs come.
Thy rendering be done
On IE as it is on Chrome.
Give us this day our daily JSON feed
and forgive us our syntax
as we forgive designers who have never coded.
Lead us not into frustration
but deliver us from pre-compilers.
For thine is the interface, the user experience, and the business logic
Looping forever and ever.
if there is a way to create a responsive website where jQuery Mobile loads only in the mobile versions. The problem is that if I load jQuery Mobile libraries, they will load even in the normal or wide displays...
This is something I struggled with as I was writing my book, Creating Mobile Apps with jQuery Mobile, and with a current client I’m working on now. Let's look at a few ways this can be handled...
The release of the iPad mini validates an entire line of tablet sizes. Essentially, it’s another case of Apple coming along and leapfrogging another existing market. The Google Nexus 7, Kindle Fire, Nook Color, and Samsung Galaxy Note have fit this small tablet bill for a while. Now that Apple has thrown its hat into the ring it will sell millions and come to dominate (as usual) our existence as web developers. But the iPad already accounted for 98% of all tablet web traffic. So how does the iPad mini really change anything?
The Big Question
In developer circles, UX conferences, Forrester industry conference calls, and even on my own blog, I’ve heard people asking a consistent question. “What are you guys doing about iPad?” There are, of course, some who are bothering to make native experiences and that is certainly a valid answer… for one manufacturer at a time. Web developers and designers who have been asked this question have always had the option of just using the standard desktop view and it was usually good enough. After playing with the Nexus 7 and the iPad mini for 24 hours I can tell you first hand, the game has changed. Read more...
In today's TechCrunch conference, Facebook CEO Mark Zuckerberg blamed their focus on HTML5 for a failed mobile strategy saying, "The biggest mistake we made as a company was betting too much on HTML5 rather than native." He is wrong on this for several reasons that I will detail. The main thing to realize is that this is not a lesson for startups to take to heart.
I am building an app using PhoneGap and JQuery Mobile.
JQM loads every page via ajax and even if the header and footer are fixed it still expects every page to have them which is absolutely disgusting. If you make a change in a header then you have to do it on every single page! I have found a great article that dynamically inserts the header and footer into each page (http://blog.intechnica.co.uk/2012/03/30/persistent-navigation-jquery-mob...) but this is still annoying for sub-pages and making sure the correct tab is highlighted.
Since I am not using JQM themes, icons and its page navigation is very basic I am thinking if I even need to use it at all? I can just use JQ (not JQM) AJAX to update the relevant parts of the UI as needed.
What do you think?