|
AUG
17
2003
|
Creation of KParts, opaque QVariant support, void * support...Lots of new features in KJSEmbed over the last few days. I got a new factory method implemented that lets you create read-only parts! This has let me knock together an example that uses KHTMLPart to provide a web browser - total code 22 lines (including blanks and comments). There is also now support for any QVariant type - even those that aren't explicitly suported.
|
 |
Comments
So what you are saying is...
We can now write full KDE applications in javascript? Is this a security issue? I mean can I just click include a .js file on a webpage and have it create a KDE app? This sounds like more of a danger than usefulness.
-jeffy
No problem
We can now write full KDE applications in javascript?
No, but access a little bit more.
I mean can I just click include a .js file on a webpage and have it create a KDE app?
No, of course not. That would be pretty stupid :)
no
We are close, we are basicly missing KConfig and DCOP. Im working on dcop now, and hope to shore that up in the next two weeks.
As for secureity, KJSEmbed is different from KJS. It also has its own secureity manager. Lastly KJSEmbed can extend KDE apps... Already you can write konqi plugins with it, and I talked to rich today about a kicker applet. So really in the next few weeks you will be able to write real KDE applications, Konqi plugins, Kicker applets and God knows what else. But no this still wont cause any more of a secureity hole than the current C++ methods of apps.