True Cross Browser Web Applications

Having a truly cross browser web application is like being truly happy. The moment you get there, someone is going to bring you up to date and ruin everything. And like happiness, you will never attain it if you chase it. And like happiness, it is a byproduct of devoting yourself to something that you are passionate about.

Developers tend to believe that the moment they start using a JavaScript library that works across browsers, they are immune to the problem. Nothing can be further from the truth. If you use such a library, this only means that the code inside the library is compatible with many different browsers. It does not automatically follow that any new line of code you will write for your application is going to work the same way across browsers. This is a hugely misunderstood concept.

With your first line of Javascript or HTML you are in cross browser hell. Let me repeat this. With your first line of Javascript or HTML you are in cross browser hell. Virtually in every project browser compatibility of the application is the responsibility of the development team. Ensuring that web applications work in all the major browser brands and their versions is an important, time consuming and difficult task. Most teams just give up and let it all flap in the breeze. Even the smallest attempt for browser compatibility crashes and burns with the first update to Firefox or Chrome and the team is back to square one again. I’ve seen IT departments that force their users to use one particular browser to access their applications. This is ridiculous and yet it is happening every day. How can it not happen? There are many nuances that needs to be mastered for true browser compatibility. Development teams are not focused on technical details of browsers and their implementations of JavaScript and HTML. They are focused on implementing business rules in code and delivering applications and rightfully so. That’s what they are supposed to do. They should not be punished because a few industry giants could not get their act together and created the worst standards in the most important platform ever created: the web browser. It is a classic example but I’ve got to repeat it here at the risk of being banal. Can you imagine that some TV sets working with some shows but not with others? Can you imagine watching House M.D. on a Sony but having to switch to a Samsung to watch Entourage?

In Formspider, browser compatibility is our responsibility. You can focus on what you are passionate about; building the best health care system, HR software or public finance application. Browser compatibility will be the byproduct of using Formspider. We take care of the platform problems. This is our job. It is what we do everyday.

Formspider applications are truly happy. It is not just the Formspider JavaScript library that works across browsers. Every application that you develop with Formspider works across browsers by default, because you only code in PL/SQL. Formspider has a very simple intuitive XML notation that helps you design your screens. It eliminates the need to be an HTML/DOM expert. We test Formspider with every major browser out there so that you can focus on your business problems knowing that once you code them all in PL/SQL, they will work on any platform.

Platform independence was one of the greatest benefits of Oracle Forms. The principle is up and alive in Formspider.

Yalım K. Gerger

Comments

Popular posts from this blog

Powerful Free Webinar Network for Oracle Developers

PL/SQL Developers! Formspider 1.9 is Out