Plasma/PlasmoidScripting: Difference between revisions
< Plasma
| Line 20: | Line 20: | ||
== Access Control == | == Access Control == | ||
* Central mechanism for controlling individual plasmoid access to DataEngines and Services | * Central mechanism for controlling individual plasmoid access to DataEngines and Services | ||
** 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 | * Integrate the cryptographic signing GSoC branch | ||
* Control access to DataEngines based on advertised safety levels | * Control access to DataEngines based on advertised safety levels | ||
Revision as of 19:23, 25 December 2010
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.
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
- ability to create from a QByteArray
- ability to create from a remote URL
Access Control
- Central mechanism for controlling individual plasmoid access to DataEngines and Services
- 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