Rapid Database Application Development
"Microsoft Access for Linux"
Current Tasks for mart
Memory leak on unloading driver? due to API change.^ toc
It is designed to be fully usable with and without KDE desktop on Linux/Unix and MS Windows platforms.^ toc
Response: "Why not use QtSQL internally?"^ toc
KFD allows choice of widget sets. That means:
Refer to 5.1:
If you really want, QtSQL drivers can be wrapped to be KexiDB compatible.
However, wrapping QtSQL for executing SQL statements means:
<jstaniek> mart: one main reason is that "let's compare against Qt3 not Qt4" ... or if, say, our needs require Qt5, should we wait to 2008?
Where are the Qt functions to:
By maintaining API-level references to connections, KexiDB can support advanced features of databases. Although it's not appropriate to bloat KexiDB with many features, it is possible to develop plugins for a given database that use specific features of particular backends.^ toc
IMPORTANT: Currently, trunk has the version of Kexi 0.8, the one that is released within KOffice 1.4, and therefore is in feature freeze. See the next section (Bleeding edge) for information on how to build the very latest version.^ toc
Currently the development branch of Kexi is not in trunk. If you have already checked out a copy of Kexi as above, the following will update your checkout to the 0.9 branch, due to be released independently of KOffice.
cd kexi svn switch svn://anonsvn.kde.org/home/kde/branches/kexi/0.9/koffice/kexi
If you don't already have a Kexi checkout, and want to go straight to the development version, use:
svn co -N svn://anonsvn.kde.org/home/kde/trunk/koffice/ cd koffice svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kde-common/admin svn co svn://anonsvn.kde.org/home/kde/branches/kexi/0.9/koffice/kexi
Please consult the AdvancedBuildNotes for information on how to build hidden features that are under development.