|
1
by Michał Zając
Import upstream version 4.6.90+repack |
1 |
TODO to get scripting into Parley |
2 |
=============================
|
|
3 |
||
4 |
* Make KPluginSelector save its settings (which plugin is enabled/disabled) |
|
5 |
* On Parley startup load the enabled scripts |
|
6 |
* Connect with signal/slot the script and the editing of vocabulary |
|
7 |
* Expose some functions that will allow the script to add translations |
|
8 |
* Make the translations visible to the user in a nice way. |
|
9 |
||
10 |
* Read up on kross |
|
11 |
||
12 |
* Define which part of the api will be exposed for scripts |
|
13 |
- Do we need an extra layer or can it be integrated directly? |
|
14 |
- Can we pass around complex stuff like KEduVocExpression or does that need a wrapper? |
|
15 |
- How can scripts fill out for example the conjugations for a verb? |
|
16 |
||
17 |
* Integrate with KNewStuff2 |
|
18 |
||
19 |
* How are scripts/plugins recognized? Probably using .desktop files. Investigate how other apps are doing this. |
|
20 |
||
21 |
* Write some example scripts to validate the implementation |
|
22 |
- Possible scripts: |
|
23 |
+ dict.someserver |
|
24 |
+ conjugations for spanish (http://turingmachine.org/compjugador/) |
|
25 |
+ script: fetchTranslation("word") |
|
26 |
||
27 |
||
28 |
* Maybe try to use python and ruby to check that both are working? |
|
29 |
- Frederik volunteers for one py script :) |
|
30 |
||
31 |
||
32 |
* Scripts can make use of kde bindings, so they can have a gui. If we deliver some by default, they could even be translated. If there is still time, look into that. |
|
33 |
||
34 |
* Scripts (for discussion) |
|
35 |
+ define script api |
|
36 |
+ scripts adding actions to menu |
|
37 |
+ script manager (amarok 1.4.x from distro packages) |
|
38 |