[Kde-bindings] KDevelop ruby support

[Navindra Umanee]

Richard Dale <Richard_Dale at tipitina.demon.co.uk> wrote:
> Well that seems a bit ugly to me. I prefer the idea of tarring up the 
> $KDEDIR/share/apps/<appname> directory with everything in it instead. That's 
> why I'd like the script in the bin directory that starts the app to be as 
> simple as possible and autogenerated by the install. 

Hmmm...  why tar?  Why not handle it like a normal KDE app with
KDEDIRS and so on?

> Another possibility is for a C++ top level stub to be generated as
> part of the install which would start the ruby app - much the same
> as we already have with krubyinit. 

This seems to sacrifice the portability and convenience of just having
to distribute the ruby script plus data files like icons.  krubyinit
really doesn't seem to be necessary and desirable.

> On Mac OS X you always need to have a top level compiled stub with
> scripting languages for instance. A C++ stub would be needed for a
> KPart written in ruby, so it might be more uniform to do exactly the
> same thing for a KDE app.

Didn't know this.  Currently in QtRuby/Korundum, there's a way (and
need) to generate C++ stubs?

Cheers,
Navin.