Message: previous - next
Month: December 2011

Re: [trinity-devel] A Standalone Konqueror

From: Darrell Anderson <humanreadable@...>
Date: Mon, 19 Dec 2011 12:25:41 -0800 (PST)
> I am aware that it does drag in a hefty bit of
> libraries. Here is a quote from a user who mentioned this on
> reddit today:
> "So? Start with Trinity, strip away
> everything that isn't needed for Konqueror 3
> functionality, and package it? I don't *care* if the end
> result is half a Gig in size - that doesn't matter. The
> functionality does"
> Essentially Konqueror doesn't need the rest
> of tdebase, and most of what it depends on is from tdelibs.
> What it does depend on can be packaged in with
> it.
> Konqueror on my machine pulls in 72 different
> libraries, as a comparison, firefox pulls in at 57 and
> mplayer at 142
>  I think it might be worth
> considering,

A common complaint I read often in reviews is from people wanting to use a sole notable KDE app in a GTK environment is using that one app requires loading several KDE related libraries. Amarok, Digikam, etc. Same complaint will be heard with Konqueror. :)

Of course, I dislike using GTK apps in KDE3/TDE. :)

One of the significant reasons I remain with KDE3/TDE is Konqueror as a file manager. Offering the app as a stand alone is an interesting topic but is the goal worth the effort? People running GTK desktops are unlikely to be motivated. People running GNOME or Unity are unlikely to be motivated. People running KDE4 are unlikely to be motivated.

I'm not against the idea. Just saying the payback might be nominal at best. :)

With that said, as an R15 priority I VERY MUCH would like to see a move toward modularizing TDE. That move would reduce build and debugging issues and could very well help your idea too.