Status | Assigned | Task | ||
---|---|---|---|---|
Open | None | T11545 Remove Kross | ||
Open | ognarb | T11531 Port KMail account wizard away from Kross | ||
Open | cordlandwehr | T11571 Port Parley away from Kross | ||
Open | alex | T11608 Port KTorrent away from Kross | ||
Open | None | T11613 Port lokalize away from Kross | ||
Open | alex | T11615 Port kdeplasma-addons away from Kross | ||
Resolved | maxrd2 | T12263 Port SubtitleComposer away from Kross |
Comment Actions
Random thoughts:
- Kross was designed to support multiple scripting languages, not just something JS-like. If we only want to support JS in a given application, there's no advantage in using Kross (or any equivalent that makes scripting language-agnostic)
- Python scripting is implemented in Krita in its own way.
Comment Actions
Python scripting is implemented in Krita in its own way.
Yeah, there the python headers & stuff is used directly. IMHO it shows that for complex apps that should support python scripting it is preferred to just use that directly.
Kross was designed to support multiple scripting languages,
It seems like one of those things that never really took off. Especially considering that QtScript is unreliable and critical parts in plasma or kwin have already been ported away from it.