From kwrite-devel Sun Jan 13 14:28:55 2008 From: Christoph Cullmann Date: Sun, 13 Jan 2008 14:28:55 +0000 To: kwrite-devel Subject: Re: KDE 4 + plans Message-Id: <200801131528.55271.cullmann () babylon2k ! de> X-MARC-Message: https://marc.info/?l=kwrite-devel&m=120023588315926 Am Sonntag 13 Januar 2008 15:18:03 schrieb Andreas Pakulat: > Just thinking out loud, but wouldn't it make more sense to move to > Kross for scripting? It sounds like the better choice, because it simply > isn't bound to a specific scripting language. > > And I saw in dipesh's blog (http://www.kdedevelopers.org/node/3187) that > you can use Kross around QtScript as well as using Kross around kjs to > work with javascript scripts. > > Or maybe, just re-reading that blog, thats not needed anymore as there's > the other way around possible as well as it seems... > > Anyway, just wanted to throw Kross into the game :) I still doubt, that Kross gives us that way of integration we need. We need both calling scripts and scripts calling us. And with calling script, I mean calling functions and object functions out of a evaluated script while giving arbitary parameters. I don't see, that this is that nice in Kross. Perhaps I am wrong here, thought. If you can show me up some example of how to do that, I might reconsider my impression. But on the other side, I don't think supporting multiple languages is a that important goal. JS is easily learned and it will help with the exchange of scripts if people need to stick to one language, like it helped that we had one hl language. cu Christoph -- Christoph Cullmann KDE Developer, Kate Maintainer http://babylon2k.de, cullmann@kde.org _______________________________________________ KWrite-Devel mailing list KWrite-Devel@kde.org https://mail.kde.org/mailman/listinfo/kwrite-devel