Commit 60717e99 authored by Yuri Chornoivan's avatar Yuri Chornoivan
Browse files

Fix various minor typos

parent e366e48f
......@@ -95,7 +95,7 @@ Item {
// TODO: This restriction (minus the timer, which improves things)
// has been proven out in the EITM fork, but could be improved later
// by tracking the cursor movement vector and allowing the drag if
// the movement direction has reversed, etablishing user intent to
// the movement direction has reversed, establishing user intent to
// move back.
if (!plasmoid.configuration.separateLaunchers && tasks.dragSource != null
&& tasks.dragSource.m.IsLauncher === true && above.m.IsLauncher !== true
......
......@@ -3,9 +3,9 @@ Plasmoids
What is a widget?
================
In the context of Plasma, a "widget" is a single, self-contained graphical object on the canvas. They can be added and removed individually, configured separately from other widgets, etc. These "mini appliations" are sometimes referred to in other widget platforms as "applets", "apps", "gadgets", "karambas", "desklets". We chose the word "widget" for Plasma as it is used by other some other existing systems.
In the context of Plasma, a "widget" is a single, self-contained graphical object on the canvas. They can be added and removed individually, configured separately from other widgets, etc. These "mini applications" are sometimes referred to in other widget platforms as "applets", "apps", "gadgets", "karambas", "desklets". We chose the word "widget" for Plasma as it is used by other some other existing systems.
The API of a widget is defined by the host "ScriptEngine", with the exception of native Plasma widgets written in C++ which allows plugins in loadable librareis which use the API of the Plasma library directly. Currently Plasma supports both such "native" widgets written in C++, ones written in various dynamic languages (Plasmoids) as well as:
The API of a widget is defined by the host "ScriptEngine", with the exception of native Plasma widgets written in C++ which allows plugins in loadable libraries which use the API of the Plasma library directly. Currently Plasma supports both such "native" widgets written in C++, ones written in various dynamic languages (Plasmoids) as well as:
* SuperKaramba's karambas
* Enlightenment 17 edje content
......@@ -15,7 +15,7 @@ These are loaded via host AppletScriptEngine plugins that bridge between the wid
What is a Plasmoid?
==================
A Plasmoid is a widget that can be loaded into Plasma that uses the native Plasma API and comes packaged in a single archive file that includes the code, metadata, images, configuration defintions, etc. Plasmoids may be currently written in the following languages / APIs:
A Plasmoid is a widget that can be loaded into Plasma that uses the native Plasma API and comes packaged in a single archive file that includes the code, metadata, images, configuration definitions, etc. Plasmoids may be currently written in the following languages / APIs:
* HTML/JavaScript widgets (essentially "web pages for Plasma"): they are limited to a small subset of the Plasma library API and DataEngines
* Simplified JavaScript: these are written in JavaScript but use a managed set of API from the Plasma library and elsewhere; these are the most likely to be widely portable between Plasma instances and are the most securable.
......@@ -23,7 +23,7 @@ A Plasmoid is a widget that can be loaded into Plasma that uses the native Plasm
* Ruby: full access to the Plasma, KDE, Qt and other Ruby APIs are provided
* Python: full access to the Plasma, KDE, Qt and other Python APIs are provided
There are tutorials for the various APIs avaiable here: http://techbase.kde.org/Development/Tutorials/Plasma
There are tutorials for the various APIs available here: https://techbase.kde.org/Development/Tutorials/Plasma
The Plasmoid Package
====================
......
......@@ -8,7 +8,7 @@
/***************************************************************************
* *
* This program is free software; you can redistribute it and/or modify *
* it under the terms of the GNU General Public License verstion 2 as *
* it under the terms of the GNU General Public License version 2 as *
* published by the Free Software Foundation *
* *
***************************************************************************/
......
......@@ -8,7 +8,7 @@
/***************************************************************************
* *
* This program is free software; you can redistribute it and/or modify *
* it under the terms of the GNU General Public License verstion 2 as *
* it under the terms of the GNU General Public License version 2 as *
* published by the Free Software Foundation *
* *
***************************************************************************/
......
......@@ -8,7 +8,7 @@
/***************************************************************************
* *
* This program is free software; you can redistribute it and/or modify *
* it under the terms of the GNU General Public License verstion 2 as *
* it under the terms of the GNU General Public License version 2 as *
* published by the Free Software Foundation *
* *
***************************************************************************/
......
......@@ -89,7 +89,7 @@ QVariant CursorThemeModel::headerData(int section, Qt::Orientation orientation,
}
}
// Numbered vertical header lables
// Numbered vertical header labels
return QString(section);
}
......
......@@ -102,7 +102,7 @@ QString XCursorTheme::findAlternative(const QString &name) const
// Qt uses non-standard names for some core cursors.
// If Xcursor fails to load the cursor, Qt creates it with the correct name using the
// core protcol instead (which in turn calls Xcursor). We emulate that process here.
// core protocol instead (which in turn calls Xcursor). We emulate that process here.
// Note that there's a core cursor called cross, but it's not the one Qt expects.
alternatives.insert(QStringLiteral("cross"), QStringLiteral("crosshair"));
alternatives.insert(QStringLiteral("up_arrow"), QStringLiteral("center_ptr"));
......
......@@ -55,7 +55,7 @@ Canvas {
// they extend to the left and right of the path, so with a
// lineWidth of 8 we'll need the entire scene scooted so
// 0,0 becomes 4,4. Since that also would screw up our absolute
// cordinates towards the right (e.g. our width bounds as reported
// coordinates towards the right (e.g. our width bounds as reported
// by XKB) we also need to then adjust the scale so the entire
// coordinate system so the scene leaves sufficient space at all
// borders.
......
......@@ -156,7 +156,7 @@ Window {
x: section.left
y: section.top
z: section.priority
// Dimension defintions can be a bit wonky for sections but overally should not
// Dimension definitions can be a bit wonky for sections but overally should not
// cause problems even when they are (so long as we don't actually render the
// sections themself)
width: section.width
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment