Language selection and the license problem
Posted: 26.11.2010 Filed under: Qt-Python Leave a comment »| I get that in the kingdom of the blind, the one-eyed man is the king. So I am going with C++. Hereby I decline below what happened. |
(Eclipse + ) Python + GTK+ + ClutterAfter
Eclipse
2 days non-stop working I couldn’t run even a simple Clutter project. I even couldn’t understand if Clutter will be under development further or not. There mentions on Clutter to be dead soon and deprecated under GObject.Bottomline, if I can’t even install it how the end user will… I give up with this option.
.
.
(Eclipse +) Python + PyDev + PySide (+ Qt4) | (+ PyQt)
PySide is the Eclipse plugin to edit Python files under Eclipse. PySide and PyQt are two seperate projects for porting Qt into Python.
Qt
Qt has got amazing rendering tools within. I really thought “this is it” when I have seen Puzzle example [1] . Drag drop will be my main concern beneath other things.When I have seen PyQt is not available under LGPL (only GPLv1, GPLv2 and commercial which is not specified on the web site). I will be writing a Python code so it is nearly mandatory to share to codes, but, I don’t know somehow it suddenly looked “not-what-I-want” to me. So I checked PySide…
PySide is okay with carrying out LGPL outcomes. But what confuses me is that PySide uses some of libqt libraries which are protected under GPL. Doesn’t it make PySide outcomes obligated to GPL? Ugh…
.
C + GTK+
I am really considering still to go with C because I don’t want to use C++ which looks like an unwanted child of C. I can’t say this is a thought I grasp after a deep technical analysis; I just didn’t like it. I would rather use Java if so. But C is not like that. It looks simpler to manage and more mature. It is not OO in nature but after recent modifications on C it is anymore usable as if OO supported. And speed attracts me indeed. And I don’t think porting to Windows or OSX would be problem as there are extremely great examples out there.
.
GPL / LGPL / Commercial?
GNU
I don’t have to share the codes. Of course I can share (I probably will) but I don’t want it to be mandatory for me — I don’t want to be obligated to share. Because, I don’t know how things will go on after first release. There is no income / donation plan in my mind for now. And obviously I need a business plan (even for non-profit option) to get this further which I don’t have one yet. I want to decide according to quality and need-satisfying of the project soon.
.
[1] http://gitorious.org/pyside-examples
[2]
