<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">---------- Messaggio inoltrato ----------<br>From: "Aaron J. Seigo" <<a href="mailto:aseigo@kde.org" target="_blank">aseigo@kde.org</a>><br>
To: <a href="mailto:plasma-devel@kde.org" target="_blank">plasma-devel@kde.org</a><br>Date: Tue, 2 Feb 2010 13:31:02 -0800<br>Subject: Re: Subject: Re: plasmate alpha1 release<br>On February 2, 2010, Diego Casella ([Po]lentino) wrote:<br>
> We need to add a dataEngine and runner templates in Javascript, as well a<br>
> runner template written in ruby but, up to now, i didn't find any example<br>
> in order to write good templates fot that. Hints ?<br>
<br>
the javascript DataEngine and Runner APIs are not documented. unless someone<br>
else get to it, they won't be before 4.5 is out. which is ok, since those<br>
Javascript APIs have known (at least to me ;) deficiencies in 4.4. those are<br>
really more 4.5 targets.<br></blockquote><div><br>Ok, so should we disable the js ( and ruby ) radio button when selecting a runner or dataEgine project, until we get an improved API ?<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>
but i can quite easily provide templates for both, and really should be adding<br>
such things to kdeexamples anyways.<br></blockquote><div><br>Good :) <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> And theme support is still unavailable, in this current state.<br>
<br>
theme support would be fairly easy to add, as far as packaging goes, but it<br>
will still require an external tool such as Inkscape for the forseeable<br>
future. so it will never be "perfect" for theming, it really would be just<br>
more of a packaging and previewing tool.</blockquote><div> </div><div>Ok, then something like "create the theme directory hierarchy" -> "drag and drop svgs and color scheme" -> "preview" -> "publish" should be fine :)<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;">i wonder if a purpose-built tool just<br>
for making theme packages wouldn't be better. what do you think of dropping<br>
themes from the target use cases?<br></blockquote><div><br>It's all the same for me. Yuen Hoe, Shantanu, what do you think ? <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>
> Furthermore, IMO, we should make PlasMate project-centric, for a couple of<br>
<br>
agreed<br>
<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 Development Frameworks<br></blockquote></div><br>