Jump to content

Plasma/PlasmoidScripting: Difference between revisions

From KDE Community Wiki
Aseigo (talk | contribs)
Created page with 'This page records currently outstanding TODOs for the Javascript and QML Plasmoid scripting support. Please feel free to tackle any of the items below at your convenience. == A...'
 
Afiestas (talk | contribs)
 
(59 intermediate revisions by 12 users not shown)
Line 1: Line 1:
This page records currently outstanding TODOs for the Javascript and QML Plasmoid scripting support. Please feel free to tackle any of the items below at your convenience.  
This page records currently outstanding TODOs for the Javascript and QML Plasmoid scripting support. This page deals with the Javascript only bindings or the QScriptEngine related bindings shared between both.
Please feel free to tackle any of the items below at your convenience.
For QML specific items, please see http://community.kde.org/Plasma/DeclarativeScripting
 
== I/O Write ==
 
* write methods that match the read I/O methods
 
== HTTP ==
 
* POST requests


== Autocompletion ==
== Autocompletion ==


* add methods to Plasma::LineEdit that map to the most important parts of KLineEdit's autocomplete API
* add methods to Plasma::LineEdit that map to the most important parts of KLineEdit's autocomplete API
== QPixmap (and QImage) ==
* ability to create from a QByteArray
* ability to create from a remote URL
== KLocale ==
* readonly access for KLocale: units of measurement, time, currency etc
== Access Control ==
* Central mechanism for controlling individual plasmoid access to DataEngines, Services and Extensions
** improve AppletAuthorization and use it in AppletInterface::dataEngine to restrict access
** perhaps allow the Containment to provide some policy?
** scriptable policies, so they are runtime?
* Integrate the cryptographic signing GSoC branch
* Control access to DataEngines based on advertised safety levels
== QMenu ==
* QMenu popups
== Configuration UI ==
* Expand/enrich config UI handling (Plasma::Widget and/or QML based?)
= Porting Plasmoids to QML =
All information about QML plasmoid porting has been move [[Plasma/QMLPorting#Porting_Plasmoids_to_QML | here]]

Latest revision as of 19:31, 14 September 2012

This page records currently outstanding TODOs for the Javascript and QML Plasmoid scripting support. This page deals with the Javascript only bindings or the QScriptEngine related bindings shared between both. Please feel free to tackle any of the items below at your convenience. For QML specific items, please see http://community.kde.org/Plasma/DeclarativeScripting

I/O Write

  • write methods that match the read I/O methods

HTTP

  • POST requests

Autocompletion

  • add methods to Plasma::LineEdit that map to the most important parts of KLineEdit's autocomplete API

QPixmap (and QImage)

  • ability to create from a QByteArray
  • ability to create from a remote URL

KLocale

  • readonly access for KLocale: units of measurement, time, currency etc

Access Control

  • Central mechanism for controlling individual plasmoid access to DataEngines, Services and Extensions
    • improve AppletAuthorization and use it in AppletInterface::dataEngine to restrict access
    • perhaps allow the Containment to provide some policy?
    • scriptable policies, so they are runtime?
  • Integrate the cryptographic signing GSoC branch
  • Control access to DataEngines based on advertised safety levels

QMenu

  • QMenu popups

Configuration UI

  • Expand/enrich config UI handling (Plasma::Widget and/or QML based?)

Porting Plasmoids to QML

All information about QML plasmoid porting has been move here