Message: previous - next
Month: January 2013

Re: [trinity-users] EXE GNU/Linux distrowatch

From: Calvin Morrison <mutantturkey@...>
Date: Thu, 24 Jan 2013 17:56:08 -0500
I suggest using webkit. It is same, simple, and used all over. I spent
a little bit of time working with it in GTK and it was a pleasure.
There are non-hacky   qt libraries to use webkit with, so I think it
is the obvious option.

On 24 January 2013 17:45, Alexandre Couture <ac586133@...> wrote:
>> <snip>
>> I do understand your concern. I will not be replacing any TDE component
>> that is still superior to its KDE counterpart; for a KDE component to be a
>> candidate for replacement it must:
>> 1.) Provide all the functionality and configurability of its TDE
>> counterpart
>> 2.) Be better than its TDE counterpart in at least one respect
>> (performance, stability, compatibility with new file formats, etc.)
>> 3.) Not use an appreciably higher amount of CPU or RAM, even in non-GPU
>> accelerated rendering modes
>> 4.) Not drag in any system services or libraries which violate Point #3
>> above; this intrinsically excludes the entire KDE PIM suite due to the
>> bloated indexing services required for operation
>> The only items that I am aware of that might fit this list of criteria are
>> kwin, a handful of kcontrol modules, and possibly some smaller KDE
>> applications such as Okular. kwin is my current focus, and so far seems
>> to work very well without increasing the memory or CPU footprint. kwin
>> also satisfies Point #2 above by presenting a much smoother action in high
>> resolution TDE sessions when compared with twin due to its integrated
>> compositing engine.
>> Mozilla has explicitly stated that it will not support embedding Firefox
>> sessions in any third party application, and has removed all programming
>> hooks needed for doing so. This leaves TDE with three long-term options:
>> 1.) Use Webkit (preferred)
>> 2.) Investigate embedding a Chromium instance
>> 2.) Completely remove the KHTML kpart (not recommended)
>> I would prefer to embed a Webkit browser kpart, as I expect website
>> compatibility with Webkit to increase in the future, and a full-featured
>> Webkit widget already exists.
>> Now that some KDE components are finally stabilising and becoming true
>> replacements for their KDE3 counterparts, we should be attempting to
>> reintegrate this new and improved technology into TDE where appropriate.
>> Thoughts are of course welcome on these topics!
>> Tim
> Galeon is an example of non-mozilla browser using Gecko as a core and on the
> wikipedia page of gecko, there is a list of other browsers using it:
> There is even a gecko render module for wine that is used for windows
> programs who needs web rendering.
> I know that they are talking about separating apps from the big kdelibs for
> kde5 and qt5, which is already released, and it will probably help a lot,
> but for now, does using apps like Okular or kwin involves loading the big
> kdelibs?
> -Alexandre