2009/5/4 Xan Lopez x...@gnome.org:
On the accessibility camp, I am sponsored by Igalia to spend as much
time as needed in the 2.28 scope (or beyond) to make WebKitGTK+ meet
all the specified requirements. I've finished and merged most of Alp's
pending patches mentioned in the November 2.26
2008/11/6 Willie Walker [EMAIL PROTECTED]:
For me, one of the most important problems we face with WebKit is its
lack of accessibility support right now. I have a great fear that Alp
may have grossly underestimated the scope of the work. I have some
confidence, however, that the WebKit folks
2008/11/7 Willie Walker [EMAIL PROTECTED]:
It took a very long time to get accessibility support added to Gecko,
and it involved a lot of collaborative work between the assistive
technology and Gecko developers. There is a *lot* of testing that needs
to be done to make sure the implementation
You may already have heard that the WebKit/GTK+ developers have been
exploring options for a release cycle. Here I'm going to outline our
plans in a little more detail.
WebKit/GTK+ is a community sub-project maintained mostly by GNOME and
GTK+ developers. It's implemented directly on top of
John Stowers wrote:
For example, the new shiny HTML5 client db stuff in webkit [2] will go
some way to allowing desktop apps to be written in HTML/JS and then
run inside a light webkit shell, but can we do better. What about
* A simple way to start a webkit browser widget associated with a
Hey,
I noticed we missed managed D-Bus[0] in the list of external
dependencies for 2.21. It's used pretty extensively by Tomboy which is
in the core desktop module, as well as a handful of other applications
like F-Spot, last-exit and Banshee.
Module Version# Download
--
Richard Hughes wrote:
- Are the current drawbacks of using autotools in GNOME so so so
annoying that it would be really worth the effort of migrating to
something else?
Well, I just copy and paste chunks of code in configure.ac from other
projects, changing the names of constants where
Ross Burton wrote:
On Mon, 2007-10-29 at 18:44 +0100, Jan de Groot wrote:
since last upgrade of my arch, the gnome-keyring didn't work anymore.
When launching the gnome-keyring-manager tool, it told me, that no
keyring daemon was active, and the following message was shown on the
console:
Alexander Larsson wrote:
On Mon, 2007-02-12 at 10:27 +, Rob Taylor wrote:
Alexander Larsson wrote:
I don't like using dbus-glib-1. That is an ABI unstable library that we
don't want to use at this level of the stack. (It would make all gnome
apps depend on an unstable library...) The way
Robert Love wrote:
There is both a daemon and a client? Explain.
The daemon is desktop-agnostic. It requires glib, HAL, and DBUS. It
runs as root, at the system-level, and enforces no policy, stores no
settings, and maintains no state across sessions.
The client, conversely, is
10 matches
Mail list logo
