Kexi/Plugins/Scripts/Database Object Model: Difference between revisions

From KDE Community Wiki
< Kexi‎ | Plugins‎ | Scripts
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 a fork JavaScriptCore and exposes internal APIs of JavaScriptCore. In Qt5 QtScript is a DONE module without (as of 2012) plans for porting to V8. It is too costly to standardize on Qt4 scripting and then porting to Qt5 (with changed API). See also [http://thread.gmane.org/gmane.comp.kde.devel.kwrite/32993/focus=75070 Summary of QtScript problems in Qt5]
*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 23:19, 25 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

  • 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"

Links

Retrieved from "https://community.kde.org/index.php?title=Kexi/Plugins/Scripts/Database_Object_Model&oldid=26793"