<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<BR> yu loser<IMG alt="" src="http://gfx2.hotmail.com/mail/w4/pr01/ltr/emoticons/heart_broken.gif" width=19 height=19><IMG alt="" src="http://gfx2.hotmail.com/mail/w4/pr01/ltr/emoticons/smile_angry.gif" width=19 height=19><IMG alt="" src="http://gfx2.hotmail.com/mail/w4/pr01/ltr/emoticons/smile_angry.gif" width=19 height=19><BR>> To: kde@mail.kde.org<BR>> From: 1i5t5.duncan@cox.net<BR>> Date: Mon, 21 Sep 2009 17:39:30 +0000<BR>> Subject: Re: [kde] kde4 browser roadmap<BR>> <BR>> Aljosa Mohorovic posted on Mon, 21 Sep 2009 15:30:10 +0200 as excerpted:<BR>> <BR>> > kde4 is now approaching stability of kde3 so i guess it's the right time<BR>> > to ask about kde4 browser roadmap. i'm sure that not everybody will<BR>> > agree but konqueror is not a modern browser although it has excellent<BR>> > integration with kde.<BR>> > <BR>> > i personally believe that browsers are today as important as koffice,<BR>> > pim or any other part of kde.<BR>> > from my point of view there are 2 options: 1. push konqueror development<BR>> > to catch up with firefox, chrome and safari 2. chose firefox or chrome<BR>> > and work only on integration with kde<BR>> > <BR>> > when i say catch up with other browsers i mean: - active development to<BR>> > support html5 - extensions - browser release cycle independent, similar<BR>> > to firefox<BR>> > <BR>> > what do you think?<BR>> <BR>> Umm... you know that the webkit that both chrome and safari use as their <BR>> rendering engine, as well as now qt4 itself, is a fork from kde's own <BR>> khtml, right?<BR>> <BR>> Actually, particularly now that qt4 is including webkit as well, there <BR>> has been serious debate about switching to qt4's native webkit based html <BR>> rendering. Plasma is actually using qt4's webkit engine already, and <BR>> konqueror will probably follow at some point, but it's not going to be <BR>> right away. I'd guess kde 4.6 to 4.8, so 16 to 30 months out, and almost <BR>> certainly requiring at least qt 4.5 if not 4.6 or 4.7 by then.<BR>> <BR>> Beyond that, really, the only way to even have a hope of catching firefox <BR>> in terms of extension support, etc, would be if all the webkit based <BR>> browser folks, safari, chrome, qt, konqueror, band together and agree on <BR>> a common extension format. That's really the only way to get a user base <BR>> anywhere close to large enough to develop the active extension community <BR>> firefox already has. Well, unless they decided to get compatible with <BR>> firefox's chrome (the XML based UI language not the browser) based UI.<BR>> <BR>> As is likely evident by now, I've done some thinking on this myself, in <BR>> addition to following planetkde, etc. I like konqueror's integration, <BR>> but am slowly coming to find the functionality of firefox's extensions <BR>> irreplaceable, thus, find myself gradually switching more and more to <BR>> firefox over time. In my case, it's the noscript and viewscript <BR>> extensions, which make keeping scripting off by default **MUCH** easier <BR>> than konqueror makes it, since about the only way to find the scripts and <BR>> where they are coming from on konqueror is to view-source the page. With <BR>> noscript and viewscript, it's simply a matter of a couple clicks to see <BR>> where the scripts are coming from, and then activating the ones one <BR>> wishes, without having to resort to globally allowing javascript in <BR>> ordered to un-break the page. I also use DownloadHelper for Youtube, <BR>> since I don't have a flash plugin installed, and that lets me download <BR>> the videos for watching using smplayer (for kde4) or kaffeine (for <BR>> kde3). However, others will have their own favorite extensions they find <BR>> they can't live without, and it's simply not even remotely realistic to <BR>> expect the devs to come up with all that variety of features on their <BR>> own, without a wide variety of users contributing as well, and that <BR>> requires a user base of critical mass before it even begins to take off. <BR>> KDE by itself simply isn't there yet, and won't be for the foreseeable <BR>> future, thus my conclusion that the only way to accomplish it would be to <BR>> either get compatible with firefox's extensions thereby eliminating the <BR>> problem, or agree with all the other webkit users on a common webkit <BR>> extension format supported by all of them.<BR>> <BR>> -- <BR>> Duncan - List replies preferred. No HTML msgs.<BR>> "Every nonfree program has a lord, a master --<BR>> and if you use the program, he is your master." Richard Stallman<BR>> <BR>> ___________________________________________________<BR>> This message is from the kde mailing list.<BR>> Account management: https://mail.kde.org/mailman/listinfo/kde.<BR>> Archives: http://lists.kde.org/.<BR>> More info: http://www.kde.org/faq.html.<BR> <br /><hr />Windows Live Spaces je ovdje! Stvaranje osobnih web-stranica je stvarno jednostavno. <a href='http://spaces.live.com/signup.aspx' target='_new'>Provjerite!</a></body>
</html>