diff options
author | Eike Ziller <eike.ziller@qt.io> | 2018-09-28 13:42:01 +0200 |
---|---|---|
committer | Eike Ziller <eike.ziller@qt.io> | 2018-10-04 07:58:31 +0000 |
commit | 9ecb100128ee8729c4ad50e2ae5981c10ba6c286 (patch) | |
tree | 789f8409887999e6f38fe1cdad27ec610e85033c /optional/texteditor/typesystem_texteditor.xml | |
parent | 3412dc563119221bd730c1487937519df0761792 (diff) |
Include Qt Creator typesystem instead of duplicating API4.8
This seems to work now after beautifying the import hierarchy.
Change-Id: I24daf09ff63ef91023366c12308d2f9fcd2676aa
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Diffstat (limited to 'optional/texteditor/typesystem_texteditor.xml')
-rw-r--r-- | optional/texteditor/typesystem_texteditor.xml | 22 |
1 files changed, 1 insertions, 21 deletions
diff --git a/optional/texteditor/typesystem_texteditor.xml b/optional/texteditor/typesystem_texteditor.xml index ef10df0..f421b76 100644 --- a/optional/texteditor/typesystem_texteditor.xml +++ b/optional/texteditor/typesystem_texteditor.xml @@ -42,28 +42,8 @@ <!-- Typesystem for Qt Creator Python host plugin --> <typesystem package="QtCreatorBindingTextEditor"> - - <!-- Load PySide QtWidgets typesystem (is this correct? yup) --> <load-typesystem name="typesystem_widgets.xml" generate="no"/> - <!-- Currently there are problems with getting this to work (see below) --> - <!-- <load-typesystem name="../../plugins/pythonextensions/typesystem_qtcreator.xml" generate="no"/> --> - <!-- - Here is the deal: This will compile just fine, but WON'T LOAD. - The reason for this is known: - -> The generated binding initializer will try to load the Python Module 'QtCreatorPython' - -> This module does not exists, because we expose everything as members of 'PythonExtension' - -> Now one might try to simply rename QtCreatorPython to PythonExtension.QtCreator, which would - generate an import statement like `Shiboken::Module::import("PythonExtension.QtCreator")` - -> Problem: That does not work either, because QtCreator is actually a member in PythonExtension, - which is a module and not a package. - -> So yeah, essentially it seems like this is something that would not be a problem in a module - for CPython, but there seems to be no facility to circumvent this when embedding CPython. - There is also no way in Shibken to fix this and no easy fix for that. - ==> The easiest way forward is to just include the parts that are needed within each binding in - the typesystem. Problems that might arise: - 1) Big size of bindings due to repetition of code (pretty sure) - 2) Interoperability issues between bindings (conjecture) - --> + <load-typesystem name="../../plugins/pythonextensions/typesystem_qtcreator.xml" generate="no"/> <namespace-type name="TextEditor"> <enum-type name="TextPositionOperation"/> |