<br><br><div class="gmail_quote">2008/6/23 Aaron J. Seigo <<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>>:<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 23 June 2008, Janz wrote:<br>
> give any hint) and couldn't find about how to get started with a non-C++<br>
> plasmoid. I saw a few examples (tiger JS plasmoid and all of those in<br>
> script/ on svn playground) but I can't install them under KDE 4.1 beta<br>
> Kubuntu package<br>
<br>
</div>we actually have a plasmapkg application in kdebase now that can install such<br>
packages.</blockquote><div>I would like to be able to use the plasapkg packaging mechanism for non-C++ languages such as C# which don't use the ScriptEngine api. C# is not a scripting language and I think people will expect either the C++ api or nothing - I really can't see how it would make sense to go through the ScriptEngine. There will be the same issue if we have Java QtJambi bindings I think. I have exchanged private emails with Aaron about whether or not Ruby should use the ScriptEngine, and I still am not keen on using it as it currently stands.<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><div class="Ih2E3d">
> So, anyway, what I really need to know is: what do I need to get a 4.1<br>
> compliant (packaging and stuff else) working JS plasmoid (let's say Tiger,<br>
> to get a small one - and do we have examples of 4.1 compliant JS<br>
> plasmoids)?<br>
<br>
</div>not particularly. we have the QScript engine in kdebase, but there is a new<br>
and much better one in the works in playground. unfortunatately at this point<br>
it won't make it in until 4.2 =(<br>
<br>
there's also a nice webkit one in payground now that uses Jolie (!)<br>
<div class="Ih2E3d"><br>
> Also, do any of you know about the same for a Python one?<br>
<br>
</div>all the python support is in playground still.<br>
<br>
sort of how we've re-focussed efforts on artwork, we also MUST get the<br>
scripting support completed, shipping and documented in 4.2.</blockquote><div> I personally would prefer to get something going for 4.1 because I don't think we can know what people want - which languages, what skill level and so on - until we start iterating with something and get community feedback. For instance, I don't know if the current group of KDE Ruby programmers grew to 10 or 100 times its current size how their requirements might change. All I know is that the current group are all 100% 'ninja' to use Aaron's terminology and would expect to be able to use the full C++ api. So my plan for KDE 4.1 is to try and provide both a ScriptEngine based api, and the full C++ api (with or without proper plasma packaging), and get something moving. <br>
<br>In a couple of weeks we are having a hacker sprint in Berlin with a lot of the bindings guys (python, ruby, c# and php) and Kross too, and I would be very keen on discussing there what to do about Plasma bindings for KDE 4.1.<br>
<br>-- Richard<br></div></div><br>