mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-28 03:15:33 +02:00
Code Issues Wiki Activity
cdt/qt/org.eclipse.cdt.qt.core/META-INF/MANIFEST.MF

22 lines
892 B
Text
Raw Normal View History

Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Fix Qt plugin's project structure The Qt plugins have been naming internal packages using two different prefixes: cdt.qt.internal cdt.internal.qt This renames all packages to cdt.internal.qt, which seems to be the convention for other projects. I've increased the Qt plugin versions because alot of new API has been added, especially to the qt.core plugin. I increased the version in the MANIFEST.MF and pom.xml files. I've also fixed the MANIFEST.MF files to take CDT out of the plugin names. I've also replaced a call to CCorePlugin.log(Exception) with a call to QtUIPlugin.log (and added the logging functions to QtUIPlugin. Change-Id: I1e3e7b2a42c2eb79fe33608c14a1abcf013a9f2c Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19698 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-12-12 07:40:51 -05:00
Bundle-Name: %pluginName
Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
Bundle-SymbolicName: org.eclipse.cdt.qt.core;singleton:=true
Fix Qt plugin's project structure The Qt plugins have been naming internal packages using two different prefixes: cdt.qt.internal cdt.internal.qt This renames all packages to cdt.internal.qt, which seems to be the convention for other projects. I've increased the Qt plugin versions because alot of new API has been added, especially to the qt.core plugin. I increased the version in the MANIFEST.MF and pom.xml files. I've also fixed the MANIFEST.MF files to take CDT out of the plugin names. I've also replaced a call to CCorePlugin.log(Exception) with a call to QtUIPlugin.log (and added the logging functions to QtUIPlugin. Change-Id: I1e3e7b2a42c2eb79fe33608c14a1abcf013a9f2c Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19698 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-12-12 07:40:51 -05:00
Bundle-Version: 1.1.0.qualifier
qt slot/signal auto-complete Tags signal and slot methods when the index is created. Uses these tags to suggest values inside of SIGNAL and SLOT macro expansions. Enabled only for projects with the QtNature. Recognizes QObject::connect function calls and suggests SIGNAL(a) and SLOT(a) for the 2nd and 4th parameters. When expanding the SIGNAL and SLOT macros within a call to QObject::connect, suggests signals and slots based on the type of the previous parameter. E.g. in QObjectA a; QObjectB b; QObject::connect( &a, SIGNAL(*), &b, SLOT(**) ); The content assistant will suggest the methods of type QObjectA that have been marked as signals at *, and the methods of QObjectB that have been marked as slots at **. Change-Id: Ia6aaa71724547b0977e322399a500f072004767a Reviewed-on: https://git.eclipse.org/r/10532 Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com> Tested-by: Doug Schaefer <dschaefer@qnx.com>
2013-02-20 13:23:40 -05:00
Bundle-Activator: org.eclipse.cdt.qt.core.QtPlugin
Fix Qt plugin's project structure The Qt plugins have been naming internal packages using two different prefixes: cdt.qt.internal cdt.internal.qt This renames all packages to cdt.internal.qt, which seems to be the convention for other projects. I've increased the Qt plugin versions because alot of new API has been added, especially to the qt.core plugin. I increased the version in the MANIFEST.MF and pom.xml files. I've also fixed the MANIFEST.MF files to take CDT out of the plugin names. I've also replaced a call to CCorePlugin.log(Exception) with a call to QtUIPlugin.log (and added the logging functions to QtUIPlugin. Change-Id: I1e3e7b2a42c2eb79fe33608c14a1abcf013a9f2c Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19698 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-12-12 07:40:51 -05:00
Bundle-Vendor: %providerName
Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
Require-Bundle: org.eclipse.core.runtime,
Fix overly strict dependency in qt.core.
2013-02-19 10:50:58 -05:00
org.eclipse.core.resources,
Bug 422797 - API for retrieving QMake information from Qt project API is located at org.eclipse.cdt.qt.core.index package. Entry point is QMakeProjectInfoFactory.getForActiveConfigurationIn method that provides ability to retrieve QMake information (IQMakeInfo interface) for active project configuration of a specified project. Also allows to listen on changes of such information. qmakeEnvProvider extensions allows CDT build-system to provide environment for QMake runs within their build-system. Information is gather by parsing output of: 1) qmake -query 2) qmake -E file.pro // only for QMake version 3.0 Change-Id: Iae569bdbc89dc26d60530596b66b5227f36dfae6 Signed-off-by: David Kaspar <dkaspar@blackberry.com> Reviewed-on: https://git.eclipse.org/r/19082 Reviewed-by: Andrew Eidsness <eclipse@jfront.com> Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-11-28 19:58:37 +01:00
org.eclipse.core.expressions;bundle-version="[3.2.0,4.0.0)",
Bug 424824: Codan checker for Qt This implements a Codan checker for QObject::connect and disconnect function calls. There are several overloads for each function, but the basic call looks like: Q * q; QObject::connect( q, SIGNAL( sign() ), q, SLOT( slot() ) ); This function calls requires that Q have a Qt signal called sign and a Qt slot called slot, e.g., class Q : public QObject { Q_OBJECT Q_SIGNAL void sign(); Q_SLOT void slot(); }; The Qt checker raises a warning if either condition is not true. It also raises a warning for SIGNAL or SLOT expansions without a parameter. Change-Id: If68a5bcdabb3f118801675e46ae926e6a250378a Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/20231 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2014-01-02 17:06:05 -05:00
org.eclipse.cdt.core,
org.eclipse.cdt.codan.core,
org.eclipse.cdt.codan.core.cxx
Added support for Qt. Extended AddFiles template to change start/end patterns.
2013-01-12 00:54:08 -05:00
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-ActivationPolicy: lazy
Added content types for .pro and .qml files for Qt.
2013-01-12 16:10:21 -05:00
Bundle-Localization: plugin
Bug 425102 QObject::connect content assist broken The QObject::connect content assistant does not work when the receiver of the function call is an implicit this. E.g., class Q : public QObject { Q_OBJECT f() { this->connect( ... ); // works connect( ... ); // does not work QObject::connect( ... ) // does not work } }; I've changed the Qt's ASTUtil.getReceiverType to navigate to the ICPPClassType through the IScope's. The previous implementation was relying on the connect function call being an IASTField I've also added a test case for this problem. Change-Id: I96c29a9a452280068bda39a63414c50008bfad37 Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/20399 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2014-01-08 12:57:25 -05:00
Export-Package: org.eclipse.cdt.internal.qt.core;x-friends:="org.eclipse.cdt.qt.ui,org.eclipse.cdt.qt.tests",
Content assistant for Qt elements This adds content assistants for QObject::connect function calls and Q_PROPERTY expansions. QObject::connect function calls look like: QObject::connect( sender, SIGNAL(someSignalFunction(int), receiver, SLOT(someSlotFunction(int)); The assistant provides proposals in the SIGNAL and SLOT expansions. The QObject for the corresponding type is used to create a list of signal or slot function signatures. Q_PROPERTY expansions look like: Q_PROPERTY( type name READ someFunction ... ) [The ... is a list of optional attributes.] The assistant proposes attribute names that have not yet been added. It also proposals appropriate values for the attribute. This patch also adds test cases for this feature. Change-Id: I0eb25235bb423c1cfcd743075331f90f269afea7 Signed-off-by: Andrew Eidsness <eclipse@jfront.com> Reviewed-on: https://git.eclipse.org/r/19721 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com> IP-Clean: Doug Schaefer <dschaefer@qnx.com>
2013-12-12 08:07:59 -05:00
org.eclipse.cdt.internal.qt.core.index;x-friends:="org.eclipse.cdt.qt.tests",
org.eclipse.cdt.internal.qt.core.parser;x-friends:="org.eclipse.cdt.qt.ui",
org.eclipse.cdt.qt.core,
org.eclipse.cdt.qt.core.index
Reference in a new issue Copy permalink