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

Latest revision as of 20:12, 26 August 2023

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 KDb's API
Use Python API/coding standards and notation as Python is the scripting choice
Information about MSA equivalent names would be reusable in Kexi Handbook too, in chapter "Comparison to MS Access"

Links

Office 2013 VBA Documentation (chm file, accessible using kchmviewer)
VBA Language Specification (new, PDF)
MS ADO Object Model
http://en.wikipedia.org/wiki/ActiveX_Data_Objects
http://www.access2base.com - well documented object model in LO following MSA, now it integrates Python too

@@ Line 35: / Line 35: @@
 ==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 KDb's API
-*When designing the object model, try to harmonize with Predicate's API
+*Use Python API/coding standards and notation as Python is the scripting choice
-*Use JavaScript notation as QtScript will be used to implement scripting
+*Information about MSA equivalent names would be reusable in Kexi Handbook too, in chapter "Comparison to MS Access"
-*Information about MSA equivalent names would be reusable in Kexi Handbook too, chapter "Comparison to MS Access"
 ==Links==
+*[http://www.microsoft.com/en-us/download/details.aspx?id=40326 Office 2013 VBA Documentation] (chm file, accessible using kchmviewer)
+*[https://msdn.microsoft.com/en-us/library/dd361851 VBA Language Specification] (new, PDF)
+*[http://msdn.microsoft.com/en-us/library/windows/desktop/ms675944%28v=vs.85%29.aspx MS ADO Object Model]
 *http://en.wikipedia.org/wiki/ActiveX_Data_Objects
+*http://www.access2base.com - well documented object model in LO following MSA, now it  integrates Python too