<div dir="ltr"><br><br><div class="gmail_quote">2008/9/11 Aaron J. Seigo <span dir="ltr"><<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thursday 11 September 2008, Richard Dale wrote:<br>
> 2008/9/11 Petri Damstén <<a href="mailto:petri.damsten@gmail.com">petri.damsten@gmail.com</a>><br>
><br>
> > Hi,<br>
> ><br>
> > I have been playing with webkit AppletScript. There is a small example<br>
> > (webkit/code/test.html) using plasma dataengines so I have added more<br>
> > functions (init(), engine.connectSource(), etc.) and plasma package<br>
> > support so<br>
> > it looks more like a normal plasma applet.<br>
> ><br>
> > Applets connect to apply & ok to know when user accepted config, but if<br>
> > AppletScript uses configxml there seems to be no way to do that? Maybe<br>
> > configAccepted signal in applet? I guess this could be good for Applets<br>
> > too so<br>
> > they don't have to rely parent to have ok/apply.<br>
><br>
> The biggest problem with using configxml with script engine based applets<br>
> is in this code where it tests 'if (d->script) {' and then leaves early.<br>
<br>
</div>after checking if there is a configXml object, yes.<br>
<div class="Ih2E3d"><br>
> I've no idea what script engine applets would want to do that is different<br>
> from a normal applet as the whole point of configxml is that it is a sort<br>
> of 'fire and forget' api that doesn't actually need any programmer<br>
> intervention to use.<br>
<br>
</div>for widgets that don't use the native configuration system, such as non-native<br>
widgets. we support a couple of those now.</blockquote>Then those wouldn't have any configXml object and this part of the logic would never be entered. I'm afraid I still don't see what the early exit code is doing.<br>
<br>-- Richard<br></div><br></div>