Re: Proposed external dependency: WebKit/GTK+
- From: Luca Ferretti <elle uca libero it>
- To: Alp Toker <alp atoker com>
- Cc: Willie Walker <William Walker sun com>, desktop-devel-list gnome org, Frederic Peters <fpeters 0d be>
- Subject: Re: Proposed external dependency: WebKit/GTK+
- Date: Sat, 08 Nov 2008 14:29:21 +0100
Il giorno sab, 08/11/2008 alle 00.11 +0000, Alp Toker ha scritto:
> 2008/11/7 Willie Walker <William Walker sun com>:
> One more thing -- action point 0: It's high time to unblock the GNOME
> WebKit dependency situation. Good accessibility is central, but we
> also have a reputation for stability and internationalisation in
> GNOME.
About non a11y-stuff in WebKit, you could also consider:
* publish targz on ftp://ftp.gnome.org/pub/gnome/sources/
* send email with news to announce mailing list
* put developer docs (API refs with gtk-doc and other, if any) on
http://library.gnome.org (is the gtk-doc support still pending?)
* provide a basic "test suite" for real world, i.e. build WebKit,
go to a site/page/html, compare rendering (webkit vs gecko)[1],
report it
About l10n/i18n, what's the plan? How many strings will webkit mark as
translatable? the inspector too? And how can translators provide PO
file? In GNOME, translators can directly upload po files on svn, but I
don't think this approach is good for webkit. Something like
launchpad.net?
Finally, could we have a little summary of changes between 1.0.1 release
and current trunk, as well as missing features (a11y apart) needed for
good web browsing experience (plain html rendering semms fine to me in
devhelp and yelp)? While, of course, a lot of stuff should be
implemented and managed in Epiphany (https, cookies, ...)
[1] for example, there are some visual issues in Transmission bittorrent
client web interface (bug #20157) or the javascript animation on jimmac
homepage (no yet reported).
> To achieve all three of these goals in time for release, we
> need to stop putting out old tarballs from 2.24 and start making
> development snapshots from trunk.
Currently in jhbuild WebKit is grabbed from git mirror on debian, about
400 MiB on first fetch
External deps should provided as released tarballs, to make distributors
happy. But, nobody will say to not provide a new weekly release and use
it.
This is the way in the previous GNOME releases was managed gtk-vnc and
swfdec-gnome deps... and will save a lot of space on my harddisk ;)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]