Projects/Plasma/Tasks: Difference between revisions

Latest revision as of 20:59, 4 January 2010

Warning

If you clear a task, please write "Completed" near it. If you are still working on it, please put your name. Percentage of the work done is accepted.

Tasks

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 not meant to be a replacement for the feature list on the release schedules pages, but rather a place to record things that aren't there.

KRunner

Runners

runners, runners and more runners!

Interface

improve paging
nicer user switcher

Misc

Plasma

Documentation
- design docs coverage (workspace/plasma/design/)
- Techbase tutorials for:
  - Wallpaper plugins
  - Containments
  - DataEngine
  - Service
  - Theming
- website overhaul
General libplasma
- more unit tests.

Plasma::Applet
- add global settings config page, if it exists in the Package (which means adding a pair of entries in packages.cpp for globalconfigui and globalconfigxml), alongside the per-applet ones
- a way to access resources for customization (think: clock faces)

Corona (QGraphicsScene subclass)

Views

Widgets Here is a page describing the nature of these widgets. Widgets still needed that aren't implemented yet are:

DataEngine

Applets
- Welcome
  - offer quick access to a few starting points including: documentation, the online community, kde tips, configuration, etc.
  - each button should show a little help text when clicked along with some links/buttons that the user can click on to go somewhere.
  - have an area on it that allows one to enter or create an openid account.
  - see Projects/Plasma/Welcome and this image
- Timeline

@@ Line 1: / Line 1: @@
+{{warning|If you clear a task, please write "'''Completed'''" near it. If you are still working on it, please put your name. Percentage of the work done is accepted.}}
 == Tasks ==
@@ Line 5: / Line 9: @@
 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.}}
+{{note|This is not meant to be a replacement for the feature list on the [[Schedules|release schedules pages]], but rather a place to record things that aren't there.}}
-=== Deal with the last bits of KDesktop  ===
-* Move the autostart functionality from KDesktop to ksmserver. ('''Stephan Kulow, coolo''')
-* Merge the functionalities of ~/.kde/Autostart with ~/.kde/share/autostart ('''Stephan Kulow, coolo''')
 === KRunner ===
-==== Major Bugs ====
-* figure out why Interface::display() sometimes doesn't result in the widget displaying
 ==== Runners ====
-* pull in options from kdesktop/minicli.cpp and merge into shell and app runners
+* runners, runners and more runners!
-* ServiceRunner: better matching (case insensitivity, substring matching, performance, etc)
-* SessionRunner: connect QActions up, show users and sessions, etc
-* CalculatorRunner: complete ('''Baris''')
-* Search Runner: use strigi
-* listen to async match updates (Interface:updateMatches())
-* determine how to order runner plugins for searching; categorization?
-* runners, runners and more runners! e.g. a kalkhi plugin...?
 ==== Interface ====
-* abstract out the svg background part of Interface and have it subclass QDialog; then make screensaver/lock dialogs subclass that and therefore look a bit more sexy and consistent
+* improve paging
-* options slide drawer animation
+* nicer user switcher
 ==== Misc ====
-* Integrate ksysguard's process table into KRunner ('''John Tapsell, johnflux''' - '''Riccardo Iaconelli, ruphy''' - '''Esben Hanse, esben''')
-* install [[Development/Tutorials/D-Bus/Autostart_Services|D-Bus autoactivation service]]
-* javascript bindings to runner.h
 === Plasma ===
-''This is what we are focussing on implementing right now:''
-* Desktop layer:
-** 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:''
+* '''Documentation'''
-* Engine base classes and command line test utilities. ('''Aaron J. Seigo, aseigo''')
+** design docs coverage (workspace/plasma/design/)
-* 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!@)
+** Techbase tutorials for:
-* Create widgets aware of zooming. First we need to discuss what can be done for each of these elements. Needed widgets are:
+*** Wallpaper plugins
-** [[/Label|A label]]
+*** Containments
-** [[/Button|A button]]
+*** DataEngine
-** [[/SVGViewer|An svg viewer]]
+*** Service
-** [[/HTMLViewer|An html widget]]
+*** Theming
-** [[/Lineedit|A lineedit/textedit]] (does it already exists?)
+** website overhaul
+* '''General libplasma'''
+** more unit tests.
+* '''Plasma::Applet'''
+** add global settings config page, if it exists in the Package (which means adding a pair of entries in packages.cpp for globalconfigui and globalconfigxml), alongside the per-applet ones
+** a way to access resources for customization (think: clock faces)
+* '''Corona''' (QGraphicsScene subclass)
+* '''Views'''
-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.
+* '''Widgets''' [[../Widgets|Here is a page describing the nature of these widgets]]. Widgets still needed that aren't implemented yet are:
-''We also have:''
+* '''DataEngine'''
-* Implement Zack's physical equations for animations
-''Nice to have:''
+* '''Applets'''
-* Implement python bindings of Plasma
+** Welcome
+*** offer quick access to a few starting points including: documentation, the online community, kde tips, configuration, etc.
+*** each button should show a little help text when clicked along with some links/buttons that the user can click on to go somewhere.
+*** have an area on it that allows one to enter or create an openid account.
+*** see [[Projects/Plasma/Welcome]] and [http://bddf.ca/~aseigo/welcometokde4.png this image]
+** Timeline