m (typo) |
(→Notes / discussion) |
||
| Line 41: | Line 41: | ||
* Few more comments on task breakdown, to see if there is something important/big item missing here: | * Few more comments on task breakdown, to see if there is something important/big item missing here: | ||
** What about integration of tools like PowerTOP, Oprofile, Valgrind? including integration into OBS as RPMs and with Qt Creator as plugins | ** What about integration of tools like PowerTOP, Oprofile, Valgrind? including integration into OBS as RPMs and with Qt Creator as plugins | ||
| - | ** What about integration with WRT SDK? WRT not in the scope of 1.1? | + | ** What about integration with Qt WRT SDK? Qt WRT not in the scope of 1.1? |
| - | ** Is the UI/ | + | *** Fathi: Qt WRT is available for MeeGo 1.1. It's a bit late for integration into 1.1. I'm in favor of postponing to 1.2. |
| + | ** Is the UI/Qt Designer considered by Qt Creator efforts, AFAIK, it is also standalone tool and important to developers? Is it good enough to support all Toolkits/APIs? | ||
| + | *** Fathi: definitely, yes. Qt Creator team planned to improve this area. What do you mean by "all" Toolkits/APIs? | ||
** Device simulation (skin, platform specific devices) already covered by QEMU? Should we separate the efforts on QEMU to bootup and run MeeGo images with good performance from the efforts on simulating devices specific to platforms for multiple OSs(Win,Linux, Mac). Both are big task task items. | ** Device simulation (skin, platform specific devices) already covered by QEMU? Should we separate the efforts on QEMU to bootup and run MeeGo images with good performance from the efforts on simulating devices specific to platforms for multiple OSs(Win,Linux, Mac). Both are big task task items. | ||
| + | *** Fathi: true. actually, the same team is handling QEMU related tasks. | ||
Contents |
[development. These guys know the components inside out]:
From Kerry: