Re: documenting javascript DataEgine and Runners

2010-02-02 Thread Will Stephenson
On Monday 01 Feb 2010 17:35:24 Aaron J. Seigo wrote:
 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.

Ok, plasmoid.dataEngine() is used in 
 http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/DataEngine
- is that just wrong?

Will
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: documenting javascript DataEgine and Runners

2010-02-02 Thread Aaron J. Seigo
On February 2, 2010, Will Stephenson wrote:
 On Monday 01 Feb 2010 17:35:24 Aaron J. Seigo wrote:
  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.
 
 Ok, plasmoid.dataEngine() is used in
  http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/DataEngine
 - is that just wrong?

yes :) i will fix that...

-- 
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
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: documenting javascript DataEgine and Runners

2010-02-01 Thread 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
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: documenting javascript DataEgine and Runners

2010-01-31 Thread Will Stephenson
On Thursday 21 Jan 2010 00:29:36 Aaron J. Seigo wrote:
 i've got my hands pretty full right now with documenting the JavaScript
 Plasmoid API:
 
 http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/API

Speaking of this, was there a JS API change between 4.4 and trunk?  
Specifically, the plasmoid.dataEngine() method appears to have moved from a 
global variable in 4.4 to a member of plasmoid.  

Also debug()  is a top level function but plasmoid.print() is not - 
http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/API#Print_and_Debug
 
describes them both as top level.

Is the JS API supposed to be fixed as of 4.4?

Will
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: documenting javascript DataEgine and Runners

2010-01-20 Thread Artur Souza (MoRpHeUz)
On Wed, Jan 20, 2010 at 8:29 PM, Aaron J. Seigo ase...@kde.org wrote:
 the sources are in kdebase/runtime/plasma/scriptengines/javascript/ in the
 javascripdataengine.cpp and javascriptrunner.cpp files.

 anyone interested? i'm happy to mentor/provide pointers in the right
 directions

I'll try start writing it during my flight time on Friday but don't
take this as granted, so if there is anybody still wanting to do it
just go for it :) I can merge stuff later :)

Cheers,

-- 
---
Artur Duque de Souza
OpenBossa Research Labs
INdT - Instituto Nokia de Tecnologia
---
Blog: http://labs.morpheuz.eng.br/blog/
PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
---
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: documenting javascript DataEgine and Runners

2010-01-20 Thread Artur Souza (MoRpHeUz)
On Wed, Jan 20, 2010 at 8:29 PM, Aaron J. Seigo ase...@kde.org wrote:
 the sources are in kdebase/runtime/plasma/scriptengines/javascript/ in the
 javascripdataengine.cpp and javascriptrunner.cpp files.

 anyone interested? i'm happy to mentor/provide pointers in the right
 directions

I'll try start writing it during my flight time on Friday but don't
take this as granted, so if there is anybody still wanting to do it
just go for it :) I can merge stuff later :)

Cheers,


-- 
---
Artur Duque de Souza
OpenBossa Research Labs
INdT - Instituto Nokia de Tecnologia
---
Blog: http://labs.morpheuz.eng.br/blog/
PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
---
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel