Difference between revisions of "Projects/Plasma/Tasks"

Line 17: Line 17:
* pull in options from kdesktop/minicli.cpp and merge into shell and app runners
* pull in options from kdesktop/minicli.cpp and merge into shell and app runners
* runners, runners and more runners!
* runners, runners and more runners!
* action/verb support
==== Interface ====
==== Interface ====

Revision as of 18:16, 31 July 2008

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.


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! =)

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.



  • pull in options from kdesktop/minicli.cpp and merge into shell and app runners
  • runners, runners and more runners!
  • action/verb support


  • options slide drawer animation
  • the icon list needs to be turned into a horizontal scrolling procession (Ryan Bitanga)
  • options area needs to be cleaned up (it doesn't resize the window properly afterwards, it needs a nice background)



This is what we are focusing on implementing right now:

  • general libplasma
    • unit tests. (Bertjan Broeksema, bbroeksema)
    • api documentation reviews
    • 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
    • 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
    • Allow selecting of multiple icons by dragging an area around them. (cblauvelt)
    • Have a sane layout manager for icons on the desktop. (cblauvelt)
  • systray
    • ability to hide icons would be useful
  • Panel
    • most extragear and playground applets misbehave in the panel
    • UI for panel config
      • resizing and moving
    • adding multiple panels
  • Welcome Applet
    • 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
  • Folder View
    • an applet that displays the contents of a folder
    • if it was also a containment that could be used as a desktop, even better
  • Clocks
    • clocks share a lot of duplicate code, so it would be good for them to share what they can, like common configuration UI
    • a graphical timezone selector would be awesome
    • show other timezones in a tooltip like in kde3
  • plasmagik
    • unit tests
    • resuscitate trunk/playground/base/plasma/plasmagik (adjam, ruphy)
  • 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
      • need zoomed-out UI for creating containments
    • Ability to define default panel/desktop/applet layouts without modifying loadDefaultSetup code, e.g. with config files on disk.
      • provide a way to define a default config to be read in at start up. this could be as easy as looking for a particularly named file, e.g. plasma-appletsrc-defaults or as "tricksy" (though not much more so) as having this kept in a global config file (e.g. [General] group, key DefaultAppletConfig) ...
      • this needs to be done in the application and not libplasma as this will be specific to the application. add a Corona::setConfigFile would also be handy, as loadApplets sets the config file name, which wouldn't be desirable in this case.
    • put the pager on the panel by default
  • Views
  • DataEngine
    • Configuration parameters for sources

We also have:

  • Implement Zack's physical equations for animations

Nice to have:

  • Associate units with a data source's data?

This page was last edited on 31 July 2008, at 18:16. Content is available under Creative Commons License SA 4.0 unless otherwise noted.