(→Interface) |
(→Plasma) |
||
| Line 44: | Line 44: | ||
''And after that, see what can be done for performances:'' | ''And after that, see what can be done for performances:'' | ||
* Engine base classes and command line test utilities. ('''Aaron J. Seigo, aseigo''') | * Engine base classes and command line test utilities. ('''Aaron J. Seigo, aseigo''') | ||
| − | * See if QGV works well for our needs. We will use it until the end of march, then we will see how it worked. We will evaluate alternatives then (if not enough satisfied). ('''Aaron J. Seigo, aseigo''', others welcome! | + | * See if QGV works well for our needs. We will use it until the end of march, then we will see how it worked. We will evaluate alternatives then (if not enough satisfied). ('''Aaron J. Seigo, aseigo''', others welcome!) |
* Create widgets aware of zooming. First we need to discuss what can be done for each of these elements. Needed widgets are: | * Create widgets aware of zooming. First we need to discuss what can be done for each of these elements. Needed widgets are: | ||
| − | ** | + | ** A label (comes with Qt) |
** [[/Button|A button]] | ** [[/Button|A button]] | ||
| − | ** | + | ** An svg viewer (comes with Qt) |
** [[/HTMLViewer|An html widget]] | ** [[/HTMLViewer|An html widget]] | ||
| − | ** | + | ** A lineedit/textedit (comes with Qt) |
Before actually coding them we should first define the speed compromises we want/can have for all of them. We will probably discuss it in the next meeting, and what we want for each of those widgets will be written in their specific pages. Then we can start to actually code it. If you have ideas, please write it in the specific page. | Before actually coding them we should first define the speed compromises we want/can have for all of them. We will probably discuss it in the next meeting, and what we want for each of those widgets will be written in their specific pages. Then we can start to actually code it. If you have ideas, please write it in the specific page. | ||
Contents |
If you want to claim a task, please put your name (or nickname, both is better) in brackets near the task you wish to claim. Please add it when you start working on it, and if you stop, please remove it, so we can know "who is working on what" and what tasks still needs to be started.
And, of course, this will avoid duplication of work. Thanks a lot! =)
| Note |
|---|
| This is a roughly sorted list of tasks that popped out during the meeting. We probably need to categorize it better, like seeing which task is blocker for which other, setting priority, split between "research" and "coding" and things like that. Still sounds like a premature thing though. |
This is what we are focussing on implementing right now:
And after that, see what can be done for performances:
Before actually coding them we should first define the speed compromises we want/can have for all of them. We will probably discuss it in the next meeting, and what we want for each of those widgets will be written in their specific pages. Then we can start to actually code it. If you have ideas, please write it in the specific page.
We also have:
Nice to have:
KDE TechBase 