Qt-contributors-summit-2013-Qt-Creator-3.0: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Qt Creator session | |||
Android, iOS<br /><span class="caps">API</span> Stabilities | |||
* Reduce number of symbols | |||
* Go over the <span class="caps">API</span>’s, review<br /> HiDPI | |||
Sharing with other projects | |||
* put <span class="caps">QML</span>/jS parser to extra repo? | |||
* Announce changes in e.g. <span class="caps">QML</span> debugging <span class="caps">API</span> | |||
* Welcome page extension? | |||
What about <span class="caps">CLANG</span>? | |||
* KDevelop is looking into it, too. | |||
* CLang by default in 3.0 | |||
* Using Clang information could be potentially used by compiler | |||
* Maybe run clang first in a fast way, then in a slower, more accurate way? | |||
Can we share qmake / qbs ? | |||
* qbs is a library | |||
Qt Quick 2 | |||
Welcome Screen – are there hooks? YEs, there are. | |||
CMake integration – can we ###### from kdevelop? | |||
Deployment – integration – what to put into build system? – not problem of Qt Creator | |||
Kits – Blackberry users are confused that they have to have different kits for different devices (even if the rest is the same). However, that’s the whole idea of the kit. |
Revision as of 14:08, 25 February 2015
Qt Creator session
Android, iOS
API Stabilities
- Reduce number of symbols
- Go over the API’s, review
HiDPI
Sharing with other projects
- put QML/jS parser to extra repo?
- Announce changes in e.g. QML debugging API
- Welcome page extension?
What about CLANG?
- KDevelop is looking into it, too.
- CLang by default in 3.0
- Using Clang information could be potentially used by compiler
- Maybe run clang first in a fast way, then in a slower, more accurate way?
Can we share qmake / qbs ?
- qbs is a library
Qt Quick 2
Welcome Screen – are there hooks? YEs, there are.
CMake integration – can we ###### from kdevelop?
Deployment – integration – what to put into build system? – not problem of Qt Creator
Kits – Blackberry users are confused that they have to have different kits for different devices (even if the rest is the same). However, that’s the whole idea of the kit.