Difference between revisions of "Projects/Plasma/Tasks"

Jump to: navigation, search
(Plasma)
(Open Issues For Review)
 
(35 intermediate revisions by 10 users not shown)
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.}}
 
{{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 ==
 
== Tasks ==
Line 7: Line 9:
 
And, of course, this will avoid duplication of work. Thanks a lot! =)
 
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.}}
 
+
  
  
Line 15: Line 16:
  
 
==== Runners ====
 
==== Runners ====
* pull in options from kdesktop/minicli.cpp and merge into shell and app runners
 
* Search Runner: use strigi (blocked by Xesam)
 
* listen to async match updates (Interface:updateMatches())
 
 
* runners, runners and more runners!
 
* runners, runners and more runners!
  
 
==== Interface ====
 
==== Interface ====
* options slide drawer animation
+
* improve paging
 +
* nicer user switcher
  
 
==== Misc ====
 
==== Misc ====
* install [[Development/Tutorials/D-Bus/Autostart_Services|D-Bus autoactivation service]]
 
* QtScript bindings to AbstractRunner
 
  
 +
=== 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 ===
+
* '''Plasma::Applet'''
''This is what we are focusing on implementing right now:''
+
* '''general libplasma'''
+
** unit tests. (Bertjan Broeksema, bbroeksema)
+
** api documentation reviews
+
** XML Config: add support for unsupported data types (these are documented in the API docu)
+
** Applet needs a way to access resources for customization (think: clock faces)
+
** Need to implement the math in Phase to update the intervals according to the CurveShape, ala QTimeLine (ask aseigo for more details if you find that cryptic ;)
+
 
+
* '''Applets'''
+
** application launcher interface
+
** <div style="color: green">taskbar (Robert Knight; others welcome to help)</div>
+
** <div style="color: green">systray (Alexander Rodin; others welcome to help)</div>
+
** <div style="color: green">on mouse over, show a set of small buttons that allow for the following actions: close, configure, lock, information and move. aseigo has graphics for the buttons already. (manyoso)</div>
+
 
** 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
 
** 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
* '''systray'''
+
** a way to access resources for customization (think: clock faces)
** should have borders so as to be able to live on desktop
+
** grid layout of icons would be nice
+
* '''plasmagik'''
+
** unit tests
+
** <div style="color: green">resuscitate trunk/playground/base/plasma/plasmagik (adjam, ruphy)</div>
+
** Pager is too sensitive to mouse moves during a click. If the mouse moves at all during a click the pager does not switch desktops. (JustinNoel)
+
** Applets launched on Screen 0 of ATI fglrx Pseudo-Xinerama setup do not drag across the Screen 1. However, Applets launched on Screen 1 drag just fine. There is an Applet Launcher in the corner of both Screen 0 and Screen 1. (JustiNoel)
+
 
+
* '''bindings'''
+
** <div style="color: green">QtScript bindings are being worked on (rdale)</div>
+
 
+
* '''RootWidget''' (the "desktop")
+
** <div style="color: green">Controls box: an expand-on-mouse-over widget that sits on top of the graphicsview and provides discoverable access to zooming, jumping, configuration, adding of elements, locking ...? Currently needs to pretty-fied and the more "techie" options removed (aseigo)</div>
+
  
 
* '''Corona''' (QGraphicsScene subclass)
 
* '''Corona''' (QGraphicsScene subclass)
** Zooming: 3-level zooming needs to be supported. 100% == 1 item group at full zoom; 50% == all item groups visible with panning with each item replaced by a simple icon; 10% == all item groups visible without panning, each group replaced by a simple icon and items not painted at all
 
** Ability to define default panel/desktop/applet layouts without modifying loadDefaultSetup code, e.g. with config files on disk.
 
  
 
* '''Views'''
 
* '''Views'''
** Implement configurable background painting. This can in part be ported from kdesktop for DesktopView.
 
** Implement composite based translucency for panels
 
** Create a dashboard view (full screen, always on top)
 
  
 
* '''Widgets''' [[../Widgets|Here is a page describing the nature of these widgets]]. Widgets still needed that aren't implemented yet are:
 
* '''Widgets''' [[../Widgets|Here is a page describing the nature of these widgets]]. Widgets still needed that aren't implemented yet are:
** Icon needs the icon hover feature to be finished
 
** [[/HTMLViewer|An html widget]]
 
** panner widget that shows N QGraphicsViewItems at a time in a fancy manner (asiraj)
 
  
 
* '''DataEngine'''
 
* '''DataEngine'''
** Configuration parameters for sources
 
  
''We also have:''
+
* '''Applets'''
* Implement Zack's physical equations for animations
+
** Welcome
 
+
*** offer quick access to a few starting points including: documentation, the online community, kde tips, configuration, etc.
''Nice to have:''
+
*** each button should show a little help text when clicked along with some links/buttons that the user can click on to go somewhere.
* Implement python bindings of Plasma
+
*** have an area on it that allows one to enter or create an openid account.
* Associate units with a data source's data?
+
*** see [[Projects/Plasma/Welcome]] and [http://bddf.ca/~aseigo/welcometokde4.png this image]
 +
** Timeline

Latest revision as of 21:59, 4 January 2010

noframe
 
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.



Contents

[edit] 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! =)

noframe
 
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.


[edit] KRunner

[edit] Runners

  • runners, runners and more runners!

[edit] Interface

  • improve paging
  • nicer user switcher

[edit] Misc

[edit] 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
  • 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

This page was last modified on 4 January 2010, at 21:59. This page has been accessed 35,234 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal