A number of KDE related news stories are floating about the interweb today, so here's a quick round-up. Aaron Seigo writes his KDE e.V. Presidential Address on his blog in an effort to force the e.V. to be more transparent about their activities. Over at Ars Technica, I have an article talking about the future of KHTML and WebKit: you'll be happy to know that this seems to no longer be a real problem. Daniel Molkentin has published a new book on coding for Qt 4.x which is now available for ordering at qt4-book.com. Lastly, I've stumbled across a short visual tutorial for those Mac OS X users among us that are looking to help test the KDE/Mac snapshots. Of course you can always go over to TechBase for the build instructions if you have some CPU cycles to spare.
Call me stupid, but I didn't really get the news about KHTML and Webkit.
Sooo...have they merged or what? When will KHTML get abandoned? If it won't, why not? Where do the SVN commits go to? You guys have your own Webkit tree?
Questions over questions...
Not a KHTML/webkit dev, but afaik several of the dev's are working with apple in the Webkit tree. Some things from KHTML are being ported over to Webkit. Most developers will abandon KHTML and work on Webkit, but it's a KDE 4.x thing I think. Of course, if Webkit becomes part of Qt 4.4, they can use that I guess.
I said Most dev's will abandon KHTML, as last time I checked not all supported the move. This might have changed now.
"Sooo...have they merged or what?"
Many parts have merged. Some things (like the article mentioned) have yet to merge and may not merge.
"When will KHTML get abandoned?"
Might be obvious, but when the last developer interested in it stops committing I guess.
"Where do the SVN commits go to?"
New commits go here: http://webkit.org/coding/contributing.html
"You guys have your own Webkit tree?"
Trolltech and KDE developers have our own platform target for WebKit. That platform target lives in WebKit SVN just like Apple's platform target and Nokia's platform target. They are all actively developed in WebKit's svn.
What has happened is that many KDE developers and Trolltech developers have decided to start working on WebKit proper. Qt will be including WebKit in an upcoming release and there will be a KDE KPart which will allow Konqueror to use the very same WebKit rendering engine that the Safari browser uses.
You must be super-smart, actually, since there are no news.
Nothing really has changed. You'll know when stuff is real
when you see actual commits, done by actual KHTML developers.
And, then, you'll know what's being attempted, not if it will
work out or not.
"...actual commits, done by actual KHTML developers..."
Don't these count?
Did any of these people contribute anything to KHTML in the last 3 years or so? No (well, Rob and Niko did KSVG2 stuff, and George did stuff relevant to... merging with Apple). So how would they count? And even more so, one has to consider that a lot of them are done as subject to commercial contracts, and, as such, should IMHO not even be done with @kde.org addresses.
... Besides, I was referring to commits in to KDE SVN, not some 3rd-party SVN.
So, what's your point? I mean, what do you think from your dev pov it's going to happen with the webkit/khtml topic? And what do you hope? You seem quite on the "don't touch our KHTML!" side, am I wrong?
My point is that there are 2 things that have actually happened:
1. Some corporations and contractors somewhat involved in KDE, such as
TrollTech, have interest in WebKit. Some of people working for them,
who have never been involved in KHTML development or have not been
involved in it for many years have committed to WebKit. Now, I am sure
those people do think their actions also help KDE, but they also have not
been the ones making thousands of changes over the last few years,
or the ones trying to setup a decent and fair working relationship.
2. Some of those people got together with some of the KHTML contributors
at aKademy, and tried to convince them to abandon KHTML for the fork.
As a result of discussions, there were some ideas for a more sensible
path that were proposed. There are hence some things that will be tried.
May be they'll work out, may be they will not. At any rate, any announcement
is premature, and an announcement coming from people not involved in
actual development is simply inappropriate.
So the short answer is that stuff might happen, and if it does, I am sure
you'll see it in the commit digest. Before that, it's all speculation.
And as my side... I would love to work with Apple (and in fact we do
cooperate with them very -losely- on KJS, especially since their JSC
developers have shown a lot more concern for our technical needs than their
HTML ones). On the other hand, I have no interest in working (unpaid) for
Apple; nor do I really have the time for diplomacy and grandiose projects.
So, well... I would really appreciate if the people who are all jumpy about
WebKit, would, you know, actually help sort the difficult issues out and not
just go around telling everyone how we should/will be using it. There are
finally signs that that may be happening, though.
Lars created KHTML, but because he hasn't worked in KDE tree recently he no longer counts... ok.
Developers join the KDE project and leave it again all the time. Only ones that that count are those currently willing to invest some of their time. Not much room for nostalgia here.
I won't even mention has-KDE4-compiled-and-running as a criteria as that would rule out far too many ;)
i think it's disingenuous to rule someone out because they start contributing again but to a related project that is still qt/kde related. in my books, working on a qt port and a kde kpart for webkit is worthy of not being dismissed.
i also think it's pretty unfair to those who are certainly active kde developers working on this stuff to ignore them in these dismissals. finally, to paint those have managed to find a way to support themselves working on things close to their interests as somehow innately untrustworthy because of it is pretty lame.
i'd also suggest that khtml and qtwebkit are in need of soft skills that many of the developers involved lack. chasing away those who can bring those to the table, particularly after they were invited in the first place, is not what i'd call big picture thinking. =)
i think that pretty much sums up what i think of the dismissive and generally negative attitudes some cast upon the idea of qtwebkit.
Maybe the negatives come from remembering how much fun it was to work on khtml before Apple did what they did.
I actually wrote a blog titled "How to Destroy a Free Software Project" based on the khtml saga. I deleted it to not hurt the people involved. I really don't want to discourage anyone. This is a mess, years have been lost, and the choices are between bad and worse. I guess the most difficult is coming to grips with the idea that a fundamental building block of the KDE desktop is now under someone else' control, someone who's interests are that KDE not exist.
I feel strongly that KDE has left itself wide open to irrelevance by thinking in this instance product not process. KDE wouldn't exist but for the process. I acknowledge my own contribution when I excitedly highlighted the patches coming from the safari codebase. It became clear that I was misled when the khtml developers either quit or only stayed on due to massive intestinal fortitude.
Didn't Webkit as a process arise from Nokia and others wanting to work with Apple? (Gee, that made the IPhone browser alot easier didn't it) I suspect that they insisted on an appropriate process before getting involved. Somehow we (KDE) just went along. I think we got suckered. Back 3,4 years ago it should have been recognized for what it was, a hostile fork.
You know, all (trademarked term) what happened, was that fame was being taken away from individual developers for their code. Like when they passed ACID test already, and KHTML didn't yet, and everybody said "why don't you just take it from Apple".
I can imagine this has hurt those developers and deprived them of their motivation to work on that specific project. But I am at the same time very glad, that the influx of manpower into the rendering engine has happened and the potential has not been waisted.
If you or anybody envy Apple or Nokia or whoever for earning money from the LGPL code, I am afraid, you didn't understand why the LGPL type of license is chosen by KDE in the first place.
And now it's happy end. A consortium of companies will in cooperation maintain the web rendering engine and make it the best suited one. They have different toolkits for which they implement backends (QT -> KDE from Trolltech, GTK from Nokia, Cocoa(?) from Apple) and that will push the quality of the abstraction to a new level.
And KDE simply can stop working on it itself, for all boring stuff, and concentrate on e.g. Plasma. And how is that not a great thing please? You can't even start to imagine how much more me Konqueror-Browser user loves to see Epiphany use Webkit (well possible now), instead of Konqueror-Browser using Gecko (still near impossible to be done right).
It's still free software, you can always *fork back* anyway.
This is open source; focused development is rare :) There are people putting effort in the better fork and there are people still afraid of change that are working on KHTML original.
Its only fair to point this out, and its not hard to see that the most compliant and most developed-in tree will naturally be picked up by distros and end users.
That's the situation (as the article already said). You make your own conclusions :-)
I'll be so happy to see this unforking but an eventual passage of kde to gpl3 are ok for webkit (or viceversa)?
the GPLv3 discussion is being had on the kde licensing mailing list. before that has come to a conclusion, it's premature to take a stand on GPLv3 and KDE one way or the other.
It's irrelevant: KHTML and WebKit is LGPL v2+
Actually 2.1+, since it's the license used in some Apple-originated files
(render_layer.cpp and arena.cpp)
WYSIWYG Editing is one of those things that is really missing in KDE.
Webkit has this ability, is this merged into KHTML?
Will we at last see TinyMCE, FCKEditor and other editors running in Konqueror?
it's in webkit, though QtWebKit doesn't implement the widgets for it yet so you still can't see them in QtWebKit. the underlying bits are there, however. so this would be one of the advantages that would come with a completed QtWebKit.
Will QT be able to base its old HTML implementation on QtWebKit, BTW?
And if QT 4.4 contains QtWebKit, probably KDE 4.0.0 should require it, so this sort of cleanup can happen as soon as possible?
Not sure if my question is relevant to this topic. I am a daily user of quanta plus. I didn't see any news about quanta plus been ported to qt4 or is there any features planned in quanta plus for KDE 4. In Linux we miss a good HTML editor like dreamweaver. The only better solution I think available to Linux user is quanta plus. I would like to know the status of this cool software. Thanks
I think the development stuff (esp. kdewebdev) is targetting KDE 4.1.
In fact, after a quick build of kdevplatform and kwebdev, I can tell you that Quanta... exists. And runs. But doesn't produce much in the way of a useful interface when it does run.
But, like I said, I believe the intention is to release it with 4.1.
Yes, the plan is to have it ready around 4.1.
There have been a number of issues with kdewebdev. For one, using a common framework with KDevelop has meant we need that in place, and we've had to wait for KDE libraries to stabilize... Then there are the obvious questions about whether we will have an adequate framework for visual development in place, which has long been a question of what is happening with Webkit. In addition to this I have been buried in taking my business from seasonal swings to a dynamic expansion so I can allocate effort without jumping up to put out fires.
While we do have some volunteer development most of our development is sponsored. Currently we have no developer working on VPL (a DTD accurate WYSIWYG alternative) and have totally burned out two volunteer developers due to the sheer difficulty of the task. The irony is that we have a huge user base and maybe two dozen sponsors. 50-100 sponsors at "lunch money" level contributions would empower us to have several developers full time on this. The efficiency is orders of magnitude higher when a developer works without interruption. I encourage our supporters to go to http://kdewebdev.org/donate.php.
Congratulations to Daniel for another Qt 4 book, this time in English.
I believe Johan Thelin also has a book, Foundations of Qt Development, which he said was going to get printed last week.
Unfortunately I will have to wait for a year before these books will be available locally, which is how long it took for two other Qt 4 books (C++ GUI programming and Introduction to Design Patterns) to be available. Hopefully I'll get my copy next month. Yay!
... now to wait for a KDE 4 Development book... :)
The Mac OS X installer asks the user to agree to the GPL license. There is no need for the user to agree to the GPL license. It only grants you rights and takes none away from you.
The GPL it's a license like any other one, and like any other one you can disagree with it and refuse it (I'm just saying you can, not that you should do that ;) ). And like any other license you have to be aware of it, so yes, the installer question about the license is needed.
No it's not, and refusing the GPL means you are not allowed to distribute the application. It has no effect on using it.
I'm not a lawyer but I suspect that almost every EULA out there is about distributing (well, about NOT distributing ;) the software you're installing.
No, that's not the case. EULAs typically also contain language on how you are allowed to use the software. E.g. the BitKeeper license contains a clause saying that you may not reverse engineer the code. There are also frequently clauses saying that you are not even allowed to modify the program files on your own computer. The GPL has none of these restrictions; there are no limitations at all on how you may _use_ the software.
There are some details you are mixing up;
according to the GPL text; as soon as you use the software you are bound by the license (you accept the license as soon as you use it, or in other words, if you don't accept it you can't use it)
The part I guess you are confusing it with is changes you make to it have to be made public, but only if you actually distribute your version. But this distribution thing has nothing to do with usage and acceptance of the license.
That's not true, in fact it explicitly says the opposite!
From version 2:
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
Version 3 makes this even more clear:
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
> according to the GPL text; as soon as you use the software you are bound by the license
As Kevin already pointed out, this is the exact opposite of the truth.
> if you don't accept it you can't use it
In the USA, even if a license explicitly forbade you from using it in any circumstances at all, you would still have the right to use it, because copyright does not give somebody the right to stop you. Copying software to your hard drive during installation and copying software into memory in order to execute it are not covered by copyright.
Not sure I got your explanation, but your statement is true.
GPL is a copyright license -- it applies to distribution -- there is no need to force the user to agree with it for the purpose of installing, using, or modifying the software -- he is only liable on redistribution (so just stick a COPYING file with the package). EULAs are shrink-wrap contracts, they have usage clauses -- the user can be liable for unauthorized usage -- that's why it's important to have the user to acknowledge it and accept the risk.
At least you must agree to the "NO WARRANTY" section (11. and 12. of GPL V2).
In case I'm a private person offering something on the Internet, everyone should be clear right from the beginning that I'm not giving any WARRANTY.
But in case companies like Apple offer something on the Internet, I at least can have the impression that it doesn't ruin my computer, deletes file, burn the neighbours dog or start another worldwar.
Such warranty is not given here and I understand that Apple or any other company needs to have this signed.
Where's the legal backing for what you are saying?
If you do want to state that, just state it. Say "KDE libraries will be installed. Bla, bla, bla. This software comes with no warranty. [Next]" That is not a condition to use the software, so it's stupid to force the user to accept it.
Anyway, this thread is about having the GPL to be accepted as an EULA contract.
From the GPL FAQ at http://www.gnu.org/licenses/gpl-faq.html#ClickThrough
"Q: Can software installers ask people to click to agree to the GPL? If I get some software under the GPL, do I have to agree to anything?
"A: Some software packaging systems have a place which requires you to click through or otherwise indicate assent to the terms of the GPL. This is neither required nor forbidden. With or without a click through, the GPL's rules remain the same.
"Merely agreeing to the GPL doesn't place any obligations on you. You are not required to agree to anything to merely use software which is licensed under the GPL. You only have obligations if you modify or distribute the software. If it really bothers you to click through the GPL, nothing stops you from hacking the GPLed software to bypass this."
KHTML / Konqueror rules. It feels so much better already on Linux than Firefox. Maybe Webkit will give Linux the speed of KHTML, with the reliability of Firefox.
I just got KHTML running on Windows:
Maybe I'm a pure Webkit / KHTML user in a couple of months ;)
Awesome! I didn't know it was already this far along. I guess now that I managed to switch to Linux for most of my time at work, it's no longer so important, but very cool nonetheless!
I know that Webkit is still similar to khtml, but I don't know whats happened besides Apple taking qt rendering out of it. I am excited to see four large groups (Trolltech, Apple, Nokia, and KDE) working on a single layout engine. While I don't think its really fair that Apple secretly forked the components that make up Webkit (khtml, kjs, ksvg I think). It would be a good thing for KDE to jump in the boat with everybody else. Such an amount of collaboration could really help create an excellent engine for unix-like desktops. If I'm not on Linux I use Firefox, but Konqueror will always be my favorite browser.
It might just be me, but I think the "We are going to WebKit" news deserves it's own story, not a minor mention in a quickies summary.
As I said before, it deserves neither, as it's woefully inaccurate.
I couldn't agree more and I had the very same feeling when I read that article (therefore my question at the very beginning) - this news is no news at all and should never have been made public. I will only result in ever more rumours about KHTML and Webkit...sigh.
you saying its inaccurate doesn't magically make it inaccurate. you may not agree with it, you may not like it ... but it's a whole lot more accurate than you seem to be willing to accept. perhaps that's something to think about.
Aaron, please... The khtml and kjs people who were
in Glasgow talked to me, asked for my opinion
(which is rather laissez-faire), and told me
what their plans are and aren't. I know that if
they wanted to make an announcement, and if there
was something worth making an announcement about,
they would. Things aren't as simple as "KDE will
use WebKit". It's true that there is a renewed interest
in merging things, but that has happened about a zillion
times before. If something happens, the commits will
And, frankly, I am getting tired of you spreading disinformation
about the direction of KHTML. You keep making all those
definite statements that seem to have at best a weak
basis in reality. I am afraid I can not interpret it as anything
other than an attempt to influence the direction of a project you have not
contributed to, which goes strongly against KDE principles.
("He who does the work decides")
It's pretty clear, for example, that the article linked above was
not vetted by anyone involved in KHTML development, as the original
version contained clearly wrong technical claims, which were only corrected
after they were noticed by an another KDE contributor.
> You keep making all those
> definite statements that seem to have at best a weak
> basis in reality
here's what i know:
- people (some with and some without a profit motive, but all with a pro-kde viewpoint in life) are working on qtwebkit and a kpart for it
- there is both community participation as well as financial investment going into this
- the goal is to provide webkit as an alternative to khtml
- when that is achieved the two code bases will compete on their merits
- if feature and bug compat with other software products using webkit is maintained (meaning a larger user base, among other things), it's obvious which one will get picked up by those integrating kde software into their own products (think linux distros, third party software developers)
- in the meantime, khtml has been decreasing in user support
- having a larger community of developers would be a great thing, and webkit will be able to move ever quicker forward for it (meaning: we benefit from better tech and those working on it from kde probably will have a more rewarding time of it)
- progress has been and is being made on the "apple cooperation" front, and at an increasing pace
- there are those who want more recognition for the role kde developers played in khtml both historically as well as currently, yet some of these same people do their best to torpedo attempts to rectify that
the above is precisely what i've been saying. when someone asks me "has a decision been made?" or "is webkit replacing khtml?" i tell them honestly: it's not been decided yet and there's much to happen before that can happen. you can look over irc logs from yesterday in #kde-devel if you want to confirm that.
now i'm not sure which part over the points aboveyou feel are inaccurate, but to me it seems fairly obvious that if qtwebkit is successful, it will be a good thing (you seem to agree on that) and our users will pick qtwebkit over khtml if they are even remotely comparable. there is serious commitment to making that happen and huge strides forward. the most serious threat to success is stop energy from within.
so ... why am i involved in this at all given that i am not a major contributor to khtml and that it allows me to deal with wonderfully negative retorts? because i was asked to by people who are involved with khtml and webkit. i accepted because this promises to have a huge impact on kde as a whole, something i happen to have a personal interest in. it's not lost on me that the campaign for silence on these matters is a great way to undermine those efforts. you can accuse me of whatever you wish, but i know where i stand, what is actually gong on and i will be sticking to that.
if there are people wish work on khtml as a separate code base from here to eternity, that's obviously perfectly fine; it also doesn't change what happens with webkit. but denying the existence and implications of qtwebkit and the people who are putting their time and effort into it (which happens to include people who did small things like, you know, start the khtml project in the first place) is not what i'd describe as charitable.