Qt pricing (most up to date) [closed] - c++

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I am thinking about using QT for rich GUI commercial multiplatform programs. A would want to know how much the commercial license would cost.
I found just old prices (2008):
https://stackoverflow.com/questions/352896/qt-commercial-licenses
I am interested for the actual price (even earlier to see how it rises) for:
win+osx
The license is one time or I have to buy license yearly?
Is there anyone who uses the LGPL version commercially?
(I know that it can be done but I might need to make changes to QT without releasing the code for it: https://stackoverflow.com/questions/2945612/qt-lgpl-licencing-for-a-free-application-with-closed-source)
Actually this price policy (We don't tell you the price! We will call you!) is really strange to me, should I rather stay away form QT? I just tried it (15-20 hours) so going with other technology (.Net and just for Windows by dropping multiplatform support) is still an option

I'm no lawyer, so I'm not an expert in this area. I just wanted to point out that you can still develop closed-source software using an LGPL license. The catch is that you can't edit the Qt libraries without releasing the changes under LGPL.
Related SO thread: https://stackoverflow.com/questions/94346/can-i-legally-incorporate-gpl-lgpl-open-sourced-software-in-a-proprietary-cl. Read the top answer to that question, there is a much better explanation there.
Unfortunately I can't help you with the pricing, but if you're not altering Qt itself then you may not need to pay for it at all.

I have used Qt LGPL in commercial closed source applications. Besides the minor inconvenience of dynamic linking, I see no reason not to.
Your concern in bullet 3:
I know that it can be done but I might need to make changes to QT
without releasing the code for it
This is a very strange requirement. I don't know why you would want to hack on the Qt source, and then not release your changes to it. If you're comparing it to .Net, consider you wouldn't be able to make changes to that framework at all.

Related

Chromium OpenGL dead project? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I've recently started exploring the guts of VirtualBox's Guest Extensions on my Ubuntu Guest. Mostly from curiosity. Partly due to "OpenGL Warning: ... not found in mesa table" warnings. I noticed they are using Chromium OpenGL implementation. I have a two part question.
1.How do I get rid of those warnings? Are they indications of a larger problem? I'm noticing repaint issues which lead me down this path.
2.Am I missing something are is this a 12 year old project last touched 6 years ago!? Is it being actively developed some where else? Will it support OpenGL 3?
Online references would be appreciated as I'm having a hard time finding anything other than these below.
http://sourceforge.net/p/chromium/discussion/stats
http://chromium.sourceforge.net/doc/index.html
The chromium project is basically dead since 2008 or so. There is no support for GL3.x, and it is not planned. Actually, implementing the main purpose of chromium (application-transparent distributed rendering by manipulating the GL command stream) is incredibly hard to outright impossible with the programmable pipeline and modern GL features.
I'm not really familiar with virtualbox, but I am aware that they just used parts of the chromium project to implement a hw-accelerated guest GL simply by forwarding the GL command stream to the host. Such a task is much easier to adapt to modern GL, as no real stream manipulation is to be done. But I'm not aware of how far they have come on that path. So consider this only half of an answer to your question.

Can I use Qt LGPL license and sell my application without any kind of restrictions? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I want to start a cross-platform project. I had my researches and now I am almost certain Qt is the right deal. There is a big obstacle here though: licensing.
I want to sell my project and I also don't want to give out any source related to my work or pay for a license. I checked and noticed Qt offers both commercial and open source solutions. I have heard too many conflicting sayings on Qt licensing which confused me a lot. Some say that even if I use LGPL version of Qt, I still need to submit my code. Is this true?
Can someone give me a simple explanation on Qt licenses and tell me if I can sell my application without any kind of restrictions at all or not? Would anyone tell me any other equivalents to Qt for cross-platform development without any restrictions?
Just dynamically link to Qt. If you dynamically link to LGPL libraries, there's nothing to worry about.
If you statically link to them, you can just distribute your object files (not your source code), and you'll be fine.
The idea of the LGPL is that the end user has to be able to replace the LGPL library with a version they want. Dynamically linking to the LGPL library lets you do that, as does statically linking and distributing your object files. So long as you do this, you can sell your closed source program all you want.
Of course, there's more to the LGPL than just this, but that's the relevant part.

Is C++ enough for Nokia developing? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I really need info about Nokia developing. Can I program Nokia (Symbian) devices only with C++, or I need Qt too? (I have Nokia Qt SDK). I'm not really sure about GUI programing, so I ask for help :)
Also it would be really helpful, if you could tell me how to make something like cmd-style on Nokia (Symbian) <--(this is an optional question)
There are probably multiple ways to accomplish what you're trying to write (as Bala.C pointed out, you can use java), but the latest releases of the symbian OS have really encouraged people to write with Qt and specific with QML. That will likely have the fastest and smoothest interface to the device, because they've spent a fair amount of time optimizing it for the platform. Plus it'll make your application more portable to their N9 and other Qt based phones (the yet-to-ship non-windows Lumia).
I'm sure there is likely an API to tie directly into their lower-level architecture for drawing on the screen as well, but I suspect it's both not-well documented (unlike Qt) and subject to change from release to release as they don't expect developers to be using it as much.
Well, I don't think only C++ will do, but with Java it will be great.
Please go through the following link, it could help you equip yourself for Nokia Symbian Development.
http://www.developer.nokia.com/Develop/Web/Web_runtime.xhtml
Good luck

worth the time investment to learn Qt (c++)? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 11 months ago.
Improve this question
i already know java, c++ (no one framework for GUI development) and little of c# (winforms for gui development) but i'm thinking to ivest my free time to learn Qt, what do you recommend me? has Qt a good future or not?
I think it's worth it. We used Qt recently because it allowed us to make a cross-platform GUI that looks good on Linux, Windows, and Mac. It's kind of a tough learning curve to figure out how to use the QLayouts correctly, but after you do your GUI will look great on many different platforms, with many different font sizes, and with many different window sizes. I like how Qt allows you to make applications that use the native widgets with the native look and feel. Applications built with Qt will look like they belong no matter what platform they are running on. Another great feature is that the Qt framework is small enough that you can just include the Qt DLL files in your application's binary directory, so it simplifies the installation process for your application and makes life easier for everyone (no VMs to install, no 600 MB downloads).
I'd recommend using Qt directly from C++. There are wrappers for it on many languages, but it's hard to believe those wrappers will support every feature and allow you to subclass Qt classes.
You can kind of make cross-platform GUIs with C# WinForms, using Mono on Linux and Mac. But Mono's WinForms is not maintained, the results look really bad, and there are some crippling bugs on macOS.
I can't say enough good things about Qt. Their documentation is bar-none. I've never seen more examples and better documentation that with Qt. It's the standard by which I judge all other frameworks. What's more, the Cross-Platform capabilities are amazing. You get native looking apps, all for free. I'd say go for it.

Recommend fast C++ UI library with small memory footprint [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I want to write an app that reacts for global shortcuts and accepts commands (the way launchy does).
I'm trying to minimize the time between pressing the shortcut and the moment the window appears on the screen and is fully operational.
Can you suggest a good UI library (with some argumentation) that could be helpful?
I looked into QT and wxWidget but I'm afraid the app will get heavy (in memory / processing speed way) - and all I need is a small window that doesn't even need to be pretty.
.. or should I just go with native Windows libraries? (the main target is my Windows 7 machine)
Fast? Small? Windows-only? Sounds like you want WTL.
Caveat: You'll need to use VC++.
Also, I recommend grabbing the source straight out of SVN, as a new release hasn't been packaged in quite some time despite the fact that the project gets updated with some regularity.
I recommend FLTK!! www.fltk.org
Win32++ no mfc required neither ATL.
If you already know the winapi this is definitely for you. If not it helps a lot.
http://sourceforge.net/projects/win32-framework/
http://www.codeproject.com/KB/winsdk/framework.aspx
If you want the smallest memory footprint and are using windows just directly call the winforms routines provided by windows. This eliminates all the code in all these third party libraries. It's smaller and will be faster.