Re: What bindings in general need is:

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: What bindings in general need is:
by Evan "JabberWokky" E. on Monday 20/Sep/2004, @05:05

I *know* I have read of such a project very recently. Scribus, perhaps?

It is rare, however.

Related Links

·   Articles on Developer
·   Also by Evan "JabberWokky" E.
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: What bindings in general need is:
by Henning on Monday 20/Sep/2004, @06:37

Only the first versions of Scribus were written in PyQt.
But the text rendering was to slow and it was rewritten in C++.
Perhaps it would have been better to replace only certain
widgets with C++.
But now there is still a possibility for scripting Scribus with Python

[ Reply To This | View ]

Re: What bindings in general need is:
by Roberto Alsina on Monday 20/Sep/2004, @06:52

If only Pyrex worked well with C++ you could write those pieces in almost-python and get almost-C++ speeds :-P

[ Reply To This | View ]

Re: What bindings in general need is:
by Humberto Massa on Monday 20/Sep/2004, @11:44

Why doesn't pyrex work well with c++? Why does it not work with PyKDE/PyQt?

[ Reply To This | View ]

Re: What bindings in general need is:
by Roberto Alsina on Monday 20/Sep/2004, @11:58

Quoting the Pyrex docs:

-----

Future Plans

C++ support. This could be a very big can of worms - careful thought required before going there.

------

And it doesn't work well with PyQt/PyKDE because there is no simple way to pass a C++ object to a Pyrex extension and use it from Pyrex.

Sure, you could use Pyrex for code that only needs to use integers and floats, but how much code like that is in your average Qt application?

[ Reply To This | View ]

Re: What bindings in general need is:
by Phil Thompson on Monday 20/Sep/2004, @10:23

Replacing certain widgets with C++ versions would have been my suggestion. This is similar to what was done with eric (the PyQt IDE). The quickest way to add a good programmer's editor was to port Scintilla to Qt, produce Python bindings for it, and write the rest of the IDE in Python.

Another common approach of commercial users when they want to revamp an existing C++ application is to isolate the core functionality in a library (if it's not already structured as such), produce Python bindings for it, and rewrite everything else (particularly the GUI) using PyQt.

[ Reply To This | View ]

Re: What bindings in general need is:
by Philippe Fremy on Monday 20/Sep/2004, @13:24

Yep. It is exactly what I am doing at the moment for my job. We have a little C++ library that does some of the irreplacable system code. We wrap it with boost and use python everywhere else. It is a _very_ productive language. I also love the way I can quickly write complicated tests or the way I can make arguments expclicit:

Compare:
acs = generate_acs( ACS_ALWAYS, (ACS_AUTH, KEY_1), ACS_NEVER, ACS_NEVER )
CreateFile( 300, 0x3F00, acs )

with:
acs = generate_acs( read=ACS_ALWAYS, write=(ACS_AUTH, KEY_1),delete=ACS_NEVER )
CreateFile( size=300, id=0x3F00, access=acs )

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"The trolls are only human and make mistakes too." -- Charles Samuels
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.