Jump to content

Plasma/PlasmoidScripting: Difference between revisions

From KDE Community Wiki
Notmart (talk | contribs)
Aseigo (talk | contribs)
No edit summary
Line 30: Line 30:
* Integrate the cryptographic signing GSoC branch
* Integrate the cryptographic signing GSoC branch
* Control access to DataEngines based on advertised safety levels
* 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?)

Revision as of 22:38, 16 January 2011

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.

Tooltips

  • Bind in Plasma::ToolTipManager and Plasma::ToolTipContent

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

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?)