[WebKit-devel] KWebKitPart is in extragear/base now; future plans

[Dawit A]

On Saturday 13 February 2010 10:41:36 Urs Wolfer wrote:
> Hi all!
> 
> Yeah, it's true! We are in extragear now.
> 
> playground/libs/webkitkde and kdereview/kwebkitpart are no more.
> 
> I already notified Albert to move the i18n stuff.
> 
> In the next days or week, I plan do the the first public release. I think
> we should call it 0.9 for now. This release will also include
> translations. With that step we should get more publicity and more
> distributions will start providing packages. This means for us more
> testing / feedback.
>
> I also plan to put the release on kde-apps.org (also useful for the .tar.gz
> download).

Great...Few questions about the release... do you plan to branch and tag any 
of the releases ? I know it is not a requirement for extragear, but I think we 
need some sort of branching and tagging to simplify the distro packagers life 
? Do you also plan to label any release announcements as beta or rc until we 
get sufficient feedback to fix/address issues encountered from the larger 
testing ?

I also think it is time for us to establish kdewebkit specific irc channel, 
perhaps #kdewebkit ?? I am sure more and more applications will start using 
either kdewebkit and kwebkitpart once the stable releases come out and that 
warrants creation of a channel dedicated to discussing issues specific to kde 
webkit/webkitpart rather than using generic channels like #kde-devel which 
might be to noisy for this purpose...

One final note... The HTML5 <video> tag will not work for most, actually 
almost all, users because of the phonon packaging mess in Qt/KDE. The phonon 
version in Qt lags the one in kdesupport and does not contain the default xine 
backend required by KDE. As such most distros simply disable phonon support in 
Qt and use the one in KDE. Unfortunately, disabling phonon support in Qt means 
that QtWebKit will not support the HTML5 video tag. The worst part is that it 
seems the issue is only slated to be addressed with the future Qt 4.7 release. 
See https://bugs.webkit.org/show_bug.cgi?id=34631 for the details. Anyways, 
you might want to mention this on the release notes so that we do not get too 
many duplicate bug reports about it.


Regards,
Dawit A.