- Nov 01, 2010
-
-
Alessandro Portale authored
Reviewed-By: TrustMe
-
Alessandro Portale authored
...and do not call it show(), because that is the signature of a non-virtual base class function. showExpanded() sucks as name, and hjk, who reviewed this is not convinced. But showExpanded() is still better than show(). Task-Number: QTCREATORBUG-2979 Reviewed-By: hjk
-
Alessandro Portale authored
- Renaming the screen orientation enum and keys - Explicit constructors - Virtual destructors - Renamed some occurences of 'Qml' in comments to 'QML' - Adding descriptive comments to all generated files which should not be touched by the user. - Adding missing license headers to the qmljsdebugger sources Task-Number: QTCREATORBUG-2885 Reviewed-by: Friedemann Kleint Reviewed-by: dt
-
- Oct 13, 2010
-
-
Kai Koehne authored
Don't confuse users by two defines they have to comment in when they just want to 'debug': Instead QMLJSDEBUGGER now activates both the Js Debugger & and the QmlObserver services. Finetuning can still be done by using the (undocumented) NO_JSDEBUGGER, NO_QMLOBSERVER defines.
-
- Sep 22, 2010
-
-
Kai Koehne authored
This allows us to enable/disable the experimental observer, independent from the core javascript-debugger functionality. Reviewed-by: Christiaan Janssen
-
Kai Koehne authored
The library not only contains the observer part, but also the javascript debugger. Reflect this in the namespace.
-
- Sep 21, 2010
-
-
Christian Kandeler authored
The GUI part of this has been removed already. Reviewed-by: Alessandro Portale
-
- Sep 20, 2010
-
-
hjk authored
-
- Sep 16, 2010
-
-
Kai Koehne authored
We should restrict ourselves to calling all qml debugging support observer, instead of mixing qml debugger / inspector / observer interchangeably.
-
Kai Koehne authored
-
Kai Koehne authored
-
- Sep 15, 2010
-
-
Kai Koehne authored
Don't force users to inherit from QDeclarativeDesignView. Instead we're using now event filters to let a user attach a QDeclarativeViewObserver object to a QDeclarativeDesignView.
-
- Sep 10, 2010
-
-
Christian Kandeler authored
Reviewed-by: Alessandro Portale
-
- Sep 08, 2010
-
-
Christian Kandeler authored
Reviewed-by: dt
-
- Aug 25, 2010
-
-
Alessandro Portale authored
- Removed the "cpp/" dir - Moved main.cpp and symbianicon.svg next to the main .pro. This also reduces the dir depth in the project view. - Introduced "qmlapplicationviewer/" dir, which will contain the files which the user should not modify. All the files there have the base name "qmlapplicationviewer" - Moved/renamed "qmlapplication.pri" to "qmlapplicationviewer/qmlapplicationviewer.pri"
-
- Aug 16, 2010
-
-
Alessandro Portale authored
-
Alessandro Portale authored
-
Alessandro Portale authored
setSource() needs to be called *after* addImportPath.
-
- Aug 15, 2010
-
-
Alessandro Portale authored
Application logic implemented. The Wizard Ui does not expose this feature, yet.
-
- Aug 09, 2010
-
-
Alessandro Portale authored
-
- Aug 06, 2010
-
-
Lasse Holmstedt authored
Reviewed-by: Alessandro Portale
-
- Aug 03, 2010
-
-
Alessandro Portale authored
Makes development easier (no recompiling needed when tweaking the templates). Also, all other templates are in that folder.
-
- Aug 02, 2010
-
-
Alessandro Portale authored
Switchen from QMAKE_BUNDLE_DATA to QMAKE_EXTRA_TARGETS, like we already do on Windows and Linux. QMAKE_BUNDLE_DATA does not seem to create make targets. We need to copy-if-changed the files into the resources folder on each run. Also pushed the Resources/ folder one level deeper, into Contents/.
-
Alessandro Portale authored
-
- Jul 30, 2010
-
-
Alessandro Portale authored
And also prevent a 0-size if the Qml document does not specify width/height.
-
Alessandro Portale authored
Using the QMAKE_BUNDLE_DATA variable to copy the data into the Resource directory in the application bundle.
-
- Jul 16, 2010
-
-
Alessandro Portale authored
Short: Create a new self running qml .sis/.deb package. Long: A typical Qml application usually consists of a couple of .qml, .js and image files. Deploying such an application is challenging, especially to mobile devices. This wizard will generate a C++ project with a customized, light weight Declarative Viewer, a helloworld Qml file and a .pro file that takes care of the deployment of the Qml file(s). This is just the first step. There will be an import wizard, and further more there will be the possibility to add additional Qml modules and probably also Qml directories to the package. Task-number: QTCREATORBUG-1813
-