Re: What Smoke is (Re: shameless cheerleading.)

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: What Smoke is (Re: shameless cheerleading.)
by Ashley Winters on Tuesday 17/Sep/2002, @12:37

David is right on the money. In fact, Smoke contains two different types of information.

First, it has a wrapper around every function in every class -- ala. SIP for PyQt. Static languages (Java, C#, etc) can use that part of PerlQt just like they would use SIP.

In addition to that, SMOKE contains meta-information... a sort of reflective introspection of the Qt library allowing queries of what functions are available and their arguments and return-types. The PerlQt binding takes full advantage of that information by providing do-what-I-mean function calling and automagic type coercion and multimethod dispatch. It also helps me make up nonsensical buzzwords to make me look smart.

Scripting languages can take advantage of that added information to provide neato stuff. Neato stuff is the best.

In conclusion (my writing teacher loves when I use that), SMOKE is the best thing since libc. Thank you. Please send your checks to me, since I'm homeless and can't work on PerlQt except to respond to e-mails from the local library. Feel free to Cc me on your Smoke questions to the PerlQt mailing-list if you're patient enough to wait a week for my response. Sadly, my Yahoo account would croak if I subscribed to the PerlQt mailing-list but only checked it once a week.

Sorry to dump it all on you Germain, but you've done a great job. Congratulations!

Related Links

·   Articles on Developer
·   Also by Ashley Winters
·   Contact author

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

Re: What Smoke is (Re: shameless cheerleading.)
by Adam Treat on Tuesday 17/Sep/2002, @16:24

Wow! Looks like you guys have done some *amazing* work with SMOKE and PerlQt. Congratulations!

Regarding the usefullness of smoke for the C# bindings... I'm not sure this is the way to go. We are in the midst of a major refactor of Qt# with the goal to replace libqtc altogether. We've written a custom parser in C# that takes the Qt headers and outputs an xml representation of them. We will then feed this xml into our generator. We are going to replace libqtc with libqtsharp which will contain all the constructors for the QObjects and then we'll call libqt directly by mangling our function names. The idea is to reduce our dependencies and tailor our glue code to meet the specific needs of the CLR.

Anyways, Nice Work: Ashley, David, Everyone

Adam Treat

[ Reply To This | View ]

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


		"I ride my bicycle." -- Michael Häckel
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.