|
Overview : Announcement Mailing List : Aethera Plugins : BlackAdder : dbRadar
Data Architect : Kapital : Kivio mp : KOBOL : KODE : PyQtDoc : Quanta Gold : Rekall
tkCard : tkBackup : tkExpense : tkPhone : tkShopper : Eric Ultimate Solitaire
Licensing Information : Download basket
Location / Home / Products / Rekall  Rekall 2.0.2
Rekall 2.0.2 is a bug-fix release. We recommend that you update to it. Bugs fixed:
- Fixed problem inserting new records into XBase/XBSQL
- Dynamic link fields fixed
- Temporary hack to do case-insensitive "like" in PostgreSQL (will be fixed properly in 2.0.3)
- KDE/QT3-only runtime packaging problem fixed
Changes from 2.0.0 to 2.0.1
Added RichText and Memo controls to reports
Added image resizing for Pixmap and Graphic controls
Fixed print-to-file under KDE
Various navigation fixes for saving fron tool bar
Added "deformat" option for use when saving Field controls
First release of IBM DB2 driver for Linux
Rekall 2.0.0
Rekall 2.0.0 is a major upgrade to Rekall, out database front end.
The biggest addition to Rekall 2.0.0 is reusable components. Rekall now
comes with a selection of components that you can use in forms; these
include standard buttons and navigation tools.
As well at these components, you can also construct your own for use as
often as you want. You can store your components either in the database
itself, or in a local area in the file system.
To support reusable components, and to make it easier to script complicated
forms, Rekall 2.0.0 introduces an Event/Slot mechanism (akin to QT's
Signal/Slot mechanism). This allows to place all script code which is
logically associated with a particular control inside that control, and
means you can copy or delete the control without worrying about copying or
cleaning up script code inside other controls.
Other new features in Rekall 2.0.0 include:
- Static images can by displayed in forms
- Data controls can appear in menu-blocks
- Spin box control
- Link controls can display multiple colums
- Link controls can use Queries as well as tables
- Event logger for debugging
- Raw SQL window for direct SQL execution
- Forms, Reports, etc. can run modally
- Fast table filters for predefined table data display
- Modal forms can be used as dialog boxes
- Explanation of queries generated by Rekall
- Menu and toolbar hiding
- MySQL and PostgreSQL connections over SSH tunnels (Linux only)
Visit the Rekall website, currently at the URL below, for up-to-date
information on rekall. Follow the "Content" link for tips, tricks and
other useful information, or follow "Screenshots" to see what Rekall
has to offer!
http://www.rekall.a-i-s.co.uk/
Rekall 1.0.3 Release Notes
Please note that the default database file extenstion has been changed
from .kdb to .rkl, although the file formats are the same and the
extensions are interchangable. If you do wish to rename the database file to use the .rkl extension then any form, report, query or copied files in the database directory must be similarly renamed (eg., myform.kdb.frm should be renamed to mkform.rkl.frm), otherwise they will not be visible from inside Rekall.
Rekall 1.0.3 is almost exclusively a bug fix release.
Rekall 1.0.3 Changes
- Fix for saving forms, reports, etc., into the database for MySQL and
PostgreSQL
- Fix for crash when combining nested blocks in forms with scroll bars.
- Fix for table update using XBase/XBSQL with unique indexes
- A PDF version of the documentation is available from http://www.seriesone.net/Rekall.
Rekall 1.0.2 Changes
The following list summarises the changes since 1.0.1 (including
changes from xbsql-0.7 to xbsql-0.8):
- Much faster display of tables with large numbers of columns.
- Much faster display of MySQL tables with large numbers of rows.
- Selection (and deletion) of multiple rows in table data and form
data view.
- Automatic for Python 1.5.2, 2.0 or 2.1 as installed.
- Online help (in progress, more to come).
- Added Enter/Return as equivalent to Tab key.
- Support for eight-bit character sets.
- Added "group by" and column aliasing to query designer.
- Support for insert/update/delete where table does not have a
primary key.
- Various other bug fixes.
- Indexing fixed for XBase/XBSQL.
- Added "group by", "having" and aggregate functions to XBSQL (note,
this is under development, please verify correct operation).
Rekall 1.0.1 Changes
The following list summarises the changes since 1.0:
- In table design, control returns to first row after the
table definition is saved.
- Fixed "sort ascending" spelling.
- Support for boolean types added to drivers and to check
box control. Note that XBase/XBSQL still has problems.
- Better keyboard navigation. Ctrl-Up and Ctrl-Down go to first/last record, and Ctrl-Left and Ctrl-Right to first/last control. Home and End operate within text controls.
- Indexing in table design believed to work now.
- More documentation including basic descriptions of control types.
- Default values now work, and can be set to script
expressions.
- Tab order dialog behaves more sensibly if controls are
not named.
- Entry to query design mode no longer immediately marks the
query as changed.
Rekall 1.0 Changes
Compared to Rekall 0.7, release 1.0 mostly contains bug fixes.
The main additions are:
- Copiers can be invoked from scripts.
- Scripts can dynamically build and execute forms and reports (this is
very basic; release 1.1 will improve support for this).
- The PostgreSQL driver handles "serial" columns correctly.
Rekall Components and the Demo Database
1. RPM installation
If you are installing Rekall to run under KDE2, there are four
RPMs to install:
|
korelib-0.8
|
library loader package
|
|
xbase-2-0.0
|
XBase routines
|
|
xbsql-0.8
|
SQL wrapper for XBase routines
|
|
rekall-1.0.2
|
Rekall itself
|
Pick the set appropriate to your distribution. These are build
against the packages as supplied with the distributions, and use
the version of QT2 supplied with the installation.
2. QT-Only installation
The QT-only version should run on any Linux i386 X-windows
system.
Unpack the rekallqt tarball, then cd into the 'rekallqt-1.0.2'
directory and execute the command "./install". This will install
rekallQT into the directory /usr/local/rekallqt, with an entry
"rekallqt" in /usr/bin. Rekall can then be exucuted using the
command "rekallqt".
If you need to, you can change the install script to install into
any direcory, however you will need to edit the "rekallqt" script
in the installation directory to match.
RekallQT includes its own copy of QT3 (3.0.1), plus the Korelib,
XBSQL and XBase components.
3. Demo Database
The tarball RekallDemo.tgz contains a demonstration database.
There are actually three copies of the database, one using MySQL,
one PostgreSQL and one XBase/XBSQL.
In the case of MySQL and PostgreSQL, it assumes a server database
called "RekallDemo", with access for a user "orders" and password
"bigboss", in both cases with the server running on localhost.
For the XBase/XBSQL version, it assumes that the tarball has been
unpacked into /home/mike as /home/mike/RekallDemo.
To set this up on another machine, the easiest thing to do is to
unpack the tarball, and then to hand edit the file Orders.kdb as
appropriate. The files "Orders.mysql.dmp" and "Orders.psql.dmp
contain scripts to reconstruct the MySQL and PostgreSQL databases:
mysql -uorders -pbigboss RekallDemo < Orders.mysql.dmp
PGUSER=orders PGPASSWORD=bigboss psql RekallDemo < Orders.psql.dmp
The MySQL version can be accessed both via the forms, etc., stored
in the directory into which the tarball extracts (accessed by
expanding "!Files" in the database window) or via those stored in
the MySQL database itself (accessed by expanding "Orders"). In the
case of the PostgreSQL and XBase/XBSQL versions, the forms, etc.,
are stored in the respective databases.
Building Rekall from Source
If you have the source tarball, Rekall can be build as follows:
- You will need korelib-0.8 installed; if you have a working Rekall
installed then korelib-0.8 must be there
- To build with XBase/XBSQL support, you will need to install the
xbase-2.0.0, xbase-devel-2.0.0 and xbsql-0.8 packages
- To build with MySQL support, you will need MySQL and its development
packages installed
- To build with PostgreSQL support, you will need PostgreSQL and its
development packages installed
- Unpack the tarball and enter the rekall directory
- Configure with the command:
./configure --with-kore-loader --with-kde-gui \
--with-qt-dir=/path/to/qt \
--prefix=/my/prefix
where /path/to/qt and /my/prefix are set appropriately. You might
also want "--enable-debug" if you want to fix bugs for us!
- make
- make install
Enjoy!
|
