Deluge Forum

jdhore wrote:I'd say the best option is to port Deluge to C...I know that's prolly never going to happen, but if it did, i'd be happy to build a Windows version (yes, Python will work on Windows, but i hate python and python sucks even more than usual on non-*nix platforms) and probably really help out with development of the *nix version. Also, coding it in C would prolly make the code smaller, lighter and faster. And, on top of that, you'd just have to port the calls to *nix apps and compile with MSVC and you're done.

markybob wrote:

jdhore wrote:I'd say the best option is to port Deluge to C...I know that's prolly never going to happen, but if it did, i'd be happy to build a Windows version (yes, Python will work on Windows, but i hate python and python sucks even more than usual on non-*nix platforms) and probably really help out with development of the *nix version. Also, coding it in C would prolly make the code smaller, lighter and faster. And, on top of that, you'd just have to port the calls to *nix apps and compile with MSVC and you're done.

that's utterly and totally irrelevant. we're having problems with dbus-glib, not deluge or python. furthermore, dbus-glib is c, and would *still* be required if deluge was pure c

johnnyg wrote:hmm not sure what happened to your original post markybob...
so you have narrowed it down to dbus-glib?
on a side note, converting it to C would actually make the code ALOT bigger, sure it would run faster and even possibly "lighter" but I doubt it would be worth it.