The biggest change comes from the fact that Firefox no longer supports the overflow style on tbody sections in tables. To maintain scrolling tables we have had to take a completely different (and to some extent traditional) approach which involves using Javascript to break a table into three tables and three divs to get the scrolling table effect.

Central to this approach was also the adoption of the jQuery Javascript library.

The other change is that Firefox no longer supports XUL in the same way.

Because of the changes to the layout of an application source the version of Unibase has been bumped to 19.

Changes to application layout:

1. In the htm directory create subdirectories “js” and “css”.
2. From /usr/local/lib, symbolically link “unibase.css” and “reset.css” to the “css” subdirectory.
3. 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.

“The client needed a more powerful machine and while we looked at various options, IBM emerged over its competitors as the leading solution,” said Zenucom managing director, Rick Marshall.

“It got the job done quickly and was significantly faster than any of the other options.”

read the full article at FERRET – Australia’s Manufactoring and Investment Directory

Rick Marshall - Zenucom's Managing Director

]]> http://unibase.zenucom.com/wordpress/?feed=rss2&p=370 0 http://unibase.zenucom.com/wordpress/?p=227 http://unibase.zenucom.com/wordpress/?p=227#comments Mon, 11 May 2009 04:03:35 +0000 admin http://unibase.zenucom.com/wordpress/?p=227 http://unibase.zenucom.com/wordpress/?feed=rss2&p=227 0 http://unibase.zenucom.com/wordpress/?p=225 http://unibase.zenucom.com/wordpress/?p=225#comments Mon, 11 May 2009 04:02:44 +0000 admin http://unibase.zenucom.com/wordpress/?p=225 http://unibase.zenucom.com/wordpress/?feed=rss2&p=225 0 http://unibase.zenucom.com/wordpress/?p=223 http://unibase.zenucom.com/wordpress/?p=223#comments Mon, 11 May 2009 04:01:40 +0000 admin http://unibase.zenucom.com/wordpress/?p=223 http://unibase.zenucom.com/wordpress/?feed=rss2&p=223 0 http://unibase.zenucom.com/wordpress/?p=215 http://unibase.zenucom.com/wordpress/?p=215#comments Sun, 10 May 2009 01:39:32 +0000 admin http://unibase.zenucom.com/wordpress/?p=215

ubxmldict – make a data dictionary from xml definitions

SYNOPSIS

ubxmldict

DESCRIPTION

FLAGS

ERRORS

EXAMPLE

SEE ALSO

NAME

transaction – transaction processor records in XML format

DESCRIPTION

ubtransaction reads XML format records and processes them to do a range of updates and processes on the database.

The different commands are:

• ADD
• DATA
• DELETE
• EXECUTE
• PASSWORD
• UPDATE
• TRANSACTION

ubtransaction uses two security models. At this time these are not high security but adequate for most installations.

Method 1. Local sessions will be processed if the environment variable “REMOTE_USER” is set. This is done automatically for web based access from ubprompt for data table updates etc.

Method 2. Remote sessions must include the element “password” (see below). If the user name password pair (from the Linux passwd database) do not match the transaction will not be processed.

All transactions are logged in /var/log/ubtransaction/ubtp.log and the details in matching log files – /var/log/ubtransaction/ubtp.<transaction>.

If sendmail is running on the server, /usr/bin/ubtransaction.smrsh is linked to /etc/smrsh/ubtransaction allowing remote transactions to be delivered to ubtransaction@<server>. An entry is also put into /etc/aliases. To disable this feature, remove both the alias entry and the link in /etc/smrsh. For postfix, only the /etc/aliases entry is required.

ADD

Add records to a table. Currently only the “attribute,value” format is supported.

<add table=”…”>

DATA

Return records from the database using a specfied format.

<data table=”…”>

DELETE

Delete records from a table.

NOTE: The matching index value is optional and if omitted, the entire table contents will be deleted.

<delete table=”…”>

EXECUTE

Execute a system command.

NOTE: ubreport is a command interpreter, as are many other UNIBASE commands. However only ubreport in non-interactive mode is sensible. Other interpreters such as perl and tcl are also suitable. The default is sh (bash).

<execute>

TRANSACTION

Wrapper for a transaction set.

This is the wrapper for this transaction set.

<transaction application=”…” {directory=”…”}>

UPDATE

Update attribute values in a record

<update table=”…”>

EXAMPLES

SEE ALSO