faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
questions and musings
by Navindra Umanee on Saturday 11/Sep/2004, @11:41
|
Congratulations on the great hack!
I take it that for the immediate future KDE will provide KHTML as default and Gecko as an "alternative". Are typical Konqueror users expected to know that they can switch from KHTML to Gecko? Or are we expecting that distributors will evaluate the choices and choose one themselves?
What has the Kecko team found so far, is Konqueror with Gecko competitive vs Konqueror with KHTML? I suppose if it is, it only makes sense to defer to Gecko as the default since it has a massive and independent development effort behind it.
Have any distributors expressed an interest in using Konqueror with Gecko instead of Firefox? I suppose the next step would be to get KaXul in Konqueror. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: questions and musings
by Anonymous on Saturday 11/Sep/2004, @11:50
|
> Have any distributors expressed an interest in using Konqueror with Gecko instead of Firefox?
Novell/SUSE has (with Novell Linux Desktop in mind).
|
[
Reply To This | View ]
|
Re: questions and musings
by anon on Saturday 11/Sep/2004, @12:32
|
I think many KDE-default distros will be interested too, as many of them default to Mozilla-browsers or present both a Moz browser and konqueror browser--- such as Mandrake, Knoppix, Linspire, Xandros, mepis,
|
[
Reply To This | View ]
|
Re: questions and musings
by David on Saturday 11/Sep/2004, @18:13
|
With improvements from Apple, I don't see the point to be honest. Firefox is a cross-platform application, not one to be integrated into a desktop.
|
[
Reply To This | View ]
|
Re: questions and musings
by Mike Fedyk on Saturday 11/Sep/2004, @23:56
|
Getting geko to be the standard for open source layout engines helps everyone since you get more eyes looking at a code base instead of their own code.
This just looks like further movement in the goal to merge geko and khtml.
More developers on geko (whether they use gtk and the suite (mozilla) or firefox) is a very good thing(tm).
|
[
Reply To This | View ]
|
Re: questions and musings
by David on Sunday 12/Sep/2004, @09:23
|
Unfortunately Gecko is not better. Why on Earth do you think Apple chose KHTML (and they worked on Netscape/Mozilla!)
|
[
Reply To This | View ]
|
Re: questions and musings
by Anonymous on Sunday 12/Sep/2004, @11:19
|
Because it is easier to maintain and faster (since it wasn't intended to draw itself, and because accuracy wasn't a top preference).
|
[
Reply To This | View ]
|
Re: questions and musings
by oliv on Monday 13/Sep/2004, @00:20
|
In all the CSS support (and correctness) tests I have seen, Gecko is the best. No doubt KHTML is getting close, but I have no good reason to take your assertion as a truth.
Apple chose Gecko because of size and cleaner-coding of KHTML. This is not an issue for the end-user (Gecko browsers such as Firefox are under the 10 MiB). What the end-user wants is good rendering.
|
[
Reply To This | View ]
|
Re: questions and musings
by David on Monday 13/Sep/2004, @13:19
|
Which is why Apple chose it. Browse backwards and forward between a handful of pages to see the speed difference. Apple needed a rendering engine that gave them a selling point for Safari (rendering speed) that would get IE off Mac. They succeeded. If they didn't think it would render well, they would never ever have picked it over Gecko.
|
[
Reply To This | View ]
|
Re: questions and musings
by brockers on Tuesday 14/Sep/2004, @20:18
|
I am sure for many people Gecko works better, but I have had some aweful luck lately. khtml seems to do a better job on many of the sites I visit. Great hack guys, but for now I will stick to khtml.
Bobby
|
[
Reply To This | View ]
|
Re: questions and musings
by Boemer on Thursday 03/Mar/2005, @03:53
|
The advantage of this integration, is that in the future you can use gecko rendering engine with native KDE components. Just like under MacOSX, when they use Safari, everything looks OSX native, just like firefox under windows. But when I firefox on linux or OSX, the buttons all look strange (or primitive).
For MacOSX the camino project is a good start, but for what I mostly need it. It is the designmode option in Gecko, so you can edit like RichText in your browser. That works with Mozilla & Firefox, but not yet with Camino.
And it AT THE MOMENT certainly doesn't work with KHTML. I know there is someone who has been working on it for the last two years, but it still isn't finished, and even when it is finished, it will take some time, for someone to build a script that supports RICHTEXT editing in MSIE & GECKO & KHTML.
I would like to see firefox with KDE look & feel, and also firefox with MacOSX look & feel.
I think that would be a win for all plattforms. I do not really like Konqueror for webbrowsing, probably because I'm used to the shortcuts for firefox, they are mostly the same under windows and linux.
And JavaScript handling for gecko and KHTML still isn't 100% the same, so I still have to test and improve the script under KHTML, after that it works for GECKO & MSIE. But I have to say, that correcting a script after it has been made to work for GECKO is much easier, than correcting it to work for MSIE!
|
[
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)
