Kexi/Plugins/Scripts/Database Object Model: Difference between revisions
(→Notes) |
(→Notes) |
||
| Line 35: | Line 35: | ||
==Notes== | ==Notes== | ||
*'''Scripting makes sense mostly in Qt5-based Kexi.''' Target implementation shall use Qt5's QtScript since it uses the more efficient V8 engine which [https://bugreports.qt-project.org/browse/QTBUG-12503?focusedCommentId=159445&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-159445 will not been used in Qt4]. Qt4's QtScript uses JavaScriptCore. It is too costly to standardize on Qt4 scripting and then porting to Qt5 (with changed API). | |||
*When designing the object model, try to harmonize with Predicate's API | *When designing the object model, try to harmonize with Predicate's API | ||
*Use JavaScript notation as QtScript will be used to implement scripting | *Use JavaScript notation as QtScript will be used to implement scripting | ||
Revision as of 22:28, 1 November 2012
Note
This page is a draft for database object model in Kexi
Class
Description....
MSA equivalent's name:
Properties:
| Name | Type | Description | Read/Write? | MSA name |
|---|---|---|---|---|
Methods:
| Name | Type | Description | MSA name |
|---|---|---|---|
Notes
- Scripting makes sense mostly in Qt5-based Kexi. Target implementation shall use Qt5's QtScript since it uses the more efficient V8 engine which will not been used in Qt4. Qt4's QtScript uses JavaScriptCore. It is too costly to standardize on Qt4 scripting and then porting to Qt5 (with changed API).
- When designing the object model, try to harmonize with Predicate's API
- Use JavaScript notation as QtScript will be used to implement scripting
- Information about MSA equivalent names would be reusable in Kexi Handbook too, chapter "Comparison to MS Access"