Using scripting languages for KDE4 main modules

[Boudewijn Rempt]

On Friday 29 September 2006 16:10, Leo Savernik wrote:
> Am Donnerstag, 28. September 2006 16:07 schrieb Albert Astals Cid:
> > Could we get a clear "Yes"?
>
> Could we also determine that at least a "usable basic distribution" of KDE
> stays buildable and usable without any need for language bindings other
> than C/C++/kjsembed?

Why? What's the the good of that? With the list you give below you're not 
going to notice the extra megabytes a Python interpreter + bindings bring 
with them. 

> With "usable basic distribution" I think of a KDE installation consisting
> of kdelibs, kdepimlib, konqueror, kcontrol, kate, kdevelop, kontact, kpdf
> (whatever it'll be called in KDE4), kview/kuickshow (whatever the common
> successor will be called), kopete, koffice, and other applications that
> make a KDE desktop useful.

In any case, while not absolutely depending on it, KOffice makes good use of 
Python and Ruby already.

-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060929/58803775/attachment.sig>