[Kde-bindings] KDevelop ruby support

[Richard Dale]

On Sunday 24 October 2004 16:37, Navindra Umanee wrote:
> Richard Dale <Richard_Dale at tipitina.demon.co.uk> wrote:
> > 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.
If there is a top level C++ stub, combined with the ruby code as a resource, 
along with the normals icons, .desktop, translation po files etc, it just 
looks like a normal KDE app from a packaging point of view. It just happens 
to have more of the program logic written in ruby. So it means you can use 
the standard KDE configuration and packaging tools. krubyinit is only six 
lines or so - the top level only needs that much code.

> > 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?
Yes, for a KPart because you need to start the ruby interpreter within the 
current process, not by exec'ing a sub-process.

-- Richard