I have a questions with regards to using Webkit as a component in a Windows application. I know there are options for embedding a browser, but they are overkill for my needs.
Looking at the WebKit licensing page, it seems that the licenses are permissible; the traditional BSD license and the Library GPL license, the latter of which allows me to distribute my application as "work that uses the library". This is also stated here. However, I've found several posts (including on Stackoverflow, such as this one) that say that Apple has some proprietary code in there which doesn't allow its redistribution. Is this an inconsistency, or am I missing something?
There are two WebKit Windows ports at the moment:
AppleWin port
WinCairo port
WebKit itself is licensed under LGPL and BSDL.
But, AppleWin port uses Apple's proprietary WebKit Support Library.
This can't be redistributed.
https://developer.apple.com/opensource/internet/webkit_sptlib_agree.html
Related
Am i able to create an OS's User Interface with Qt's .ui file?(Qt .ui file is an xml file)
This confused me long time already,bcuz in http://qt.io
you can see
BUILT WITH Qt
LG’s webOS
The answer is yes and Qt is a cross-platform application development framework. Some of the well known applications developed with Qt are KDE, Opera, Google Earth, and Skype. Qt was first publicly released on May 1995. It is dual licensed. That means, it can be used for creating open source applications as well as commercial ones. Qt toolkit is a very powerful toolkit.
I'm planning to implement a VST host for a cross-platform application I'm developing.
Which version of VST should I prefer, VST-2 or VST-3? It seems that VST-2 is depreciated but most other host applications still use that rather than 3.
Are there any examples which will build on Linux (Ubuntu) that have got a host built in and are licensed BSD or similar? I've got no issue with JUCE except after a day of trying that, there are too many build issues on Linux for the VST host example.
The application is written in C++.
Definitely VST2.x. I would not call the VST2 standard "deprecated", so much as VST3 is "DOA". ;) Almost all commercial sequencers support VST2, hardly any (except for Steinberg's Cubase, of course) support VST3. As far as plugins go, almost all plugin manufacturers support VST2, but much fewer ship a VST3 plugin.
The reasons why very few plugins/hosts made the jump to VST3 are among the following:
There are very no real technical advantages to the VST3 API compared to the tools offered by the VST2 API
The VST3 API is significantly larger and harder to understand than VST2
VST3 is not backwards-compatible to VST2; it's basically a completely different plugin standard
As for a Linux-compatible VST2 example, check out MrsWatson, which is licensed under BSD (full disclaimer: I'm the author and maintainer of this project).
What is the license of Qt platform (Qt libraries, QT Creator, Designer, Linguist etc) after Digia bought it from Nokia?
Is it still LGPL? Are they planning to enforce their own commercial license? Or will there be three versions of it (GPL/LGPL/Commercial)?
Taken from the Digia's Qt Commercial Blog
Committed to both commercial and open-source licensing
Since we
acquired the commercial licensing business of Qt a bit more than a
year ago the Digia Qt R&D team has been hard at work developing and
releasing not only new and updated features and functions for Qt
Commercial customers, but also working together with the Qt Project
building and releasing both the commercial and LGPL releases,
contributing documentation, bug fixes and improvements mainly to the
desktop and embedded platforms.
...
With this acquisition Digia will have an increasing responsibility to
the global Qt community, not just the commercial licensing business.
We believe in the power of the Qt dual license. It is a great value
for Qt that it can be used under an open source and commercial
license, since customers have different needs and the licenses have
different purposes. Digia wants to continue the good co-operation with
different individual contributors and companies working together in
the Qt Project. We also are committed to continuing the special
relationship Qt has with the KDE community via the KDE Free Qt
Foundation. We believe that this symbiosis is valuable for everyone
involved.
...
We want to work with the entire Qt ecosystem through
the Qt Project to make sure that Qt will continue to thrive both under
commercial and open-source licenses.
Sounds like they want to keep things running the way they are and focus on making the commercial and open source communities even stronger.
I would start using C++ and develop commercials application with GUI. I found Qt libraries and seem that are good for my software.
I saw that Qt has LGPL license, I read that the license allow the developer to create an application and release it with different license, but I don't understand if at the moment I can develop a commercial C++ windows application (closed source) with Qt WITHOUT pay for the Commercial license.
Could someone clarify this point?
Thank you!
The LGPL licence means you can use Qt in a commercial application if, and only if, you dynamically link to it. That means using a DLL (or equivalent for your platform) rather than a static library. As long as you do this you can apply whatever licence you like to your actual application.
Look at the Wikipedia article for more information on the LGPL.
if you do so, you have to provide a way to get the source of the libraries under lgpl you are using.
hy
I'm trying to port a KDE application to windows
my problem is finding a suitable KDE SDK for windows, i can't include any k-headers (kapplication.h kaction.h ....) and I haven't even got to the libs
is there a guide for doing things like this
KDE 4 is intended to natively support windows so it should be less of a "porting" effort and more of a "getting it to compile as-is" effort (though there will likely be a few minor changes). You should be able to find the relevant information on the KDE on Windows site. Specifically, there is a porting section in their wiki for ensuring KDE apps run under windows.