Revision as of 14:49, 16 May 2012

Methodology

current vision, ideas, concepts and terminology: are we thinking the same thing when we say a term?
identify user scenarios, what do you want to do, why and in what situation

in the machine (example: being at work on a document while discussing about it simultaneously on email, chat and audio call)

  "because it works on OSX" or even "because it works on Plasma Desktop" are not valid answers ;)

Thinking instead for a moment about the other solutions: why the solution of other system does work/why it doesn't work?

dedication to a task vs listening mucic/glancing over news items while working)

Define sub tasks of the "manifesto" points, more deltailed, but still not regarding implementation

think in steps required to do a task: not just in "launching applications" that is just an aspect of it
what is and what should be the boundary between what is an app and what is the workspace
generic "information flow" of everything that i see on the screen: includes applications switching, not limited to it

Write an updated version of what is now "ways of the plasma", ui guidelines etc
identify where the work has to be done for an abstract task item:
- bluedevil
- libplasma
- qml components
- tasks applet
actual coding/documenting/coding tasks up for grab ;)

@@ Line 7: / Line 7: @@
 * what in current suituation of things matches with this?
 * what doesn't?
-* Try to answer the problem without looking at other
+* Try to answer the problem without looking at other answers..
-answers.. "because it works on OSX" or even "because it works on Plasma
+   "because it works on OSX" or even "because it works on Plasma Desktop" are not valid answers ;)
-Desktop" are not valid answers ;)
+* Thinking instead for a moment about the other solutions: why the solution of other system does work/why it doesn't work?
-* Wwhy the solution of other system does work/why it
-doesn't work?
 ==High level "manifesto" points==