The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
This is not an interview
by Sarath on Wednesday 13/Jun/2007, @09:53
|
I hopped on the arstechnica page to read the interview. The whole article has hardly a line from Knoll - a warning for all those planning to read the interview.
|
[
Reply To This | View ]
|
Re: This is not an interview
by Troy Unrau on Wednesday 13/Jun/2007, @12:00
|
You're right - but I simply borrowed the title from the original article. A more suitable title might be "Reflections on KHTML and Webkit as dicussed with KHTML creator Lars Knoll" or similar. That said, there are still long term benefits to KDE from this announcement.
|
[
Reply To This | View ]
|
Re: This is not an interview
by D Kite on Wednesday 13/Jun/2007, @19:48
|
In what way?
Has the development situation improved since the last time I looked?
Derek
|
[
Reply To This | View ]
|
Re: This is not an interview
by anonymous on Friday 15/Jun/2007, @05:34
|
I don't know when you last looked, but the development situation has improved for KDE developers. We now have a number of TT/KDE developers with commit and review access to WebKit svn. As Lars said in the interview, WebKit is now nearly indistinguishable from a fully fledged open source project. Commit and review access are acquired through the same process as KDE employs. Submit bug reports, patches and generally demonstrate that you are responsible and apply for svn access rights.
There is a small but dedicated group of Trolltech and KDE developers who are working well with the WebKit community right now. Many of the same people who brought you the original KHTML. Simon is even working on a QtWebKit KPart that will be a drop in replacement for KHTML in Konqueror when finished. Lots of interesting things are happening with QtWebKit. Stay tuned!
|
[
Reply To This | View ]
|
Re: This is not an interview
by anonymous on Friday 15/Jun/2007, @15:59
|
let me fix that PR speak for you.
> situation has improved for KDE developers.
situation is identical, but we don't want the soufflé to puff down, so let's post one more of those silly retired-since-four-years-khtml-developer-think-webkit-is-great article and have fake "anonymous" people sing the praise.
> a number of TT/KDE developers
Trolltech is doing all the work.
It is dying to see Qt adopted as the main portability platform for WebKit.
It knows WebKitQt is architecturally limited on X11 because of widgets being sub-windows, but all the same, let's posture as if platform parity is a reachable goal. It's not as if Linux matters in the big picture anyway.
> WebKit is now nearly indistinguishable from a fully fledged open source project.
"Open source" WebKit is a complete marketing stunt.
Apple won't share a bit of control so Nokia forked, Adobe forked, and all Trolltech wants is having fresh and naive KDE developers maintaining that free advertisement for them, so they can have their developers back.
Want a peak into the future? have a look here:
http://www.synack.net/~bbraun/writing/osfail.html
amazing how history repeats itself when profit is in sight!
|
[
Reply To This | View ]
|
Re: This is not an interview
by anonymous on Monday 18/Jun/2007, @07:06
|
"It knows WebKitQt is architecturally limited on X11 because of widgets being sub-windows" ... "Open source" WebKit is a complete marketing stunt."
You have absolutely no idea what you are babbling about, but don't let that stop you.
|
[
Reply To This | View ]
|
Re: This is not an interview
by anonymous on Monday 18/Jun/2007, @17:05
|
"You have absolutely no idea what you are babbling about"
actually *you* seem to have no idea what I'm talking about,
and I'm not surprised given people working on WebKitQt seem to just care about building a backend and have the engine maintained by "other" people, whoever that would be.
Let me check. Since more than a year that you have been unleashing propaganda on the dot and blogs, the only contribution you made to the CSS/HTML/ECMA engine has been
http://bugs.webkit.org/show_bug.cgi?id=11544
a ten line patch that is hopelessly wrong.
No engine on earth, not even MSIE's, is broken enough to render this piece:
<fieldset><legend style="text-align:right">foo</legend></fieldset>
with a right aligned legend except WebKit after your patch.
Well, thanks guys. Great reputation you are making to KDE.
But hey, sorry for the "babbling". Hope you can soon figure what limitation I was talking about, anyway.
|
[
Reply To This | View ]
|
Re: This is not an interview
by George Staikos on Tuesday 19/Jun/2007, @06:32
|
That's really funny that you think that's me posting the comment.
|
[
Reply To This | View ]
|
Re: This is not an interview
by anonymous on Sunday 24/Jun/2007, @07:07
|
what a strange idea. I'm not sure why you'd think that.
The antecedent of 'you' in the bottom half of the message is of course 'people working on WebKitQt', as should be hinted by the latter plural on 'guys'.
|
[
Reply To This | View ]
|
|
Safari
by Martin on Wednesday 13/Jun/2007, @10:43
|
Users: Don't expect any revolutionary improvement if and when Konqueror switches to Webkit. When I got a Mac from my employer, I expected pretty much every site to just work in the Webkit-based Safari. I was surprised to find out that about the same fraction of web sites have problems in Safari as in Konqueror. Not necessarily the same sites, but roughly the same percentage.
I switched to Firefox on the Mac, but I'm still using Konqueror as my primary browser on Linux machines.
|
[
Reply To This | View ]
|
Re: Safari
by ac on Wednesday 13/Jun/2007, @11:40
|
If as you say, the set of sites that work not well in safari is not the same as the set of sites that work not well in konqueror, then it will be a good thing for both mac users as kde users!
|
[
Reply To This | View ]
|
Re: Safari
by anonymous on Friday 15/Jun/2007, @16:56
|
except most sites that work better in Safari compared to Konqueror do so because they sniff the exact browser you are using, and decide to specifically support it or not, no matter what's the underlying engine.
Your "WebKit" browser is not identified as "Safari" on an "Apple" platform?
Be gone, you meaningless < .2% marketshare freak!
Have you ever heard of "Epiphany" in the DHTML development community?
No. Not at all. Not a single word. It doesn't matter that they have full Gecko engine compatibility and are the flagship browser of the GNOME desktop environment, they are just an insignificant also-ran.
Compare that to KHTML, which has full, explicit support from a dozen different DHTML menu providers.
http://www.milonic.com/
http://www.hiermenuscentral.com/
http://deluxe-menu.com/browsers-info.html
http://dhtml-menu.com/tree-examples/tree-menuxp.html
This is what's at stake. Significance in the desktop war.
|
[
Reply To This | View ]
|
Re: Safari
by Andre on Wednesday 13/Jun/2007, @16:09
|
The advantage could be to free ressources.
|
[
Reply To This | View ]
|
Re: Safari
by Petteri on Thursday 14/Jun/2007, @03:40
|
> Don't expect any revolutionary improvement if and when Konqueror switches to Webkit
I thought that Konqueror was not going to switch.
|
[
Reply To This | View ]
|
Re: Safari
by André on Thursday 14/Jun/2007, @04:25
|
If WebKit is KPartified, it would be quite easy to switch. No explicit support from Konqueror needed, AFAIK.
|
[
Reply To This | View ]
|
Re: Safari
by reihal on Saturday 16/Jun/2007, @01:02
|
Webkit is being kparted right now: playground/libs/webkitkde
Stick webkit in Kate and you have a tabbed web browser you can call Katerer.
.
|
[
Reply To This | View ]
|
|
Hmm
by Andre on Wednesday 13/Jun/2007, @12:39
|
The strange thing is how much exposure Apple gets for porting it to windows.
|
[
Reply To This | View ]
|
Re: Hmm
by cm on Wednesday 13/Jun/2007, @13:34
|
Exposure? As in: http://larholm.com/2007/06/12/safari-for-windows-0day-exploit-in-2-hours/
]:-)
|
[
Reply To This | View ]
|
Re: Hmm
by Louis on Wednesday 13/Jun/2007, @18:43
|
Yep, it has amazed me the last two days as the tech "media" has slammed Apple for the bugs in Safari for Windows, even though Apple clearly states, at the point of download, that it is a public beta. Looks like computer-related media would understand what 'beta' means and the purpose of releasing a beta. Great job, nameless security pros! You've uncovered flaws in unfinished software! What a discovery! Seriously, I'm sure Apple thanks you. Sorry for being off topic.
|
[
Reply To This | View ]
|
Re: Hmm
by strider on Wednesday 13/Jun/2007, @23:07
|
The carries for both the Windows beta version and the latest release version for OS-X (Safari 2.0.4 apparently).
For that matter, the professional in question is David Maynor.
|
[
Reply To This | View ]
|
Re: Hmm
by Diederik van der Boor on Wednesday 13/Jun/2007, @23:23
|
> even though Apple clearly states,
> at the point of download, that it is a public beta
Well I've installed the thing, but about every button causes the program to crash. All bold fonts don't render. These are hardly bugs which should be in a beta. It looks more like a pre-alpha release (or random svn snapshot), and Apple is giving Windows users a really bad first impression about Safari.
After 1 minute of clicking around I determined it's totally unusable right now.
|
[
Reply To This | View ]
|
Re: Hmm
by Michael on Thursday 14/Jun/2007, @03:24
|
> Well I've installed the thing, but about every button causes the program to
> crash. All bold fonts don't render. These are hardly bugs which should be in a
> beta. It looks more like a pre-alpha release (or random svn snapshot), and Apple
> is giving Windows users a really bad first impression about Safari.
I think this only happens on Non-English Windows installations. On my Windows XP PC at work Safari runs quite stable (I have not encountered a single crash) and also all headlines show up as expected
|
[
Reply To This | View ]
|
Re: Hmm
by mabinogi on Saturday 16/Jun/2007, @23:00
|
I'm sure someone at Apple will apologise to you personally for having deliberately left the security bugs in.
A bug is a bug, the only way to be sure that a release does not contain security bugs is to have already discovered all the bugs - and since the point of a Beta is to uncover undiscovered bugs, then it should be no surprise that some of those bugs are security related.
|
[
Reply To This | View ]
|
|
Gnustep
by Andre on Wednesday 13/Jun/2007, @12:44
|
Can webkit and Gnustep be used to create a mac compatibility layer.
|
[
Reply To This | View ]
|
Re: Gnustep
by fast penguin on Thursday 14/Jun/2007, @04:14
|
WebKit is a fork from KHTML. They are HTML renderers. WebKit is platform independent; it already works on Qt, but integration to KDE4 techs is being worked on.
|
[
Reply To This | View ]
|
Re: Gnustep
by semsem on Friday 15/Jun/2007, @05:45
|
...be used in order to achieve mac compatibility? when webkit is free the logical next step would be *step integration, no?
|
[
Reply To This | View ]
|
|
CoreAnimation
by EMP3ROR on Wednesday 13/Jun/2007, @13:09
|
What is the Qt project which is similar to CoreAnimation?
|
[
Reply To This | View ]
|
Re: CoreAnimation
by Diederik van der Boor on Thursday 14/Jun/2007, @00:29
|
I guess the QTimeLine, QGraphicsView classes and new transformation algorithms (Zack-foo) are the first steps towards it.
|
[
Reply To This | View ]
|
|
KHTML is notoriously underrated
by Michael Daum on Thursday 14/Jun/2007, @03:25
|
As a professional web consultant I am used to work with all browsers out there. I always start development with Konqueror and check FF and IE later. From that perspective I can only say that the _html_ rendering engine of Konqueror, KHTML, is doing a better job than FF and IE. And I am very serious about that.
These are the little things that KHTML simply got sorted out properly where FF and IE suddenly come up quirky. Konqueror does however have some problems in the javascript area which have be ironed out step by step. Things steadily improved and I would very much appreciate going forward on this route instead of throwing out the baby with the bath water. Webkit and Safari is only getting more PR than Konqueror but is not necessarily better.
|
[
Reply To This | View ]
|
Re: KHTML is notoriously underrated
by mean_checker_;) on Thursday 14/Jun/2007, @05:28
|
Your site looks professional indeed but my W3C-checkers tell me that there are some mistakes. Of course you never claimed it to be "valid" (that's what I said or assumed). But is there a reason for keeping it that way (I mean not 100% valid, though perfectly renderable via Konqueror)?
I do not intend to offend! If you got the impression, sorry for that.
HTML
http://validator.w3.org/check?uri=http%3A%2F%2Fwikiring.de%2FPublic%2FWebHome
Links
http://validator.w3.org/checklink?uri=http%3A%2F%2Fwikiring.de%2FPublic%2FWebHome&hide_type=all&depth=&check=Check#results1
CCS
http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwikiring.de%2FPublic%2FWebHome&warning=1&profile=css21&usermedium=all
|
[
Reply To This | View ]
|
Re: KHTML is notoriously underrated
by superstoned on Thursday 14/Jun/2007, @10:31
|
I haven't looked into the specifics, but it's very well possible (some of) these 'bugs' are needed to get IE working with the site?!?
|
[
Reply To This | View ]
|
Re: KHTML is notoriously underrated
by mean_checker_;) on Thursday 14/Jun/2007, @11:54
|
Sounds reasonable. I do only basic web pages (from templates: www.oswd.org & www.openwebdesign.org ), therefore I have only little knowledge but comments like this are good to learn something. Let's see.
|
[
Reply To This | View ]
|
Re: KHTML is notoriously underrated
by Diederik van der Boor on Friday 15/Jun/2007, @01:34
|
> I haven't looked into the specifics, but it's very
> well possible (some of) these 'bugs' are needed to
> get IE working with the site?!?
The underscore hack is quite tricky, any browser with parsing errors could pick it up too. He could have used a validating hack instead:
* html <selector here> { ... }
Because IE6 actually thinks there is something above <html> (perhaps the 'document' or <!DOCTYPE>, who knows :) ) Most hacks are simple stuff to attach "hasLayout" to an element. This is a optimization that causes IE's rendering algorithm to skip elements which have no markup. Unfortunately they didn't take some variants into account like padding on a parent element. Often a simple "position: relative" or "min-height: 0" is enough to fix this.
Microsoft fixed these parsing bugs in IE7. They also fixed the "* html" parsing bug, which is not a problem since it renders much more like Firefox. Fortunately for us, there is yet another hack that works:
*+html <selector here> { min-height: 0; }
:-p
|
[
Reply To This | View ]
|
Re: KHTML is notoriously underrated
by blade on Friday 15/Jun/2007, @07:39
|
or use conditional comments
|
[
Reply To This | View ]
|
|
Will Webkit make Konqueror compitable with Gmail?
by Samir on Tuesday 19/Jun/2007, @13:20
|
Since Safari is working with Gmail, does this mean, when Webkit is integrated into Konqueror, that Konqueror will also work with Gmail?
Oh by the way: When can we expect that Webkit is integrated into Konqueror?
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
Posted by Troy Unrau on Tuesday 12/Jun/2007, @10:24