Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (7)
to General by teroyk - 8 hrs, 13 mins ago - more...
|
2009-10-27
, 09:48
|
|
Posts: 37 |
Thanked: 6 times |
Joined on Oct 2009
@ UK
|
#2
|
You need to pay that if you don't want to comply with the LGPL. Y ou can still have a proprietry application using the LGPL.
http://qt.nokia.com/products/licensing
http://qt.nokia.com/products/licensing
| The Following User Says Thank You to matikjn For This Useful Post: | ||
|
|
2009-10-27
, 20:23
|
|
Posts: 31 |
Thanked: 8 times |
Joined on Jan 2008
|
#3
|
Hi,
Thanks for the reply. I missed that option.
So, from reviewing the website once more, and also consulting wikipedia on the terms of LPGL, am I correct in thinking that under the terms of this license:
i) I can produce a standalone 'executable'/installable file which is not open source, but dynamically links with qt libraries at runtime.
ii) The qt runtime libraries are already present on the maemo device/N900?
iii) Statically linking with qt libraries is not permitted if my code is closed source.
iv) I presumably cannot in anyway ship modified versions of the qt libraries. However, inheritance of the provided qt classes is permitted.
I wish these questions were addressed a little more clearly and obviously on the website - perhaps they are and I have again missed them.
Thanks for any help in clearing up these issues.
Regards,
spann
Last edited by spann; 2009-10-27 at 20:42.
Thanks for the reply. I missed that option.
So, from reviewing the website once more, and also consulting wikipedia on the terms of LPGL, am I correct in thinking that under the terms of this license:
i) I can produce a standalone 'executable'/installable file which is not open source, but dynamically links with qt libraries at runtime.
ii) The qt runtime libraries are already present on the maemo device/N900?
iii) Statically linking with qt libraries is not permitted if my code is closed source.
iv) I presumably cannot in anyway ship modified versions of the qt libraries. However, inheritance of the provided qt classes is permitted.
I wish these questions were addressed a little more clearly and obviously on the website - perhaps they are and I have again missed them.
Thanks for any help in clearing up these issues.
Regards,
spann
Last edited by spann; 2009-10-27 at 20:42.
|
|
2009-10-27
, 20:40
|
|
Posts: 61 |
Thanked: 18 times |
Joined on Oct 2009
|
#4
|
@spann - Just a thought, but you might want to reconsider how you engage with the Open Source community. There are ways to monetize an open source application. Going closed source is not exactly embracing the 'spirit' of openness that Maemo/linux/OSS represents - this isn't an Apple dev platform 
|
|
2009-10-27
, 20:43
|
|
Posts: 1,746 |
Thanked: 2,100 times |
Joined on Sep 2009
|
#5
|
i) I can produce a standalone 'executable'/installable file which is not open source, but dynamically links with qt libraries at runtime.
ii) The qt runtime libraries are already present on the maemo device/N900?
iii) Statically linking with qt libraries is not permitted if my code is closed source.
iv) I presumably cannot in anyway ship modified versions of the qt libraries.
However, inheritance of the provided qt classes is permitted.
Also, if possible, consider what Jed said
|
|
2009-10-27
, 21:36
|
|
Posts: 37 |
Thanked: 6 times |
Joined on Oct 2009
@ UK
|
#6
|
Originally Posted by spann
I'm not 100% sure if the official QT package will be included as default - QT 4.6 was only ported to maemo earlier this month, and GTK (Hildon) is the native toolkit for maemo 5.
ii) The qt runtime libraries are already present on the maemo device/N900?
Even if not installed it will be easy for users to install either the 4.5 community port or 4.6 port when it is available (Q1 2010 apparently).
This thread might be useful...
http://talk.maemo.org/showthread.php?t=33220
|
|
2009-10-27
, 22:00
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#7
|
Originally Posted by matikjn
The Summit firmware already included the 'community supported' Qt 4.5.3
I'm not 100% sure if the official QT package will be included as default - QT 4.6 was only ported to maemo earlier this month, and GTK (Hildon) is the native toolkit for maemo 5.
| The Following User Says Thank You to attila77 For This Useful Post: | ||
|
|
2009-10-27
, 22:13
|
|
Posts: 37 |
Thanked: 6 times |
Joined on Oct 2009
@ UK
|
#8
|
Originally Posted by attila77
Thanks, I hadn't noticed that before
The Summit firmware already included the 'community supported' Qt 4.5.3
|
|
2009-10-28
, 00:10
|
|
Posts: 61 |
Thanked: 43 times |
Joined on Aug 2008
|
#9
|
Originally Posted by Jed
I would like to hear more about this.
@spann - Just a thought, but you might want to reconsider how you engage with the Open Source community. There are ways to monetize an open source application. Going closed source is not exactly embracing the 'spirit' of openness that Maemo/linux/OSS represents - this isn't an Apple dev platform
If you got more to say please start new conversation at appropriate area and we go on from there.
P.s
http://smellslikedonkey.com/wordpress/?page_id=274
|
|
2009-10-28
, 00:32
|
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#10
|
I can guarantee you most people are not going know how to obtain the source and compile even if was available. Heck I've been using Linux for slightly more than a year and I still have troubles when doing it. Now if someone compiled it then released it for free in compiled formthat might be problematic. But then again so would someone just breaking the DRM on your app and distributing it.
__________________
Originally Posted by ysss
They're maemo and MeeGo...
"Meamo!" sounds like what Zorro would say to catherine zeta jones... after she slaps him for looking at her dirtily...
In this scenario, am I looking at paying approximately 3.5k dollars for a qt license to allow me to do this? Pricing obtained from this page:
http://qt.nokia.com/products/pricing
I'm assuming that I'm missing something here, otherwise the 50 euro Ovi registration fee is looking even more insignificant!
Regards,
spann