trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: November 2011

Re: [trinity-devel] qt3-webkit

From: Kristopher John Gamrat <chaotickjg@...>
Date: Sun, 27 Nov 2011 21:08:07 -0500
On Sunday 27 November 2011 08:34:16 pm Luke Kenneth Casson Leighton wrote:
> On Mon, Nov 28, 2011 at 1:00 AM, Robert Xu <robxu9@...> wrote:
> > On Sun, Nov 27, 2011 at 19:54, Luke Kenneth Casson Leighton
> > <luke.leighton@...> wrote:
> >>
> >>  hmm... qt3 doesn't have a qtwebkit object, does it?  ... would you
> >> like one? *waggles-eyebrows* :)
> >>
> >
> > *stares for a moment*
> > YES YES YES YES YES ;)
> 
>  hehe.  i'm the maintainer of pythonwebkit -
> http://www.gnu.org/software/pythonwebkit - i've kinda been looking for
> an excuse to update it and also add "proper" python-qt DOM bindings.
> you would not believe how unbelievably slow and how much memory
> qtwebkit uses under qt4.  at least double what anything else is.
> 
> so i'm just throwing ideas out, at this stage.  but, if i use the
> pythonwebkit port of webkit, full python bindings to the entire DOM
> model - as if it was javascript not python (just exactly the same
> function names, properties and object names) - get thrown in "for
> free".
> 
>  what sort of doors would that open up, for people, if qt3 - and kde -
> had both a qtwebkit widget, as well as full python bindings to the DOM
> model?  (caveat: i can't get you full c++ DOM bindings to webkit,
> because the python bindings are "direct" i.e. they do *not* go via qt
> objects.  at all).

You don't need to worry about KDE. TDE is (obviously) completely different from KDE4, and some of the code base has been altered from KDE3 to accomodate TQt.

As for what it would open up, lots. We'll finally be able to get rid of the broken KHTML in Konqueror with minimal effort. We'll also be able to write new Qt3 browsers, or even backport newer Qt4 browsers to Qt3 (though I doubt that will happen). That will definitely allow further development of other Qt3 software that depends on outdated HTML rendering, and also further opens Qt3 to developers who wish to continue using Qt3.

All of these things allow for an increase of Qt3 applications for end users. Since TDE uses Qt3/TQt as it's base, that will allow for fewer libraries and more consistent theming, and easier integration into TDE if so decided.

-- 
Kristopher Gamrat
Ark Linux webmaster
http://www.arklinux.org/

Attachments: