Python dependency

[TomasM]

Hello.
I hope this message comes to attention to some compiz-fusion developers.

PLEASE PRETTY PLEASE DROP THE ANNOYING PYTHON DEPENDENCY!

Thank you for listening.

I believe there are thousands of people like me who simply don't wish to install python, pygtk, and all the stuff needed to configure beryl/compiz-fusion. Please think rationally.... Python is very big and many people find it annoying. I understand you may like it, but consider all the people who don't. Thank you.

[RYX]

Hi TomasM!

I understand that everyone thinks differently, but I think the python-dependency is related to the fact that the settings-manager is written in python, which is fairly common for today's desktop-applications. It improves development-speed and maintainability and allows more people to contribute because the language is easier to understand and learn.

May I ask what desktop or system you use that you don't have any python-programs installed? I thought that even the server-based distributions would ship python by default.

Or are you referring to the development-packages? Those, indeed, shouldn't be needed when installing compiz-fusion as a user.

:)

[TomasM]

Thank you very much for your reply.

I'm using Slackware, which is pure KDE-based and thus doesn't contain any GNOME libs (expect of gtk2). There is a python package available for Slackware, yes, but the settings-manager needs more than python, for example pygtk, which requires other libraries, which require even more libraries.

I don't like to install 100MB of python+libraries+something in order to edit a simple configuration file... It simply doesn't make sense :)
But it seems I'll have to live with it.

[RYX]

I can understand that - from a KDE-users' perspective it is quite uncomfortable to install gtk-related packages (it is the same with me the other way round, I don't like installing any kde-* packages). But for now it is the only available settings-tool that is up-to-date, the only alternative would be installing gconf and use the gconf-editor and gconf as backend, but I am quite sure that won't satisfy you that much, either :) ...

Hopefully someone will write a Qt-version of ccsm somewhen to get rid of the gtk-dependency (likely still python, but at least using KDE-ui elements) ... or maybe a Kconfig-plugin for kcontrol-integration? I think beryl had something like that.

EDIT: Ummm ... I forgot about the ini-plugin. You can use it without any backend/frontend - it uses plain text-files in ini-format ... (included in compiz default package).

:)