Re: Mono

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Mono
by Richard Dale on Sunday 17/Feb/2008, @11:11

Yes, I pretty much agree with you here, and you are quite correct when you say "next step easier is a scripting language", such as Python or Ruby. What is the value added by using QtJambi or Qyoto instead of the C++ api?

However, from my point of view, getting C# bindings working with Qt/KDE is a very interesting technical challenge. Currently Arno Rehn is doing great stuff with that. He is making the Smoke library that is used by the Ruby/C# and PHP bindings more modular. That will make it much easier to create Smoke libraries to cover various KDE plugin apis such as Plasma or Akonadi.

The Qyoto/Qt C# api is quite a bit different from the QtJambi one, although C# and Java are quite closely related. Slot/signals are done quite differently in Qyoto compared with QtJambi, and in Qyoto Qt properties are mapped directly onto C# ones. So if you are a Free Software hacker, the differences are larger than they first appear.

The is only a GPL version of Qyoto available, whereas QtJambi is dual licensed - the target market is very different.

Qyoto/Kimono should be able to cover important KDE apis be KDE 4.1, but there is no work being done on a KDE version of QtJambi as far as I know.

Related Links

·   Articles on Developer
·   Also by Richard Dale
·   Contact author

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


		"When I'm not hacking on a computer, I like to play the guitar and get drunk. Sometimes both at once." -- Richard J. Moore
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.