[kde-linux] State of Konqueror ?

Richard cms0009 at gmail.com
Thu Jan 17 21:16:08 UTC 2008


On Thursday 17 January 2008 3:44:57 pm Kevin Krammer wrote:
> On Thursday 17 January 2008, Richard wrote:
> > Well, after reviewing Dolphin the new file manager for KDE 4, and Firefox
> > 3 Beta3.  I could not help but think?, there must something serious wrong
> > with Konqueror...
>
> Not that I am aware of.
>
> > Well, I don't understand why the KDE group would need dolphin?
> > there is Krusader!, if one is needed more.
>
> I don't know Krusader to well, but I think it also targets a different
> group of users than the one Dolphin is mainly intended for.
>
> Dolphin started as a proof-of-concept to demonstrate technologies and
> techniquies for making common file handling task more obvious, easier to
> understand, etc.

I never thought of that when I first started using KDE,
after dumping windows...

>
> It is targeted at users who are not so comfortable with the usual way most
> of us others have grown accustomed to, e.g. split view, detailed about the
> file itself (permission, etc), but rather prefer to have the content
> outweight the system's view, e.g. having documents separated by content
> type rather than file properties.
>

Again, Konqueror can do that, and more... and if they add more options,
it could kill the older Midnight Commander.

> > I think IMHO there must be a serious issue with Konqueror, and that is
> > why they have not chosen to FIX Konqueror... maybe it would take to much
> > time to fix Konqueror... and its easier to come out with with newer
> > product ?
>
> I personally don't think there is a need to "fix" Konqueror, it works the
> way I expect a file manager to work and I prefer having it available
> instead of getting its behavior changed. After all the current groups of
> users will still be users after the newly targeted group gains access to
> the platform and it might not be a good idea to turn them away by removing
> something they like.
>
> Additionally the way things are implemented makes it easy for the two
> development teams to share functionality, actually they even have quite
> some overlap in personnel.

As a file manager is works... but they could add more features .

>
> > as a file manager, its great!!, sure they could add more options,
> > meta-data mouse overs...etc and its very mature, piece of software,
> > compare to Dolphin.
>
> Exactly, therefore ripping out things from Konqueror and replacing them
> with totally new code doesn't sound like a good idea.

Well, if the Older Code, is in from past, but acting like a brick wall,
then remove the brick wall... IMHO, and add something that can be easily 
upgraded


>
> > as a Web Browsers, as of late... it dieing a slow death...
>
> Quite contrary. Its renger engine, especially in the form of webkit, is
> starting to become available on all sorts of platforms, from the usual
> desktop software to embedded devices and smart phones.

Webkit, second time I heard of this... but its NOT in place now?
so, the problem is that Konqueror did not pass the Acid Test 3,
it crash and burn... firefox 3 beta 3 got over 60
the lack of development on Konqueror scares me.



>
> > first Adobe Newest Flash plug-in FAILS to work with Konqueror, there are
> > numerous reports, on launchpad about this.
>
> True. It is really a pitty that proprietary software vendors like Adobe
> switch to incompatible API version within the same major version.
> Compatability is something they regularily demand from the platform
> developers, but incidents like this show nicely that they do not intend to
> do it themselves when others rely on it.

But, You and I know this, that the proprietary software MFG, will continue to 
do so... flash, gmail..etc (hence) the new code, could help to fix those 
untimely changes quicker!, Where the MFG has done wrong, where is not to OUR 
Standards (Linux Group)


>
> Fortunately the user experience is important to the free software
> developers and so they changed their applications accordingly during their
> maintenance phase, where one usually keeps from changing functionality and
> concentrates on fixing bugs.

Yes, on the Bugs fixes... but if the Devel, does not keep with the MFG,
when they changing there base code, then the WHOLE project could come to a 
slow down or do I dare to say, a Stand Still..<yikes>


I gone back to school, to learn Java,
threw and threw.. hopefully soon I could offer something to the Linux Group

Rich





More information about the kde-linux mailing list