[Kde-bindings] KDE/kdebindings

[Arno Rehn]

Am Montag 12 Mai 2008 12:07:49 schrieb Richard Dale:
> On Saturday 10 May 2008 14:58:34 Sebastian Sauer wrote:
> > > I agree that following the standard Plasma packaging
> > > convention for non-C++ languages is certainly a good idea, and probably
> > > using the ScriptEngine api will have advantages in the future. I'll try
> > > and get a ScriptEngine/Korundum based binding done in the playground,
> > > rather than in kdebindings itself - I've thought about it a bit and it
> > > will be possible to get pretty much the same api as I had before with a
> > > bit of work.
> >
> > Even more great to hear.
>
> On Saturday I was thinking about this again and I realised that the
> krubyplugfactory allows me to write any KDE plugin in Ruby, and that the
> ScriptEngine script runners are just another sort of plugin. I already have
> all the apis for script runners wrapped as bindings in Ruby. This means
> that it is actually possible to implement the Ruby script runners for
> applets and data engines in Ruby, which makes it pretty trivial.
>
> I need to understand the package format a bit more, because you need to
> write code that describes the layout of a package (also possible in Ruby).
> The big problem is that the scripting api doesn't give you any way to
> access KConfig stuff, and not being able to read and write config data is a
> bit of a show stopper. I may need to cheat for now to work round that until
> there is an 'official' way of doing it.
Well, nothing prevents you to require Korundum in your ruby script. AFAIK that 
has nothing to do with wheter you write a plasma script or a ruby app. The 
scriptengine api provides popupConfigDialog (or similar, forgot the correct 
name..), so there should be a possibility to do that kind of stuff.

-- 
Arno Rehn
arno at arnorehn.de