On 2 August 2016 at 17:17, Pau Garcia i Quiles <pgqui...@elpauer.org> wrote: > > > On Sat, Jul 2, 2016 at 8:37 PM, Dag <dand...@get2net.dk> wrote: > >> >> >> Kross/python: Scripting is used for some functionallity so python support >> is needed. (or else convert to javascript) >> > > I would really prefer JavaScript (QJsEngine), as Kross does not work on > Windows.
Yes, QJsEngine is what we plan (pun!) to use for KReport exclusively for official extension APIs and automation. Not this year but always good to know... Python is just insecure for public scripts. And since KReport seems to be also used by Plan, there's some opportunity to use a common scripting stack. For best experience maybe even a single JS engine instance for various tasks (Plan-specific, KReport-specific, etc.) in a single app. > Also, if a Plan user wants to implement some functionality, JavaScript would > looks less intimidating. After all, Plan users are Project Managers, not > developers. +1 -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
