Difference between revisions of "Plasma/Terminology"

Jump to: navigation, search
(Workspace)
m (Fix minor typos)
 
Line 1: Line 1:
On this page, we collect definitions of terms used in Plasma. Its main purpose is to get developers' terminology synchronized.
+
On this page, we collect definitions of terms used in Plasma. Its main purpose is to get the developers' terminology synchronized.
  
 
= Workflow =
 
= Workflow =
Line 24: Line 24:
  
 
= Shell =
 
= Shell =
The shell, technically speaking, is the binary that will load and display the UI parts of the "Workspace". It doesn't provide its own UI, it may be tied to a particular formfactor.
+
The shell, technically speaking, is the binary that will load and display the UI parts of the "Workspace". It doesn't provide its own UI, it may be tied to a particular form-factor.
  
 
Examples (these refer *only* to binary names):
 
Examples (these refer *only* to binary names):
Line 32: Line 32:
  
 
=== Current Implementation ===
 
=== Current Implementation ===
The term shell does not include Plasmoids loaded into it, it's provides the implementation of the Corona and defines how the views are bound to it. These views hold containments, which then load applets. The particular shell and the final UX are only tied in part.
+
The term shell does not include Plasmoids loaded into it, it provides the implementation of the Corona and defines how the views are bound to it. These views hold containment, which then loads applets. The particular shell and the final UX are only tied in part.
  
 
= Activities =
 
= Activities =
Line 44: Line 44:
 
* Calligra Active
 
* Calligra Active
  
Action Item: Take proposal to call all workspaces "Plasma" or "Active" to kde-promo, with the intention of removing the other brand.
+
Action Item: Take the proposal to call all workspaces "Plasma" or "Active" to kde-promo, with the intention of removing the other brand.
  
  

Latest revision as of 17:48, 14 June 2019

On this page, we collect definitions of terms used in Plasma. Its main purpose is to get the developers' terminology synchronized.

Workflow

Workflow is the sequence of actions a user performs to accomplish a task. A workflow involves applications, but can also lead the user across devices.

Example:

  • Writing a report and sending it to your boss
  • Importing photos and reviewing them
  • Interacting friends (catching up on the social network, taking part)
  • Running into articles while working on the desktop, reading them on your tablet later
  • Downloading a movie on the laptop, watching it on the TV/Media Center

Workspace

The workspace's purpose is to guide the user through their workflow, across applications. A workspace runs on a specific device, such as Desktop, tablet, etc, and forms part of workflows across devices. The workspace is a generic term for all the software component intended to provide the final UX for the global work environment, the minimal "fixed" running user interface that manages documents, applications (opening, closing) and global system properties such as notifications or attached hardware devices.

Examples:

  • Plasma Desktop (or "KDE Plasma Desktop")
  • Plasma Netbook (or "KDE Plasma Netbook")
  • Plasma Active (or "KDE Plasma Active" (in case that wasn't clear by now))

(KDE is used as umbrella brand in this context, standing for "created by the KDE community")

Shell

The shell, technically speaking, is the binary that will load and display the UI parts of the "Workspace". It doesn't provide its own UI, it may be tied to a particular form-factor.

Examples (these refer *only* to binary names):

  • plasma-desktop
  • plasma-netbook
  • plasma-device

Current Implementation

The term shell does not include Plasmoids loaded into it, it provides the implementation of the Corona and defines how the views are bound to it. These views hold containment, which then loads applets. The particular shell and the final UX are only tied in part.

Activities

Active Applications (work in progress)

Active applications follow a set of user interface guidelines to integrate well with Plasma workspaces across different devices (including desktops).

Examples:

  • Okular Active
  • Calligra Active

Action Item: Take the proposal to call all workspaces "Plasma" or "Active" to kde-promo, with the intention of removing the other brand.


Vision

Today people have huge numbers of files, devices, people they know, network services they use; and few use their computer (laptop / desktop) for just one particular task (work, entertainment, personal communication, school..).

Plasma Workspaces should enable workflows for multiple tasks, possibly on multiple devices, focusing on providing scalable interfaces to present information and access to data in ways people will find useful for today's contexts. This should all be presented using direct manipulation interfaces that have an organic look and feel.


We would also like you to acknowledge that the term to describe a certain avian animal. Or, to paraphrase it: THE BIRD IS THE WORD.


This page was last modified on 14 June 2019, at 17:48. Content is available under Creative Commons License SA 4.0 unless otherwise noted.