A great deal of things are happening for Qt right now. Very exciting news:
Qt frontend for Mozilla engine (or, rather, has finally been dusted off and updated) Now we have two of the best browser backends to choose from. (or three if you want to use that ActiveX thing)
and
Nokia gives out free N810 devices to developers in Akademy 2008. Wow, thats a heap of n810’s to throw around.
Too bad Kate forgot to mention the other talks from Nokia:
- Harald - Programming for embedded Linux
- Andreas - How Graphics View Works
- Simon - QtWebKit! (We are part of Nokia now).
- Girish - OpenDocument support in KWord 2
- and playboy Zack’s talk on Gallium3D - Graphics Done Right
and not to forget about former Trolls
And if course, I cannot really yet mention all the really powerful great stuff being developed at Qt Sofware/Nokia.. but I really want too! Because its just too cool and will blow your minds.
6 Responses to “too much Qt going on!”
Oh, happy day! Does this mean that Firefox will FINALLY properly integrate into KDE4?
s/two/three/ (or s/three/four/) - KHTML is not dead yet, and it fits better into an app already using Qt than the non-portable IE ActiveX crap will ever do.
@Kevin Kofler KHTML sucks cause it’s not compatible to many sites unlike gecko and webkit, yes I know it’s not KHTML fault blahblahblah but all I want is something that works for me and KHTML does not. Plus KHTML lacks point & click extensions to install and firebug (yeah I know there is a debuger in trunk but it sucks compared to firebug or even webkit’s inpector). So I’m glad I can pick between gecko and webkit now with Qt, at least those work with google apps and digg.
All sounds like good fun. Will these talks be available on the web for us plebeians and general non-attenders?
Hmm KHTML, it has some nice features and of course I prefer to live in wonderfully-integrated KDE-land but, well, until website displaying incorrectly becomes a rare occurrence konq will not be my default webbrowser. Plus Firefox has plugins.
p.s. Tungsten Graphics (of Zack Rusin fame) really needs a new logo, the current one is awful.
p.p.s. The right-hand navigation panel pushes the main reply box to the bottom of the page, with a big white space after the “name” “security code” etc. boxes. It’ll look OK aftere a few replies have been posted but is a little shabby right now.
Nice to see that Nokia has hit the gas instead of the brakes when it comes to Qt development. But it makes one wonder about Qtopia, especially Qtopia Phone. Qtopia Phone seems to have been put on ice, even more so when a Qtopia engineer finds time to write about Qt.
Enjoyed the info just the same. Thanks.
I, personally, support KHTML for a few reasons:
1) The vast, ever-increasing, majority of sites DO work just fine with KHTML. There are some that don’t, but in most cases I can fake FF and the site automagically works (Hooray for web standards!).
2) Name one real reason why KHTML sucks. It is incredibly better than that non-standards compliant, formidable piece of crap ActiveX thing, smaller in code base than either Gecko or WebKit, and integrates better with KDE than either Firefox or any WebKit browser currently is (inline spell check, KWallet password saving, etc).
3) KHTML holds to the KISS philosophy (Keep It Simple Stupid). Examining the WebKit codebase, it does not. For a user, they probably don’t notice.
I don’t object to porting WebKit to KDE, or using it. WebKit is a good rendering engine, partially because it inherits design from KHTML (Apple obviously saw something in KHTML when they chose it).