I am a little unclear on something about Qt. I though there was a clause in its licensing that made it BSD if TrollTech was acquired. Since that didn't actually happen, what is the future for Qt when Nokia cans it.
Android Lighthouse: Android Qt Port
11–20 of 28 posts
Re: Android Lighthouse: Android Qt Port
#12I am a little unclear on something about Qt. I though there was a clause in its licensing that made it BSD if TrollTech was acquired. Since that didn't actually happen, what is the future for Qt when Nokia cans it.
You are thinking of: http://www.kde.org/community/whatiskde/kdefreeqtfoundation.p...
"To fulfil the purpose of the Foundation, an agreement between Trolltech and the Foundation was made. This gives the Foundation the right to release Qt under a BSD-style license in case Trolltech doesn't continue the development of the Qt Free Edition for any reason including, but not limited to, a buy-out of Trolltech, a merger or bankruptcy"
Re: Android Lighthouse: Android Qt Port
#13Earlier quoted context omitted.
Learning Java is easy - porting 20years of libraries from C/C++ to Java is trickier. We only just got done porting them all from Fortran!
You could always use some sort of FFI. I don't think it's that big a deal, since you can still use C and C++ libraries on any desktop platforms + on Android.
FFI to C++ is a frustratingly difficult task for a number of reasons (there's a great presentation from FOSDEM where the Mono guys try to do this, can't find it right now though). There's a reason why FFI is mostly done against C libraries.
Re: Android Lighthouse: Android Qt Port
#14Doesn't matter - Nokia will cancel Qt in the next round of budgets. The real question is how screwed are C++ developers in general? MSFT's offering is switch to managed C++/C++ CLR and use WPF - two doomed technologies together. Or there is always MFC Apple say don't even try with C++ just switch to objective C Your only choice is GTK (from C) and plug into the rich commercial opportunities of Gnome and Linux on the…
I certainly hope C++ on the desktop is dead, there are far more productive languages for UI development. Obj-C, Ruby, Python, C# all come to mind. Show me a UI that a C++ programmer took a full week to build, and I can probably build it in an afternoon in C#/WPF.
Re: Android Lighthouse: Android Qt Port
#15Doesn't matter - Nokia will cancel Qt in the next round of budgets. The real question is how screwed are C++ developers in general? MSFT's offering is switch to managed C++/C++ CLR and use WPF - two doomed technologies together. Or there is always MFC Apple say don't even try with C++ just switch to objective C Your only choice is GTK (from C) and plug into the rich commercial opportunities of Gnome and Linux on the…
Why would Qt die once Nokia looses interest in it? I am sure Qt can survive on its own.
Qt as an open-source project will do just fine.
My fear is that Nokia will let future development languish and/or restrict future commercial licenses. Nokia's track record to date hasn't shown anything this evil, but you never can tell.
Re: Android Lighthouse: Android Qt Port
#16I've noticed there are a lot of ports from C/C++ to Java of late. Are there some sophisticated tools floating out there for syntactic transformations from C/C++ -> Java? Or is this all due to the gravitational pull of the JVM/Android?
This is not a Java port of it, but rather it runs using the Native SDK.
Re: Android Lighthouse: Android Qt Port
#17Earlier quoted context omitted.
You could always use some sort of FFI. I don't think it's that big a deal, since you can still use C and C++ libraries on any desktop platforms + on Android.
FFI to C++ is a frustratingly difficult task for a number of reasons (there's a great presentation from FOSDEM where the Mono guys try to do this, can't find it right now though). There's a reason why FFI is mostly done against C libraries.
Fair enough: I was thinking more about C than C++ there. I guess that for at least some libraries an FFI + a C to C++ glue layer might work.
Now that I think of it, I'm happy with a C + high-level language future, and C++ programmers should pick up one or both of them.
Re: Android Lighthouse: Android Qt Port
#18Doesn't matter - Nokia will cancel Qt in the next round of budgets. The real question is how screwed are C++ developers in general? MSFT's offering is switch to managed C++/C++ CLR and use WPF - two doomed technologies together. Or there is always MFC Apple say don't even try with C++ just switch to objective C Your only choice is GTK (from C) and plug into the rich commercial opportunities of Gnome and Linux on the…
I certainly hope C++ on the desktop is dead, there are far more productive languages for UI development. Obj-C, Ruby, Python, C# all come to mind. Show me a UI that a C++ programmer took a full week to build, and I can probably build it in an afternoon in C#/WPF.
Show me a Ruby, C# etc desktop app that took more than a week.
Word, Excel, Autocad - fancy writing something like that in a toy language?
Re: Android Lighthouse: Android Qt Port
#19Doesn't matter - Nokia will cancel Qt in the next round of budgets. The real question is how screwed are C++ developers in general? MSFT's offering is switch to managed C++/C++ CLR and use WPF - two doomed technologies together. Or there is always MFC Apple say don't even try with C++ just switch to objective C Your only choice is GTK (from C) and plug into the rich commercial opportunities of Gnome and Linux on the…
Why would Qt die once Nokia looses interest in it? I am sure Qt can survive on its own.
How is OpenSolaris doing now that Sun has gone?
Re: Android Lighthouse: Android Qt Port
#20Earlier quoted context omitted.
I certainly hope C++ on the desktop is dead, there are far more productive languages for UI development. Obj-C, Ruby, Python, C# all come to mind. Show me a UI that a C++ programmer took a full week to build, and I can probably build it in an afternoon in C#/WPF.
Show me a Ruby, C# etc desktop app that took more than a week. Word, Excel, Autocad - fancy writing something like that in a toy language?
Word, Excel, and Autocad are all more than twenty years old. They date to an era when C++ was the only tool available.
Furthermore, all of them can host modules written in "toy languages." Word and Excel are extended by VBS and C#. Autocad is extended by C# and AutoLisp.