3 ms·
And licensing. Qt is LGPL or commercial. HTML is (in practice) more liberally licensed. (Edit: not GPL, but LGPL. Which is almost as bad for embedded systems a
by jacobush 9y ago
And licensing. Qt is LGPL or commercial. HTML is (in practice) more liberally licensed.
(Edit: not GPL, but LGPL. Which is almost as bad for embedded systems as GPL itself is. How do you let the user relink Qt or replace Qt with their own version, in the field? Nightmare. Just pay up. Qt LGPL is (or was) fine for desktop apps pre app stores. Now, not so much.)
- mkl 9y agoQt has been LGPL as well for years now.
- jacobush 9y agoAh, yes, true. See my edit though.
- bkor 9y ago> How do you let the user relink Qt or replace Qt with their own version, in the field? Where in the GPL or LGPL is this stated?
- detaro 9y agoGPLv3 section 6 requires you to to provide instructions that allow the user to replace GPL-licensed software on a device, unless there is no upgrade functionality at all (so if you have an upgrade mechanism, you must open it to the user, if you burn the software to unchangeable ROM you don't have to replace that with writeable memory just to enable user replacement) LPGLv3 section 4 modifies this for LGPL-licensed software, requiring you to allow replacement of LGPL-licensed parts of software under the same mechanisms. This is commonly known as the "anti-tivoisation provisions".
- Const-me 9y ago> And licensing. Qt is LGPL or commercial. And if you need on-screen keyboard, there’s no LGPL option available. You have to pay them significant amount of money, and also per-device fee.
- tjoff 9y agoThere is an API for creating one yourself, I did, not hard at all. Now it might not have a dictionary and other fancy features but it was adapted to our needs and it didn't take long at all to implement.
- Const-me 9y agoNot hard for a single language. Languages differ in the way their keyboard should work; not just layout, behavior is also different.