Do we know what level of accessibility is possible within the current mono framework? Do we know what level of accessibility is likely (e.g. with C# apps ported from other platforms?)
Bill Haneman wrote: > Federico said: > > >> Big tangent: the "GNOME Certification" plan will help in defining what >> is a "good GNOME application" and what isn't. That certification will >> include things like consistent look&feel [insert a lot of handwaving >> about how to quantify this...] >> > > /me points to > Gnome Accessibility Guide For Developers, > http://developer.gnome.org/projects/gap/guide/gad , and > Testing Gnome Applications for Accessibility: > http://developer.gnome.org/projects/gap/testing/index.html > > > Bill > > >> Federico >> >> >> >> ------------------------------ >> >> Message: 5 >> Date: Wed, 19 Jul 2006 01:07:57 +0200 >> From: Philip Van Hoof <[EMAIL PROTECTED]> >> Subject: Re: [Evolution-hackers] Memory consumption and virtual >> machines >> To: desktop-devel-list@gnome.org >> Message-ID: <[EMAIL PROTECTED]> >> Content-Type: text/plain; charset="us-ascii" >> >> On Tue, 2006-07-18 at 16:05 -0500, Federico Mena Quintero wrote: >> >>> On Tue, 2006-07-18 at 14:46 -0400, Jeffrey Stedfast wrote: >>> >>> I've been talking to Philip on IRC, and gave him these requirements for >>> his patch: >>> >>> 1. Don't change the external ABI of Camel, so that Evo needs no changes, >>> *OR* also submit a patch to update Evo for the changed API. >>> >> Achieved >> >> >>> 2. Make sure the summary format on disk works with older Evos without >>> making *them* rewrite the summaries. This is for deployments which have >>> machines with old and new versions of GNOME, but NFS homedirs accessible >>> from any machine. >>> >> Achieved my renaming all the summary filenames >> >> >>> 3. Keep the coding style, variable naming convention, indentation, etc. >>> >> Done >> >> >> For you, attached and on a plate: >> >> o. The patch for evolution-data-server >> o. The patch for evolution-exchange >> >> >> Trying to get this upstream is, for me, saying thank you. >> >> Looking at the patch technically AND testing it (and if it doesn't >> perform, giving me numbers that compare it with the original implement- >> ation) is all I'm asking for. >> >> If Novell wants me to implement unit tests (or other tests) for this, I >> will ask for payment. >> >> -- >> Philip Van Hoof, software developer at x-tend >> home: me at pvanhoof dot be >> gnome: pvanhoof at gnome dot org >> work: vanhoof at x-tend dot be >> http://www.pvanhoof.be - http://www.x-tend.be >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: evolution_data_server__mmap_summary.diff.gz >> Type: application/x-gzip >> Size: 14012 bytes >> Desc: not available >> Url : >> /archives/desktop-devel-list/attachments/20060719/9407295b/attachment.bin >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: evolution_exchange__mmap_summary.diff.gz >> Type: application/x-gzip >> Size: 871 bytes >> Desc: not available >> Url : >> /archives/desktop-devel-list/attachments/20060719/9407295b/attachment-0001.bin >> >> >> ------------------------------ >> >> _______________________________________________ >> desktop-devel-list mailing list >> desktop-devel-list@gnome.org >> http://mail.gnome.org/mailman/listinfo/desktop-devel-list >> >> End of desktop-devel-list Digest, Vol 27, Issue 65 >> ************************************************** >> > > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
