O4W and older browsers.

OpenInsight for the Web (O4W) is fast becoming, if not already is, Revelation’s leading web development tool. This is no surprise when you see just how easy it is to create Web 2.0 compliant browser based systems against OpenInsight’s own Linear Hash data, TigerLogic’s D3 data, Rocket Software’s U2 data and also SQL data stores – the latter 3 via the built in dedicated data connectors.

However, being fully Web 2.0 compliant does come at a small cost. O4W uses advanced web technologies to deliver an interactive and dynamic web experience. To fully benefit from this, users and developers should use the most current versions of their web browser. At the time of writing this blog posting, these versions include; Chrome 3, Firefox 3, IE8, Opera 9 and Safari 3.

However, that is not the be all and end all. Developers and users may chose to use older versions of their web browser, but at the risk of reduced functionality. Developers who choose to support these older browsers should undertake their own careful testing of any plug-ins and functionality that their web solutions may rely upon. Minimally acceptable browser versions currently include Chrome 1+, Firefox 2+, IE6+, Opera 9+ and Safari 3+.

As a default, users accessing an O4W based system with an older browser will be presented with a message that their browser is unsupported. They can continue, but the message remains at the top of the O4W forms as a reminder that something might not work totally as expected. This can be seen if you run the Online O4W demo in an older browser or with IE8 running in compatibility mode.

The good news though, is that the javascript to create and display this message is stored in the O4W configuration record and this functionality will be updateable via the O4W Maintenance/Config Records screen in version 1.1 and later.

However, for the moment (version 1.0) developers can disable or modify the message by editing the appropriate CFG_O4W record in the O4WCONFIG table and clearing out or changing field 45 as appropriate. This can be either ‘CFG_O4W’ globally, or *CFG_O4W for a specific application.

Updating this will be easier from O4W version 1.1 (to be included in OpenInsight 9.2.1). From version 1.1, O4W will have an updatable field via the DB Management, O4W Maintenance, configuration Records, Browsers Tab.

Partial content c/o http://www.revelation.com/ discussion forum.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s