Re: Kross and QtScript

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Kross and QtScript
by Sebastian Sauer on Saturday 13/Jan/2007, @00:33

Well, IM(H)O merging is maybe not the best idea since Kjs+KjsEmbed and QtScript are just different implementations. Merging them is like to suggest to merge Python with Ruby cause you like both and cause they are very similar (OO, dynamic, written in C, scripting languages, etc.). Anyway, that's only my personal point of view and everybody who believes it's possible to merge them (KjsEmbed with QtScript or maybe even Ruby with Python) and likes to start working on it, is free to do so and it wouldn't be the first time that an unique vision becomes reality within the KDE-project :)

Related Links

·   Articles on KDE Public Relations and Marketing
·   Also by Sebastian Sauer
·   Contact author

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

Re: Kross and QtScript
by Sebastian Sauer on Saturday 13/Jan/2007, @00:43

btw, to close the circle the title of this thread was dealing with; for sure there is nothing what would prevent us to also add QtScript-support to Kross which would then support both js-implementations. Nothing except that myself does not like JavaScript at all and would like to see Java-support first much more ;)

[ Reply To This | View ]

Re: Kross and QtScript
by MM on Tuesday 16/Jan/2007, @05:12

Thanks

[ Reply To This | View ]

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


		"Never miss an opportunity to throw away code." -- Guillaume Laurent
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.