Patch: Using kpart's KJS::Interpreter (was Re: XML, XSL, XSLT, XPath support?)

[Koos Vriezen]

On Tue, Apr 12, 2005 at 10:29:55PM +0200, Christoph Cullmann wrote:
> On Tuesday 12 April 2005 21:36, Koos Vriezen wrote:
> > I leave the usefulness question to Leo :-). But in general, that's
> > exactly where it is used for. GUI elements are the images in html. When
> > clicked they invoke javascript actions (with onClick or href
> > attributes). And that will call the javascript bindings the plugin has.
> > Eg. for an embedded media player, it's typical the play/stop actions.
> > For an editor like kate, it might be syntax highlighting (ie. allowing
> > the user to change the highlighting scheme), column setting etc.
> I don't think this will work with our use of kjs, as we keep only one global 
> interpreter for all documents, and you can't do anything in it, as the 
> document/view object won't point to right doc/view at any time beside the 
> explicite calls in the inside of the part, therefor don't think this has any 
> use for us.

Can you elaborate on this, eg suppose a kate object is embedded in khtml
and it has the globalObject of kate. In html, the path to this object is
'document.applets[0]'. Now what would it take to call the 'setText'
function, ie. in 'document.applets[0].XXXX.setText("foo")' what is XXX?

Koos