<div dir="ltr"><br><br>
<div class="gmail_quote">2010/2/26 Khudyakov Alexey <span dir="ltr"><<a href="mailto:alexey.skladnoy@gmail.com">alexey.skladnoy@gmail.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">÷ ÓÏÏÂÝÅÎÉÉ ÏÔ 26 ÆÅ×ÒÁÌÑ 2010 01:22:15 Yiannis Belias ÎÁÐÉÓÁÌ:<br>
<div class="im"><br>> > Scripts are using D-bus to communicate with kstars. Therefore I propose<br>> > to clean up current D-bus interface and document it. Latter part is most<br>> > important. It's not possible to write scripts when interface is unknown.<br>
><br>> Well, it seems the script builder acts like a kind of documentation system,<br>> like the "function wizard" in open office.<br>><br></div>Yes it does but it is kind of. But it's royal pain to maintain in actual<br>
state. I think it should be replaced with normal documentation. Chapter in<br>kstars handbook devoted to scripting would be nice. Any other suggestions?<br>
<div class="im"><br>> > After that both script builder should and code for script execution<br>> > should be removed. They are maintenance burden.<br>> ><br>> > Your opinions on the matter?<br>><br>
> Since I'm interested in scripting with kstars, I did a small search about<br>> šKDE scripting. At Amarok for example, they have kept a subset of their old<br>> šd-bus scripting and added a javascript api based on QtScript framework[0].<br>
> šOthers seem to use QtScript too, like plasma for writing plasmoids and<br>> šcontrolling the desktop. On the other hand, there is smoke(seems to export<br>> šmuch of kde api) and kross(not for stand alone scripts?) that support many<br>
> šlanguages, like python and ruby.<br>><br>> Out of curiosity, I followed the QT scripting guide[1], and made an example<br>> šof how one could use a supposedly existing kstars javascript api to make a<br>> šsimple calculation. I'm attaching the files to see for yourselves.<br>
><br></div>There are two major non-contraditory options. First one is d-bus for<br>controlling application from outside. I think it's good to have ability<br><br>Another option is to use QtScript/Kross to extend functionality of<br>
applications. Both of these technologies provide way to embed another high-<br>level language.<br><br>Probably right option is to clean up d-bus first.<br>
<div class="im"><br>> Also, I've been looking at the kstars/INDI docs and there are references[2]<br>> šabout INDI scripts for controlling devices, even with the help of script<br>> šbuilder[3].<br>> I have not been able to find a reference of how a script like that could<br>
> šlook like, though ... Just some commented out INDY functions in kstars.h<br>><br></div>It is supposed to work but:<br><br>Excerpt from kstars.h<br>> š š// TODO INDI Scripting to be supported in KDE 4.1<br>> š š#if 0<br>
As you can see scripting got a lot of attention. I hope it will work in 4.5.<br>_______________________________________________<br>Kstars-devel mailing list<br><a href="mailto:Kstars-devel@kde.org">Kstars-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kstars-devel" target="_blank">https://mail.kde.org/mailman/listinfo/kstars-devel</a><br></blockquote></div><br>Bonjour , je ne comprends pas l'anglaisš mais le Francais<br>
š<br>Salutations</div>