<br><br><div class="gmail_quote">2008/11/3 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 Monday 03 November 2008, Simon Edwards wrote:<br>
> Helloooo,<br>
><br>
> Aaron J. Seigo wrote:<br>
> > i'd like to move libplasma over to kdelibs on Nov 3rd. it'll be a fair<br>
> > amount of work, and i'll announce here when i've started so other people<br>
> > don't get caught with local changes to libplasma.<br>
> ><br>
> > so this is the "last call" for binary incompatible API changes ... time<br>
> > to speak up or forever hold your peace, where "forever" is defined as<br>
> > "until kde 5"<br>
><br>
> My only concern is that the script engine APIs seem to be missing a<br>
> number of methods which match the C++ API. For example, dataenginescript<br>
> doesn't have a counter part to "QStringList DataEngine::sources()" which<br>
> AFAIK makes it not possible to implement source listing functionality in<br>
> a scripted data engine.<br>
<br>
</div>i sat down for five minutes and added the two most glaring missing things from<br>
DataEngineScript.<br>
<br>
in the time it took you to write that email, you could have done the same.<br>
<div class="Ih2E3d"><br>
> (Sorry, I don't have time right now to give more detail. Should the<br>
> scripting APIs be part of the BC API?<br>
<br>
</div>yes<br>
<br>
> can that be delayed?)<br>
<br>
it's all be sitting there for nearly a year now and i get ~zero feedback from<br>
those who might use it. i honestly don't see that improving and as such don't<br>
see that as a reason to hold things up.<br>
<br>
ok, that's not quite true. i do see that improving when people start taking<br>
scripting seriously.<br>
<br>
i'm very surprised that the work going into scriptengines has mostly been in<br>
the form of writing bindings with little to no care as to what is actually in<br>
libplasma itself. that's a very poor model for creating scripting support for<br>
applications, imo.<br>
<br>
i had the bulk of feedback from the GoogleGadgets and Edje implementors, which<br>
is fasincating.</blockquote><div>Well I think what Simon and myself are doing is different from what the GoogleGadgets and Edje implementors were doing. <br><br>For better or worse we don't want to design a new api because we think the C++ api is perfectly fine when translated method for method, and class for class, to other more dynamic languages. I don't personally use the term 'scripting language' for this, because I don't see this to be anything to do with scripting. To me scripting is all about driving a C++ application with a lightweight language like Lua. <br>
<br>I see our work consisting of making the api that the RAD language programmers sees as similar to the api that a C++ programmer sees. And although I am perfectly happy with the results for the Ruby and C# script engine apis, I really wish we had some users actually doing things with the bindings to get more feedback about any changes before everything is frozen.<br>
<br>One little thing that would be nice, is to be able to specify a different name for the main file in a plasmoid so that we can have main.rb, main.py etc without needing to have a new package structure plugin just to be able to do that.<br>
<br>-- Richard<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
in any case, take the BC requirements as a call to action and look over those<br>
classes so we can get them into the order you'd be comfortable with.<br>
<div><div></div><div class="Wj3C7c"><br>
--<br>
Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Software<br>
<br>
</div></div><br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
<br></blockquote></div><br>