[Kexi-devel] Qt Script possibly not the best tech for Kexi scripting
piggz1 at gmail.com
Mon Feb 16 12:19:36 UTC 2015
For kexi reports I'd like to try out qjsengine. It looks closest to qtscript, which is the only Kross engine I ever really tested.
Js is easy to pickup and powerful enough for our uses I think.
Sent from my BlackBerry 10 smartphone.
From: Jaroslaw Staniek
Sent: Monday, 16 February 2015 12:09 PM
To: Robert Leleu
Reply To: Calligra Suite developers and users mailing list
Cc: Calligra Suite developers and users mailing list; kexi-devel at kde.org
Subject: Re: [Kexi-devel] Qt Script possibly not the best tech for Kexi scripting
On 16 February 2015 at 12:56, Robert Leleu <robert.jean.leleu at wanadoo.fr> wrote:
> I'd rather use Python which seems actively developed, and seems to be the
> most easily usable by non-programmer people (my experience)
Knowing Python, it's my personal choice too. However too bad it's
official: Due to its architecture Python can't offer sandbox for
security (google for python sandbox). Users of Kexi apps would gain
practically full access to your computer account.
So we don't want another VBA with useless questions users can't answer
properly without an audit "Do you want to enable scripts in this
file?". Rather means for extensions like in Firefox or Chrome.
Anyone with enough resources is free to add python support though, it
just won't be the type of scripting we're talking about. It would be
extension system for trusted environments.
and is maintained as a pilliar of Qt Quick 2.
regards, Jaroslaw Staniek
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
: A graphic art and office suite - http://calligra.org
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
calligra-devel mailing list
calligra-devel at kde.org
More information about the Kexi-devel