Non-C++ Apps in KDE Main Modules (Was: Guidance in KDE Admin)
On Wednesday 26 March 2008 16:17:53 Leo Savernik wrote: Am Mittwoch, 26. März 2008 schrieb Nicolas Ternisien: All modules need porting to KDE4 (and could make nice showcases for the Python bindings then). Mountconfig would also need porting to Solid (it already uses [...] No other opinion ? If you agree, just say Yes/+1 or No/-1, just to be sure this is something useful, and that will help KDE Admin being more interesting. It looks like Guidance introduces a hard python dependency into KDE. I don't particularly like that. Is there any precedent that justifies a hard runtime python dependency? I think the Release Team should discuss this and provide a policy statement. Do we allow Python/Ruby/C#/Perl etc. apps in the KDE main modules? If so, which ones and why? Oh, and this is also needed for Jonathan's system-config-printer-applet Here are some off-the-cuff thoughts to get the ball rolling: For the language 1) must have a mature, working, kde binding (i.e. there isn't a working perl binding IIRC) 2) must be mature and operational on all our target platforms 3) must be able to provide full translations and internationalizations For the app: 1) must follow the kde look-and-feel, widgets, etc ... ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Non-C++ Apps in KDE Main Modules (Was: Guidance in KDE Admin)
Le Thursday 27 March 2008, Allen Winter a écrit : I think the Release Team should discuss this and provide a policy statement. Do we allow Python/Ruby/C#/Perl etc. apps in the KDE main modules? If so, which ones and why? Oh, and this is also needed for Jonathan's system-config-printer-applet Here are some off-the-cuff thoughts to get the ball rolling: For the language 1) must have a mature, working, kde binding (i.e. there isn't a working perl binding IIRC) 2) must be mature and operational on all our target platforms 3) must be able to provide full translations and internationalizations For the app: 1) must follow the kde look-and-feel, widgets, etc ... Also, per binding we probably a list of do and don't which should be followed by applications using the said binding. For instance, the use of the python dbus bindings has shortcomings (as system-config-printer-applet shown), do we allow apps like that? There's probably similar cases for other bindings. Regards. -- Kévin 'ervin' Ottens, http://ervin.ipsquad.net Ni le maître sans disciple, Ni le disciple sans maître, Ne font reculer l'ignorance. signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Non-C++ Apps in KDE Main Modules (Was: Guidance in KDE Admin)
Kevin Ottens wrote: Also, per binding we probably a list of do and don't which should be followed by applications using the said binding. For instance, the use of the python dbus bindings has shortcomings (as system-config-printer-applet shown), do we allow apps like that? There's probably similar cases for other bindings. That seems to me to be an unmaintainable list. Why not use an easier criteria like app must work reliably as advertised and/or app must not suck? :) -- Rex ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
New Features list?
Hi, IIRC for KDE 3.5 there was an xml file to accumulate the various changes (specially features) that were done. Does something like that exist for KDE 4.1 too? I mean besides the feature planning page on techbase. Where do I find it if it exists? I'd like to add an entry for the Print Shortcuts feature I just comitted. Andreas -- You will be aided greatly by a person whom you thought to be unimportant. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
KDE 4.0.3 packages uploaded (try #1)
Hi, KDE 4.0.3 packages are uploaded to the usual place. it might happen that I have to update kdebase-workspace again, but other than that, this should be it. Please let me know of any issues you find. Thanks, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.0.3 packages uploaded (try #1)
On Thursday 27 March 2008, Dirk Mueller wrote: Please let me know of any issues you find. the translations are still being generated, I hope I can upload them tomorrow morning. Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
