I'm trying to find any research/academic/journal papers/articles that analyze recent versions of Qt and Qt Creator.
Specifically, I'm trying to evaluate Qt from a real-time safety critical perspective, so any information is helpful.
P.S. I've tried the typical search approach:
Google scholar, IEEE Explore, ACM Digital Libray, etc.
Maybe I'm not using the right search terms, but nothing useful is turning up when I search for the following:
"Software safety Qt GUI" or any permutation of that.
Thanks again for any helpful insights.
To get the best info on Qt for research, contact Qt's leadership directly especially the public marketing contacts from the most recent Qt real-time announcement:
Jessica MillerWind Riverjessica.miller#windriver.com
Katherine BarriosDigia / Qt CommercialKatherine.barrios#digia.com
These three people may be helpful too - you'll need to figure out their contact info.
David Stone, Qt Communications Manager.
Aron Kozak, Web and Community group.
Hanne Linaae, Qt Education manager.
You can post your request in the Qt developer network forums.
Qt Developer Network Online Communities:
http://qt-project.org/wiki/OnlineCommunities
Qt Forums:
http://qt-project.org/forums
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
Friends I am in dilemma.
None of the threads explain if [and how ] i can migrate an application from Qt free version to Qt commercial.
Me and my friends started developing an application using Qt[freely available] for learning .
We have created a good application and think we can sell it for pocket money.
The application does not modify any of the Qt source[we are not that good programmers :P] and we dynamically linked also.
I want to know how can i migrate it to Qt Commercial [since it protects from giving my source code].
First things first
a) can i migrate an application[not distributed in any form] written in Qt free version to Qt commercial.
b) will i have to re-write the application again in Qt commercial version or i can use my source files from old project and migrate to new Qt commercial project.
c) are there any API difference between Qt commercial libraries and Qt LGPL libraries that will make porting difficult/impossible. we still plan to have dynamic linking
d) i hope all Qt LGPL features are supported in Qt Commercial.
e) is there any complex legal thing i need to know. i only understand with LGPL we have to distribute code / object code + dynamic linking but in Qt commercial we dont have to.
If it is possible and legal then only we will buy Commercial License[expensive huh] ?
Why don't you go to qt.digia.com click Try&Buy and then Download and Install Qt Enterprise.
You'll see if you can port it before actually buying a license.
And for licensing questions I would suggest to contact then directly. I guess they would give you all the answers you need and try to help you with any problems you run in to.
The core is basically the same. So you can compile your existing code by enterprise version with no change. The only reason for the commercial license is if you need commercial support or you are shipping on an embedded platform like a cellphone.
Qt Enterprise has some more features and tools like Charts, Qt purchasing, Qt Quick Compiler, Boot2Qt and some others.
I see two really big issues:
Not understanding the terms of the commercial license you plan on using.
Not understanding the terms of the LGPL you develop under: they are nothing like what you state.
The terms of the commercial Qt license either expressly prohibit what you have done, or it is implied/understood that what you did is a NO-NO. Your project is now legally tainted and you can't ever apply the commercial license to it unless you buy the licenses for all the developers that participated in the development. They'd go broke long ago if everyone was as "clever" as you are.
The LGPL does not force you to release your source code. All it forces you to do is to let the end user re-link with binary-compatible Qt of their choice, and for you to allow access to the sources of Qt you used. If you use a release Qt, all you need to provide, on request, is the .zip of the Qt version(s) you redistribute. Since you link dynamically with Qt, there's nothing further you need to do here.
The only binary differences between commercial and open source Qt are in the license markers. There's literally nothing you need to do to link your code with a commercial Qt. Just swap out the DLLs and you're done.
I'm not a lawyer.
I use ITK 4.3, VTK and Qt on Visual Studio 9. How do I add ITK-SNAP?
I want to know the difference between ITK and ITK-SNAP and what does ITK-SNAP add compared to ITK.
I started working with ITK. Do I need to change my code or can I continue in my project?
SNAP is a software application used to segment structures in 3D medical images. It provides semi-automatic segmentation using active contour methods, as well as manual delineation and image navigation. The software was designed with the audience of clinical and basic science researchers in mind, and emphasis has been placed on having a user-friendly interface and maintaining a limited feature set to prevent feature creep. ITK-SNAP is free software, provided under the General Public License. ITK-SNAP binaries are provided free of charge for academic or commercial use.
This tutorial provides a step by step walkthrough of building ITK-SNAP 2.4.0 from source on Windows. We will be using Microsoft Visual Studio 2010 for building the application. Make sure you have VS 2010 installed and VS Service Pack 1 as well. (if required) : Click Here for full tutorial
ITK is abbrevation of Insight Segmentation and Registration Toolkit which is open source library which provide image processing algorithms to develop your application on different platforms ex python, c++.You can follow this link: http://qtitkvtkhelp.blogspot.in/2012/11/itk-installation-for-msvc.html to build ITK and use that in your application. ITK-SNAP It is an open source software you can directly install it from here. I think this is solution for all of your questions.
I had asked before also for rendering pdf but its in blackberry JAVA development.
But currently I want to know , is it possible to render a PDF in the playbook using native sdk 2.0.0 with the QT framework.
If it is possible then can you suggest me some example if it exist on the google?
Is it possible with any third party library i.e of c++??
Thanks in advance.
It is possible, provided you agree to the licensing of the third party library.
Open source world has two know libraries for PDF rendering:
Poppler
MuPDF
Both provide bindings for Qt, the bad part is that both are licensed GPL.
However, the firms working behind both libraries provide commercial licensing options.
For commercial licensing:
GlyphandCog provides commercial licensing for XpdfWidget/Qt
Artifex Software, Inc. provides commercial licensing for MuPDF.
I'm trying to build an application in my ARM9 (Freindly ARM) board that will get data via serial port and update the database.
Now I need to port SQLite in my embedded linux and write an application to store my values.
How to port SQLite to Embedded linux
Pygtk or Qt? Which is easy for a newbie ?
P.S: I know I'm asking a lot of questions in a single post, but I just thought giving the complete picture will help to give a better suggestion. If not personalized opinions, I'll be grateful if you guys can give me pointers to good links/tutorials. :) Thanks.
1.
You don't need to port sqlite to the your Freindly ARM ARMv9 board.(as Mat has already mentioned)
I am going to assume that you have a mini2440 or
a micro2440.
Either way it is a Samsung S3C2440 chip.
sqlite works on this board as per the following thread.
Sumeet's post has cross compliation instructions.
Qt cross compliation works as per the following thread
So does Python and Gtk.
You have 2 options when it comes to cross-compliation,
Cross compile yourself
Use a tool like buildroot or openembedded's bitbake
For further resources on cross-compliation and building packages for this board
see the following resources.
mini2440 Google Code Project, specifically see the wiki and download sections
FriendlyArm Forum
FriendlyArm Downloads
linuxmce mini2440 wiki page
HOWTO-Getting-Started-With-OpenEmbedded for mini2440
Further HOWTOs
2.
PyGTK and PyQt are both relatively easy to learn in comparison to learning and debugging cross compilation on embedded architectures. If by Qt you didn't mean PyQt but instead meant C++ and Qt, then it not only becomes a choice of GUI toolkit, but also of language. I don't know your familiarity with Python or with C++, so I don't know which would be easier for you.
Which one you want to use is up to you.
Resources for both are linked to below
PyQt4 Tutorial
PyGTK Tutorial
As you may already know, Phoenix is developing an alternative computing environment based on top of its BIOS, called HyperSpace. According to its designers it should run "a collection of commonly-used browser-enabled applications designed to make the Internet browsing experience simple, fast and secure".
Although Phoenix has declared in its FAQ that you will not be able to install/run your own applications on top of the HyperSpace, in a recent interview on MIT's Technology Review said that they are planning to open in June an iTunes-styled store to sell applications.
I'm guessing they are probably up to Apple's business model of providing secure applications via a centralized service thus sooner or later a developer toolkit shall arrive.
Since Qt has an impressive record of cross-platform capabilities, do you believe that Nokia should make an alliance with Phoenix to port the Qt toolkit to the coming HyperSpace application developers? If it's not Qt what should the ideal developing platform for HyperSpace be?
It looks to me that this is basically a dual boot machine.
one boot goes to a version of windows that QT supports (or will presumably support).
one goes to a web browser and will only run web applications or widgets.
If your asking whether QT should allow you to target the second environment, then it all depends on whether that is even remotely compatible with the QT technological choice of including a Webkit engine.
There could also be a licensing issue.
I am not convinced the Hyperspace product is aimed at desktop developers the way QT is. I think it's aimed at web applications developers.
Edit: What you seem to wonder is whether Nokia sees a commercial interest in supporting Hyperspace and whether they have the resources to do it. Unfortunately, I suspect only the head of QT development at Nokia can truly answer that.
"I am not convinced the Hyperspace product is aimed at desktop developers the way QT is"
Qt is aimed at embedded mobile phone apps, they are now owned by Nokia, if Qt happens to run on desktops that is just a nice bonus for Nokia.
Given it's, small size, no external dependencies and 'easy to port'-ness I would have thought Qt was a good start for a bios-os desktop.