Re: Dataengines, libs and default config

2009-09-20 Thread Aaron J. Seigo
On September 20, 2009, Petri Damstén wrote: > I think most of the kde-look.org plasmoids are made with python (quick > check from 20 highest rated is about 90%). I personally don't like the > idea of letting those to be second class citizens. obviously the majority of scripted widgets right now

Re: Dataengines, libs and default config

2009-09-20 Thread Petri Damstén
On Friday 18 September 2009 21:43:20 Aaron J. Seigo wrote: > On September 18, 2009, Petri Damstén wrote: > > > > Currently making a weather applet is much harder in scripting > > > > languages because you don't have access to the library. > > > > > > can't you build some QScript bindings for it? th

Re: Dataengines, libs and default config

2009-09-18 Thread Aaron J. Seigo
On September 18, 2009, Petri Damstén wrote: > > > Currently making a weather applet is much harder in scripting languages > > > because you don't have access to the library. > > > > can't you build some QScript bindings for it? then the applet can request > > that add-on? > > Yes of course but I

Re: Dataengines, libs and default config

2009-09-18 Thread Petri Damstén
On Friday 18 September 2009 20:26:20 Aaron J. Seigo wrote: > On September 18, 2009, Petri Damstén wrote: > > Would it be possible to put default config pages that are currently in > > libs (libplasmaweather, libplasmaclock, ...) to dataengine (or > > somewhere)? > > DataEngines can not do any UI.

Re: Dataengines, libs and default config

2009-09-18 Thread Aaron J. Seigo
On September 18, 2009, Petri Damstén wrote: > Would it be possible to put default config pages that are currently in libs > (libplasmaweather, libplasmaclock, ...) to dataengine (or somewhere)? DataEngines can not do any UI. > Currently making a weather applet is much harder in scripting language