Cheat Sheet for HTML coders using O4W

Whilst the wizards in O4W can help developers and power users to build some very nice online database driven applications in super quick time and without the need to write, debug and maintain Web2.0 code, it is no surprise that the true power of O4W is held within O4W’s extensive API.  However, whilst most OpenInsight and ARev developers take to building web pages using the API like a duck takes to water, HTML coders with only a little (or no) BASIC+ knowledge might flounder and find themselves on a shallow, but still unwanted, learning curve.

It is for this reason that Bryan has put together a very, VERY, useful cheat sheet to help developers with HTML knowledge to quickly and efficiently apply that knowledge to building O4W pages using the API.  The cheat sheet is split into three key sections with each showing the HTML tag, attribute, style, etc. and the corresponding O4W API attribute (I hope that I am using the correct terminology here, but someone will correct me if not).  The three sections include:

  1. A non-exhaustive list of the HTML generated by O4W.
  2. A non-exhaustive list of the attributes and styles that O4W generates.
  3. A variety of HTML5 compliant APIs used to support both mobile and newer (HTML5) browsers.

O4W API calls generate HTML in addition to javascript, and occasionally it is useful to know which O4W call generates which HTML.  For example, when searching the internet for a particular solution to a problem, the results will usually be displayed as “regular” HTML; to convert that information into useable O4W calls, it is important to know which O4W calls will return the desired HTML.  This cheat sheet is therefore especially useful when used with the main O4W Reference Guide which documents all of the O4W API calls.  If you are familiar with HTML, then you can look-up the HTML in the left column of the table and then the sheet will give you the corresponding O4W API call to use in the right hand side column.  Armed with this information, it is then a simply task of checking the O4W Reference Guide for more detailed information about using the O4W API call.

As Bryan says, “It’s likely that at some time you’ve found yourself working in O4W, and wondered how to accomplish a specific task (like changing the borders on a table, or generating pre-formatted text).  You probably turned to Google (or your favorite other search engine) (but most likely Google) and found the answer in a few seconds – but the answer told you what HTML you need to use to generate your desired results.  How do you translate that HTML back into O4W API calls?”.  It is this cheat sheet that directly addresses this need.


Leave a Reply

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

You are commenting using your 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