Unibase has undergone a significant update to ensure compatibility with the latest web browsers, including Chrome, Safari, Firefox, and Internet Explorer.
This upgrade introduces substantial changes, primarily driven by Firefox’s discontinuation of overflow styling on tbody elements. To address this, Unibase has adopted a novel approach for implementing scrolling tables, leveraging JavaScript and the jQuery library to restructure tables using divs. Furthermore, the update reflects the reduced support for XUL in Firefox. Consequently, these layout modifications necessitate a version bump to Unibase 19, accompanied by specific adjustments to the application’s directory structure and initialization process.
Changes to application layout:
- In the htm directory create subdirectories “js” and “css”.
- From /usr/local/lib, symbolically link “unibase.css” and “reset.css” to the “css” subdirectory.
- From /usr/local/lib, symbolically link “unibase.js” and “ub_input.js” to the “js” subdirectory.
Add to the application “inc” directory:
- ln -s /usr/local/lib/bodyInit
- ln -s /usr/local/lib/body
- ln -s /usr/local/lib/init
Initialisation:
In unibase-18.00 the typical way to start a web page is with ”. This has been replaced with the more correct jQuery technique. bodyInit has a body element, the reference to jquery.js (must be in body of document, not head), and the code to call ubinit. body is just the body element and jquery.js, while init is a stub you can include if there is other initialisation to be done once the document has loaded.
Scrolling tables, iframes, and divs should use these classes to get correct inline flow:
- div: class=”scrollable inline-block”
- iframe: class=”scrollable inline”
- table: class=”scrollable inline-table”
xul:
xul is no longer supported for data access and will fail. The only recommendation is to rewrite the reports as standard html. Now a much easier task.
