Re: KJSEmbed hits the big time

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: KJSEmbed hits the big time
by rjw on Tuesday 26/Aug/2003, @14:12

Would it be difficult to extend Kjsembed to more than just ECMAscript?
Is the introspection of QT stuff separated from the KJS binding?

IE Can we look forward to python scripts in Koffice? ;-)

Another interesting point would be to expose all these bindings via DCOP for interprocess scripting .. or is this already possible?

Related Links

·   Articles on KDE Office Suite
·   Also by rjw
·   Contact author

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

Re: KJSEmbed hits the big time
by Richard Moore on Wednesday 27/Aug/2003, @02:14

It would certainly be possible to write an equivalent for python, but I have no intention of making kjsembed itself language independent. I think the disadvantages of having a mixture of languages used by different scripts out weighs the pretty minimal gain of supporting more than one. After all, once you support python, why not perl, ruby, scheme etc.

Ian Geiser is working on DCOP support for kjsembed, I'm not 100% sure how much is working right now.

Rich.

[ Reply To This | View ]

Re: KJSEmbed hits the big time
by Ian Reinhart Geiser on Wednesday 27/Aug/2003, @08:36

it can now crash the remote app :)

the dcop command is getting through but something is going wrong communicating variant types. lastly i have started on adding the ability to create dcop interfaces in a kjs script but this code needs to be rethought.

[ Reply To This | View ]

Re: KJSEmbed hits the big time
by Eric Laffoon on Thursday 28/Aug/2003, @16:15

I'm very interested in this to see how it may be useful for Kommander, which provides language neutral dialogs with optional scripting. I do my best to follow it, but if you could keep me advised that would be great. As much as I think KJSEmbed is great and a generally good choice for this I think that being able to shell out from an app and run Kommander with DCOP and the option of using any scripting language is worth having too.

Also congrats to Rich on this and all his hard work.

[ Reply To This | View ]

Re: KJSEmbed hits the big time
by rjw on Friday 29/Aug/2003, @01:34

It seems insane to me to want people to rewrite the scripting language independent parts for any other language they want to use.

The point is, we are going towards a mini-ide being accessible from KOffice. How much of this is js specific?

The other thing is, if we are going toward OOo, and want to import MS office files, why would you want to make it harder to support (shock, horror) VB properly? (Maybe via mono, or something).

[ Reply To This | View ]

Re: KJSEmbed hits the big time
by Norbert on Friday 29/Aug/2003, @01:52

Yes, python scripts in KOffice are possible. I already have a "Prove-Of-Concept" plugin for KSpread on my hard disc, but it is outdated and doesn't work with 1.3. Maybe I will look into this again, once I get back to develop on KSpread in mid of September.

[ Reply To This | View ]

Re: KJSEmbed hits the big time
by panzi on Wednesday 07/Jun/2006, @00:51

If there would be a poll, I would vote for python. :)
JavaScript is nice, but it's OOP features seem a bit hackish.
I like python and python is very commonly used.

[ Reply To This | View ]

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


		"Feature freeze means that everyone has a bad feeling when they change something, almost nothing more." -- Stephan Kulow
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.