documenting javascript DataEgine and Runners

[Aaron J. Seigo]

On January 31, 2010, Will Stephenson wrote:
> Speaking of this, was there a JS API change between 4.4 and trunk?

there shouldn't be; they should be identical. the idea is to keep strict 
compat in the JS API from 4.4.0 onward.

> Specifically, the plasmoid.dataEngine() method appears to have moved from a
> global variable in 4.4 to a member of plasmoid.

i don't think that's changed at all, actually. the code is identical in both 
4.4 and 4.5. i just tested with trunk and dataEngine is still, indeed, a 
global function.

i think that plasmoid.dataEngine would actually be better and more consistent, 
but i'm not sure it's worth breaking whatever JS plasmoids exist prior to 4.4. 
there are already published JS plasmoids using the top-level method and while 
it is a wart it's a smallish one and probably not worth changing.

> Also debug()  is a top level function but plasmoid.print() is not -

print is a top level function and debug wasn't ... in trunk they both are. i 
will fix this so that debug() is a top level function in both releases.

> http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/API#Print_a
> nd_Debug describes them both as top level.

yes, they should be.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks