On Wednesday, February 27, 2013 13:03:59 Marco Martin wrote: > On Wednesday 27 February 2013, Aaron J. Seigo wrote: > > > > 1. notifying the component (e.g. plasmoid) that configuration has > > > > completed > > > > > > I have an object exposed by the plasmoid, ConfigPropertyMap that is a > > > qqmlpropertymap, ie property bindings work with its values, so that > > > would > > > look like "automatic" without need for configChanged() event listener > > > > this is probably my favourite bit of this approach. we'll just need to > > make > > sure that the config object gets properly tickled when, for instance, > > javascripts are run via the Desktop Scripting API. > > at the moment i see only 2 ways: > a) just config file modifications watching (kconfigskeleton already does it > iirc) not efficient but works > > b) making that config object directly accessible to the desktop scripting > api (not sure if the latter would require desktop scripting moving to qml's > javascript instead of qtscript javascript as well)
what about reacting to configChanged in the script engine? that could connect a signal to each ConfigPropertyMap object ... -- Aaron J. Seigo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/plasma-devel
