Being browser smart for WaveMaker || Part-3
Being browser smart
The reality is that not all browsers are created equal. Things
such as rendering speed, developer support, and support of HTML5 features can
vary widely among browsers. While there are many browsers out there, more than
many people even realize,
we shall concern ourselves only with the most common
ones. Of those, we can generally categorize them into three families based on
their underlying layout engines. Here, the "big three" for both
desktops and mobile are—Gecko: used by the Mozilla Foundation for Firefox,
WebKit or Webkit forks: used by Apple's Safari and Google's Chrome and Trident:
used by Microsoft's Internet Explorer.
WaveMaker applications make heavy use of JavaScript in the
browser. Therefore, the faster a browser can parse and run JavaScript, the
faster a WaveMaker application will generally run in that browser. Deployed
WaveMaker applications will run in the most common browsers. For older versions
of Internet Explorer that lack HTML5 support and have rather slow JavaScript
engines, we can use plugins such as Google Chrome Frame. Chrome Frame enables
our JavaScript application to run in the Chrome V8 engine even when the
application is loaded from an older version of Internet Explorer. You can learn
more about Chrome Frame at:
"In June 2013, Google announced the retirement of Chrome Frame."
We
may not get to dictate what browser our users use to run our application, but
we do get to choose what browser we primarily develop in. Here too, some
browsers are better than others. As such, Chrome and Safari are the preferred development
browsers by most WaveMaker developers today. In this website, we'll be using
Google Chrome, as it is fast, has excellent developer support, and is available
on all major platforms. You are welcome to use other browsers; however, we will
only using Chrome in this web.
WaveMaker applications work in the most popular modern browsers.
However, those browsers may interpret your Cascading Style Sheets (CSS),
JavaScript, or resultant HTML differently, and you'll want to test your
application in the browsers your users will be using before you declare
victory. This testing may require using another system or a virtual machine
(VM). Someone developing on OS X, for example, might use a VM running Windows
in order to test with Internet Explorer. WaveMaker handles most of all the
cross-browser issues for you, and your application may "just work" in
other browsers. However, you'll still want to test it.
"If something isn't working right, clear the browser cache to ensure
the correct file loading. We'll discuss why in Chapter 15, Debugging."
As a general rule, the more customization you do, the more
cross-browser testing you'll want to do. I suggest you first get your
application working in a developer-friendly browser to flush out the general
issues. Then, cross-test in other supported browsers to get the browse-specific
issues before declaring the application as done.
To see the Previews post click the link below:
Visite regular the Web Tutorials for learn more about the leasted technology.
