Kexi/Compatibility: Difference between revisions
< Kexi
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
== Compatibility with KEXI 2 == | == Compatibility with KEXI 2 == | ||
Status for KEXI 3.0 and 3.1. KEXI offers the same list of features as KEXI 2 and uses the same format for <tt>.kexi</tt> files and server projects. | Status for KEXI 3.0 and 3.1. KEXI offers the same list of features as KEXI 2 and uses the same format for <tt>.kexi</tt> files and server projects (MySQL, PostgreSQL). | ||
Exceptions (status for 3.1): | Exceptions (status for 3.1): | ||
* no scripting (in KEXI 2 it was present as experimental), we plan to deliver brand new JavaScript support (without web browser overhead) | * no scripting (in KEXI 2 it was present as experimental), we plan to deliver brand new JavaScript support (without web browser overhead) | ||
| Line 9: | Line 9: | ||
Further KEXI version would, of course, get new features not present in KEXI 2. | Further KEXI version would, of course, get new features not present in KEXI 2. | ||
Like most older KEXI version, KEXI 3 has no official support for server projects other than MySQL and PostgreSQL. | |||
Revision as of 14:33, 10 March 2018
Compatibility of KEXI 3
Compatibility with KEXI 2
Status for KEXI 3.0 and 3.1. KEXI offers the same list of features as KEXI 2 and uses the same format for .kexi files and server projects (MySQL, PostgreSQL). Exceptions (status for 3.1):
- no scripting (in KEXI 2 it was present as experimental), we plan to deliver brand new JavaScript support (without web browser overhead)
- "map" report elements: not supported until KEXI 3.1
- "map" form widgets: not supported
Further KEXI version would, of course, get new features not present in KEXI 2.
Like most older KEXI version, KEXI 3 has no official support for server projects other than MySQL and PostgreSQL.