Slashdot Mirror

← Back to Stories (view on slashdot.org)

Nokia Makes LGPL Version of PyQt

Posted by timothy on from the if-not-one-way-then-another dept.

EtaCarinae writes "Nokia didn't succeed in convincing Riverbank to change its licensing terms on PyQt, and so decided to create their own LGPL'ed version of it. From the FAQ at the PySide site: 'Nokia's initial research into Python bindings for Qt involved speaking with Riverbank Computing, the makers of PyQt. We had several discussions with them to see if it was possible to use PyQt to achieve our goals. Unfortunately, a common agreement could not be found , so in the end we decided to proceed with PySide.'"

4 of 263 comments (clear)

  1. Re:Kudos to Nokia by moon3 · · Score: 0, Troll

    Thank you Nokia! Now drop the MOC from QT and everybody might consider your platform.

  2. Re:Kudos to Nokia by Anonymous Coward · · Score: 0, Troll

    Not if you want to write commercial software on top of it...

    s/commercial/proprietary (or non-free)

    The GPL is a commercial license. It clearly permits the licensed software to be sold.

    Technically, I could use windows 98 as a platform to process important financial transactions on. It doesn't mean it is feasible.

    Just because GPL allows selling commercial software, it doesn't mean that it is very feasible.

  3. Re:Kudos to Nokia by Anonymous Coward · · Score: 0, Troll

    MOC is terrible, makes QT terrible


    1) complicates the build process
    2) pollutes the global namespace terribly (emit, signals, etc.)
    3) slows rebuild as MOC has to inspect the code and regenerate MOC files if needed
    4) cannot understand normal and common C++ code (inner class, templates)
    5) causes binding errors that are (maybe not) discovered at runtime
    6) doesn't know const char * vs. char const * are the same
    7) same goes for any other compatible but not strictly-exact prototype
    8) adding one more tool/compiler to code generation (to make, compiler, resource compilers, linker..)
    9) complicates porting to emerging or not supported platforms as you have to port MOC compiler first
    10) MOC 'invents' its own non-standard non-ISO C++ syntax
    11) fragments drive as every MOC dependent file has to be frequently overwritten
    12) is redundant as Boost already and clearly shows

  4. Re:Kudos to Nokia by nstlgc · · Score: 0, Troll

    Yea, and when somebody does it they get an article on Slashdot questioning their ethics. Good point.

    --
    I'm Rocco. I'm the +5 Funny man.