Talk:KDE Plasma 4

Untitled
Borderline C but some may not agree.

I got a message saying this was proposed for deletion. I didn't figure out how to find out why. I assume because KDE4 is out. Could the person who marked it for deletion post why here? Shortgeek (talk) 20:50, 20 January 2008 (UTC)

I have removed the Stub status of this article in the WikiProject Computing block, but don't know what class the article does belong to. If someone else knows, please fill it in. Starofale (talk) 21:10, 13 January 2011 (UTC)

2011-04-26 Review thoughts:
You have done a very appreciated job of trying to connect prior terms to current, thank you!

So many terms flying around, changing so frequently, articles like this help - thank you for having it here to refer to.

- "In its default configuration it resembles earlier KDE Software Compilation releases ..." - can you refine? KDE was a set of software, including a display manager. Plasma is only a display manager (if I follow your article correctly). Today, KDE still seems to be a set of software, that includes Plasma as its display manager. So your sentence is confusing. Perhaps "In its default configuration, Plasma resembles the former KDE display manager, part of the KDE Software Compilation, ...

-- Part of the confusion is KDE used to be 'KDE'. Now KDE includes Plasma. KDE <!=> Plasma, but it could be commonly construed in the past that KDE <=> KDE.

- "Plasma Active is not a workspace on its own. It is a service built on top of the Plasma frameworks that enables the creation of full-fledged workspaces using only QML files without the need to program in C++." The earlier implication is that Plasma is the display manager. Here, Plasma Active is not a display manager, but built on Plasma frameworks. Leading to the question

--- how is something displayed if there is no display manager? Perhaps Plasma Active is a framework to sit upon a device's native display manager?

- "Two examples of containments are the desktop background and the taskbar" Does the taskbar sit on top of the background? i.e. An example of a containment with a containment?

- "containment can be anything the developer wants: an image (either raster graphics or an SVG image), animation, or even OpenGL. Images are most commonly used, but with Plasma the user could set any applet as the desktop background " earlier you note "Plasma separates components into "data engines" and their visualization counterparts". In this section you have mixed the two, could you continue to separate them? "the user could set any applet to provide the desktop background image"?

- "Widgets are aware of their size and can be made to show more or less data depending on their size. Plasma can support other widgets." - you have crossed from applets to widgets here. Pick one term, or, explain what widgets are. Connect those dots.

... sorry, ran out of gas on this, stopping here.

Bs27975 (talk) 11:20, 26 April 2012 (UTC)


 * I have no idea who you are talking to and I also have no idea what your “<!=>” stuff means.
 * Some of your feedback is valid, other feedback is not. Eg. where do you have your “display manager” stuff from? Seems you don’t know what a display manager (KDE Display Manager) is. Maybe you also confuse it with X window managers (KWin), widget toolkits (Qt), X.Org Server, or whatever. Whatever it is you confuse, it is out of scope of this article to explain how typical Linux distributions are set up in order to render graphics on screen. --KAMiKAZOW (talk) 01:22, 28 April 2012 (UTC)


 * @Bs27975: Desktop widgets are (small) applications that are run by a widget engine. See the articles display server/windowing system (and my very cool illustrations there) and then understand, that GNOME Shell is partly programmed as a plugin to mutter. GNOME Shell is called a "UX", a "GUI" or a "graphical shell". similar to GNOME Panel, KDesktop or Plasma Active. User:ScotXW t@lk 14:00, 21 May 2014 (UTC)

": I have no idea who you are talking to and I also have no idea what your “<!=>” stuff means." (1) Who I am talking to is irrelevant, it is commentary upon the article, and one reader's comments. Take it as feedback, and do with it what you will. Whether you consider it valid or useful or not is irrelevant - it is feedback / input / suggestions. (2) <-> is pretty intuitively understood unless you are deliberately choosing not to. <=> is a petty intuitive equivalent. '=' is what it is in the computer / programming world - if you do not understand it, why are you writing an article / how can you possibly expect to be taken as credible. In that world '!=', since '!' is commonly understood to equal 'not', make '!=' obviously into not equal.

": Some of your feedback is valid, other feedback is not. Eg. where do you have your “display manager” stuff from?" (1) Feedback is always valid. Feedback is always from the perspective of the reader. That it's not your perspective, or that you don't agree with it, doesn't invalidate the feedback. (2) As I wrote "KDE was a set of software, including a display manager. Plasma is only a display manager (if I follow your article correctly). Today, KDE still seems to be a set of software, that includes Plasma as its display manager. So your sentence is confusing. Perhaps \"In its default configuration, Plasma resembles the former KDE display manager, part of the KDE Software Compilation\", ... " - KDE was (is) commonly perceived to be a graphical environment. Along the way KDE became KDE SC, and a new reader may not yet understand that. Even an old reader seeking to get up to speed will still assume KDE is KDE, until they understand plasma is now present, yet 'plasma' is an almost useless unintuitive term. So they land here, in this article - trying to understand what's what. So part of what I am saying here is ... help the reader (SIMPLY!) understand which is what and where to go for better information and understanding. The point is not what I do and do not know, the point is the article is not informing which is what, how, and thus confusing to read. Take the comment as a note that some reader found it confusing, and requested clarification and refactoring. Whether or not a display manager is a window manager or not, my point is a reader coming here may or may not understand the nuances - so your article could be improved either by explaining that, or by wikiword linking to articles that do. In essence, pulling on the 'KDE', let alone 'plasma' (given 'kde-plasma') thread leads to many other threads both forwards and backwards. What a (this) reader has expressed here in talk is - 'I still find your article confusing, please help!' Please just take it as that - a call for help. Whether you do or can (have the time) is up to you, but that doesn't invalidate the call for (additional) help.

Why has Gnome anything crept into this discussion on a KDE element?

Why has any other linux distributions crept into the discussion on this article?

Please don't be defensive. I gave reasonable feedback with request and perhaps suggestions for clarification and making a better article for the reader you intended to serve in writing the article in the first place. Take them as you will, but please don't attack. Please remember the first two lines given: "You have done a very appreciated job of trying to connect prior terms to current, thank you!" and "So many terms flying around, changing so frequently, articles like this help - thank you for having it here to refer to." I will say this again - THANK YOU! for writing the article. All of this is highly confusing and inter-related, and your attempts to bring some linearity and comprehension to the ecosystem is very much appreciated. It was not an attack - please don't do so. Please just take it as "I'm still confused."

BS (talk) 16:46, 6 December 2014 (UTC)

Cleanup 3-24-2014
Fixed "non-native language" mentioned in the Cleanup box from Feb. 2014 but not sure what constitutes "inappropriate tone." — Preceding unsigned comment added by 66.212.53.23 (talk) 18:34, 24 March 2014 (UTC)

File:Linux kernel ubiquity
My scheme was removed, though it actually illustrates the intent behind KDE Plasma Workspaces very well: In case my illustration, since it mentions the Linux kernel is sooo damn bad, leave it out of the article, but claiming it an umbrella term, is just plain wrong. User:ScotXW t@lk 13:49, 21 May 2014 (UTC)
 * 1) Some people confuse "Plasma Workspaces" with Qt or GTK+ (i.e. widget libraries), though it rather resembles GNOME Shell/KDesktop (i.e. a UX, a GUI, a graphical shell).
 * 2) But even the comparison with GNOME Shell is actually wrong, because Plasma Workspaces (plural) is rather a framework to facilitate the creation of multiple UXs. And multiple UXs were indeed created: Plasma Desktop, Plasma Active and Plasma Netbook. File:Linux kernel ubiquity.svg illustrates exactly this intention perfectly.
 * 3) KDE Plasma Workspaces is not a "bundle" nor an "umbrella term" of multiple UXs, but indeed a framework to create such.

Vandalism in WIKIDATA
Someone at "14:40, 29 June 2016" removed the enwiki link in the WIKIDATA and caused the en.wiki article had not any interlanguage link for more than 5 mounths! please check and report this vandalism. I re-turned the en.wiki link. Editor-1 (talk) 14:23, 13 December 2016 (UTC)