https://techbase.kde.org/api.php?action=feedcontributions&user=Fonz2591&feedformat=atomKDE TechBase - User contributions [en]2024-03-19T09:34:36ZUser contributionsMediaWiki 1.40.2https://techbase.kde.org/index.php?title=Projects/Plasma/Tasks&diff=12433Projects/Plasma/Tasks2007-07-24T17:06:46Z<p>Fonz2591: /* Plasma */</p>
<hr />
<div>{{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.}}<br />
<br />
== Tasks ==<br />
<br />
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.<br />
<br />
And, of course, this will avoid duplication of work. Thanks a lot! =)<br />
<br />
{{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.}}<br />
<br />
<br />
<br />
=== KRunner ===<br />
==== Major Bugs ====<br />
None! =)<br />
<br />
==== Runners ====<br />
* pull in options from kdesktop/minicli.cpp and merge into shell and app runners<br />
* ServiceRunner: better matching (case insensitivity, substring matching, performance, etc)<br />
* CalculatorRunner: complete ('''Baris''')<br />
* Search Runner: use strigi<br />
* listen to async match updates (Interface:updateMatches())<br />
* determine how to order runner plugins for searching; categorization?<br />
* runners, runners and more runners! e.g. a kalkhi plugin...?<br />
<br />
==== Interface ====<br />
* 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 ('''Baris''')<br />
* options slide drawer animation<br />
<br />
==== Misc ====<br />
* install [[Development/Tutorials/D-Bus/Autostart_Services|D-Bus autoactivation service]]<br />
* javascript bindings to runner.h<br />
<br />
=== Plasma ===<br />
''This is what we are focusing on implementing right now:''<br />
* '''general libplasma'''<br />
** unit tests.<br />
** api documentation reviews<br />
** XML Config: add support for unsupported data types (these are documented in the API docu)<br />
** layout code improvements (HuntsMan)<br />
** Applet needs a way to access resources for customization (think: clock faces)<br />
** provide a way to mark an applet as needing configuration before usage (similar to how we do with failureToLaunch)<br />
<br />
* '''Applets'''<br />
** application launcher interface<br />
** taskbar (robert knight; others welcome to help)<br />
** systray<br />
<br />
* '''plasmagik'''<br />
** Basic classes are in (Package, PackageMetadata, Packager and PackageStructure)! =)<br />
** unit tests<br />
** resuscitate trunk/playground/base/plasma/plasmagik<br />
<br />
* '''bindings'''<br />
** QtScript bindings are being worked on<br />
** need to re-evaluate the place of KRoss in the all of this<br />
<br />
* '''RootWidget''' (the "desktop")<br />
** 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<br />
<br />
* '''Corona''' (QGraphicsScene subclass)<br />
** Item groups: a container to group items (mostly applets, really) and handle layouting and level of detail<br />
** 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 ('''fonz''')<br />
** Saving and loading of layouts (Alexis)<br />
** The concept of form factor needs to move out of Corona and into the item group class<br />
<br />
* '''Views'''<br />
** Currently there is DesktopView which is, somewhat obviously, the desktop view onto the Corona<br />
** Implement configurable background painting. This can in part be ported from kdesktop for DesktopView. Should be plugin based.<br />
** Create a panel view<br />
** Create a dashboard view (full screen, always on top)<br />
<br />
* '''Widgets''' [[../Widgets|Here is a page describing the nature of these widgets]]. Widgets still needed that aren't implemented yet are:<br />
** Icon needs the icon hover feature to be finished<br />
** [[/HTMLViewer|An html widget]]<br />
** panner widget that shows N QGraphicsViewItems at a time in a fancy manner (asiraj)<br />
** a "something just changed" widget that provides a bit of animated flash when something changes (andred)<br />
<br />
* '''DataEngine'''<br />
** Configuration parameters for sources<br />
<br />
<br />
''We also have:''<br />
* Implement Zack's physical equations for animations<br />
<br />
''Nice to have:''<br />
* Implement python bindings of Plasma</div>Fonz2591https://techbase.kde.org/index.php?title=Projects/Plasma/Tasks&diff=8236Projects/Plasma/Tasks2007-02-23T01:35:58Z<p>Fonz2591: /* Tasks */</p>
<hr />
<div>{{note|This page is '''REALLY''' work in progress and at the moment is just about the meeting of 21/02/2006}}<br />
== Tasks ==<br />
<br />
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.<br />
<br />
And, of course, this will avoid duplication of work. Thanks a lot! =)<br />
<br />
{{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.}}<br />
<br />
''Deal with the last bits of KDesktop still there:''<br />
* Move the autostart functionality from KDesktop to ksmserver. ('''Stephan Kulow, coolo''')<br />
* Merge the functionalities of ~/.kde/Autostart with ~/.kde/share/autostart ('''Stephan Kulow, coolo''')<br />
* Complete runner classes in KRunner ('''Aaron, fonz2591''')<br />
* Integrate ksysguard's process table into KRunner ('''Riccardo Iaconelli, ruphy''' - '''Esben Hanse, esben''')<br />
<br />
''This is what we are focussing on implementing right now:''<br />
* Desktop layer:<br />
** Use a widget able to have background painting.<br />
** Implement the zooming of objects.<br />
** Implement the grouping of objects in collections (with special containers).<br />
<br />
''And after that, see what can be done for performances:''<br />
* Engine base classes and command line test utilities. ('''Aaron J. Seigo, aseigo''')<br />
* 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!@)<br />
* Create widgets aware of zooming. First we need to discuss what can be done for each of these elements. Needed widgets are:<br />
** [[/Label|A label]]<br />
** [[/Button|A button]]<br />
** [[/SVGViewer|An svg viewer]]<br />
** [[/HTMLViewer|An html widget]]<br />
** [[/Lineedit|A lineedit/textedit]] (does it already exists?)<br />
<br />
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.<br />
<br />
''We also have:''<br />
* Implement Zack's physical equations for animations</div>Fonz2591