Automating Your Desktop with KJSEmbed
Submitted by Ian Reinhart Geiser 2004-04-19 KDE 5 Comments
I’m a C# developer (.net framework) and I’m in the process of learning C/C++ because I’d like to develop apps on linux.
I’m just curious what the speed is like compared to C++ QT apps?
On a decent machine (say 800MHz+) with a reasonable amount of ram would you notice a speed difference compared to a natively compiled app (i.e. fat client w/ database backend)?
I guess I should clarify: in your example above (fat client w/ database backend), if you are using the built-in KDE-database bindings, and keeping most of your business logic in the database, then I think your performance hit would be fairly minimal. I guess app start-up time would be slower (the first time, until it is cached), but otherwise, the real load is being handled by the database and the Qt native components.
Your answers are pretty true for kjsembed too, though the JS itself is reasonably quick. For example there is no problem handling mouse and paint events from scripts.
BTW Since you’re interested in XUL, you might light Kaxul which uses kjsembed to allow you to run XUL code with a native KDE gui.
Thanks for the tip! I’ll check it out.
While I have you here, I’d like to ask another question or two: Is the JS engine in KJSEmbed based on the Mozilla JS interpreter? Is it a complete implementation of JS 1.5?