Tasks

Just put your name (or nickname) in brackets near the task you want to claim. This will avoid duplication of work. Thanks! =)

What happened in the meeting

This wants to be just a short resume on what happened in the first meeting (21-02-2006)

First thing, Aaron explained us what is his idea of Plasma and why he arrived there. Especially, he said that: «we need an amarok of the desktop so people go "oh. -that's- why"».

For those still not familiar with this concept, he explained also that everything will be "a widget (or, as somehow caught on, "plasmoid")... from the launcher buttons to full on widgets and mini-apps" Especially, the desktop won't be centered anymore on displaying the content of a folder. This will still remain availeable though, you will be able to do a full-screen plasmoid that shows the content of a certain folder. ;-)

After that, we started the discussion on what needs to be done. The first thing is to get all the essential components that still are in KDesktop been moved away. So, we are at a good point in this, because everything but the autostart stuff has been moved into KRunner. KRunner is a new application for KDE 4 that will manage the screensaver, will show a task list (like the windows' key combo Ctrl+Alt+Del), will provide a run dialog and manage app startup notification. KRunner will be a standalone app that will register global keycombos and show things as-needed.

The autostart stuff should probably be merged in ksmserver (it makes much more sense there), and be unique (right now there are ~/.kde/Autostart and ~/.kde/share/Autostart).

After having the old desktop killed, we will work on a replacement, Aaron said, and this means working on two separate parts: zooming and containers and efficient widgets.

Using or not QGraphicsView is a major concern right now, but we concluded that probably the final decision about what to use has to be delayed to the next meeting, or to the end of march at most, after having checked with the TT guys about whether it's possible to have a performant QGraphicsView for zooming in Qt 4.3 or not. In case the answer is not, we will implement it, modifying the existing engine. It seems that we all agree on the fact that we'd love to use QGraphicsView, altough it's a tricky decision to take right now. We decided to use it until the end of march and then see if it's still possible to continue using it.

It will also be really nice to make it capable of embedding widgets. It shouldn't be difficult to implement, but there is still no code for that. We will probably also need to create our own set of high-performant widgets, to enable really fast zooming. For example, the text can disappear, or we could not redraw the widget while the zoom factor remains under 0.75... The widgets we will need are:

A label
A button
An svg visualizer
An html widget
A lineedit/textedit

We still need to concretely define which optimisations can be done for _each_ widget, and then we will be able to actually write them.

Then we talked about visualization, and we briefly decided to use some of the Zack's phisical equations [[1]][[2]] to make the best animation possible. Aaron stated that we're ok as long as we don't run the physics engine continuously, otherwise it tends to burn CPU cycles.

Ok, now let's concretize all the stuff said above and put them in a sort of TODO:

New tasks popped out in the meeting

First, let's kill the last bits of KDesktop still there:

Put the autostart functionality from KDesktop to ksmserver.
Merge the functionalities of ~/.kde/Autostart with ~/.kde/share/autostart
Complete runner classes in krunner
Integrate ksysguard's process table into krunner

Then, this is what we want to implement:

What plasma will be able to do/what we do want from it:
- Use a widget able to have background painting.
- Implement the zooming of objects.
- Implement the grouping of objects in collections (with special containers).

And after that, see what can be done for performances:

See if QGV works well for ↑ (Unicode char for ^, arrow up). 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).
Create widgets aware of zooming. First we need to discuss what can be done for each of these elements. Needed widgets are:
- A label
- A button
- An svg viewer
- An html widget
- A lineedit/textedit (does it already exists?)

Before actually coding them we should first define the speed compromizes 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:

Implement Zack's pyisical equations for animations

Transcript

The transcript of the meeting is available here; or, alternatively you can view it in HTML here.