QSA-interest Archive, November 2006
Again: Licensing issues, couple of questions
Message 1 in thread
Hello,
as I was told earlier that it was not possible to access the Qt-API from within
a QSA script, because of licensing issues. I have a couple of questions here,
regarding a commercial license.
First, there's this sentence at http://www.trolltech.com/products/qt/addon/qsa :
"All three groups are empowered by scripting to compose their own
functionality from the functions that the application developer
provides, and from the Qt toolkit itself."
The second part -- "and from the Qt toolkit itself" -- is wrong, isn't it?
Second, how "thick" does a layer need to be so it's not exposing the Qt-Toolkit?
The UtilFactory and InputDialogFactory do nothing but double the methods and
properties of the Qt-Classes, so they basically expose the same interface.
Does this mean I'm forced to duplicate the interfaces of Qt-Classes to
use them in QSA?
Does it make sense to force this by license, where it seems to be encouraged by
philosophy?
I don't think it's too much work to create like 20 or so of these
wrappers, once
you get the hang of it, so it's no big deal if I'm allowed to do so.
But, on the other
hand, I find it really awkward to force this by license.
And why does the InputDialogFactory not include a PushButton, one of the most
basic controls? Any special reason for this?
When I am exposing a normal QDialog, every child-Widget is exposed, too. So
I am exposing the methods and properties, which are original Qt-API.
Is this fine?
As you might've noticed, I'm quite puzzled about QSA. :-)
I'm currently playing with it for an open-source project, but this is
halfway for evaluating
it for our commercial product. The commercial product will use the
scripting language
(maybe QSA) as it's "main" programming language. This means, the
core-functionality
will be provided by the application, but most dialogs and features
will be implemented
using the scripting language.
I'm a bit worried whether this might be troublesome with QSA, since
the scripting
language needs as much access to the application as possible.
Regards,
Daniel Albuschat
--
[ signature omitted ]
Message 2 in thread
Daniel Albuschat wrote:
> Hello,
>
> as I was told earlier that it was not possible to access the Qt-API from
> within
> a QSA script, because of licensing issues. I have a couple of questions
> here,
> regarding a commercial license.
Hi Daniel,
do you refer to license limitations of QSA or of Qt itself? If so, which
license type (commercial, OS) do you refer to?
thanks,
/eno
To unsubscribe - send "unsubscribe" in the subject to qsa-interest-request@xxxxxxxxxxxxx
Message 3 in thread
Daniel Albuschat wrote:
> Hello,
> First, there's this sentence at
> http://www.trolltech.com/products/qt/addon/qsa : "All three groups
> are empowered by scripting to compose their own functionality from
> the functions that the application developer provides, and from the
> Qt toolkit itself."
>
> The second part -- "and from the Qt toolkit itself" -- is wrong, isn't it?
You are free to access the properties, signals and slots of objects
exposed in your application, also QLineEdits, QPushButtons, etc, so this
is correct.
> Second, how "thick" does a layer need to be so it's not exposing the
> Qt-Toolkit?
I've pasted the relevant parts of the license below:
<snip>
9. The license granted in this Agreement for Licensee to add scripting
functionality to his software product(s), distribute the Applications
and the Redistributables (if any) is subject to all of the following
conditions: (i) all copies of the Applications must bear a valid
copyright notice, either Licensee's own or the copyright notice that
appears on the Licensed Software; (ii) Licensee may not remove or
alter any copyright, trademark or other proprietary rights notice
contained in any portion of the Licensed Software; (iii)
Redistributables, if any, shall be licensed to Licensee's customer "as
is"; (iv) Licensee will indemnify and hold Trolltech, its related
companies and its suppliers, harmless from and against any claims or
liabilities arising out of the use, reproduction or distribution of
Applications; (v) Application(s) must be developed using a licensed,
registered copy of the Licensed Software; (vi) Applications must add
primary and substantial functionality to the Licen sed Software; (vii)
development or execution of scripts may not be the Application's
primary purpose; (viii) the scriptable part of the Application may not
give access to more than a small subset of Qt's functionality; (ix)
the scriptable part of the Application may not give direct or indirect
access to construction of classes in the Qt Application Program
Interface; (x) Applications may not compete with the Licensed Software
or with Qt; (xi) Licensee may not use Trolltech's or any of its
suppliers' names, logos, or trademarks to market Application(s),
except to state that Application was developed and/or script-enabled
using the Licensed Software.
If the conditions in subsections (vii), (viii) and/or (ix) above are
not fulfilled, the users of the Application(s) must obtain a valid Qt
license according to Appendix 2, and Appendix 2 has to be distributed
as a part of the Application's license agreement instead of Appendix 1
(as specified above under section 8).
</snip>
> The UtilFactory and InputDialogFactory do nothing but double the
> methods and properties of the Qt-Classes, so they basically expose
> the same interface.
But they are provided by QSA so its not the same.
> When I am exposing a normal QDialog, every child-Widget is exposed, too. So
> I am exposing the methods and properties, which are original Qt-API.
> Is this fine?
yes. The license prohibits construction of QWidgets from script, and
that's the essence of it, so accessing a QDialog is fine.
best regards,
Gunnar
To unsubscribe - send "unsubscribe" in the subject to qsa-interest-request@xxxxxxxxxxxxx
Message 4 in thread
Gunnar Sletta wrote:
> I've pasted the relevant parts of the license below:
>
> <snip>
> ...
> </snip>
>
And again:
is this a license limitations of QSA or of Qt itself? If so, which
license type (commercial, OS) do you refer to?
thanks,
/eno
To unsubscribe - send "unsubscribe" in the subject to qsa-interest-request@xxxxxxxxxxxxx
Message 5 in thread
troll@xxxxxxxxxxxx wrote:
> is this a license limitations of QSA or of Qt itself? If so, which
> license type (commercial, OS) do you refer to?
Hi,
This part is from the the commercial QSA license, regardless of platform.
-
Gunnar
To unsubscribe - send "unsubscribe" in the subject to qsa-interest-request@xxxxxxxxxxxxx
Message 6 in thread
Gunnar Sletta wrote:
> troll@xxxxxxxxxxxx wrote:
>
>> is this a license limitations of QSA or of Qt itself? If so, which
>> license type (commercial, OS) do you refer to?
>
> Hi,
>
> This part is from the the commercial QSA license, regardless of platform.
>
Thank you for the clarification.
/eno
To unsubscribe - send "unsubscribe" in the subject to qsa-interest-request@xxxxxxxxxxxxx
