Re: Proposal: (No?) email client for Ubuntu 17.10
On Wed, Apr 19, 2017 at 06:07:16AM AEST, Jeremy Bicha wrote: > If we do include an email client, which one? > > Thunderbird (TB) This is the most usable from a screen reader accessibility point of view. Evolution is getting there, but still has some work needing to be done. Not sure about the other options proposed in this thread, although electron apps are not accessible either. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Translatable strings in custom key files.
Hi folks. I'm using ini-like files for metadata, using the glib key file API to read these files. I'm wanting to implement translation support for some of the keys within the files. All is ok on the code side, using the get locale string calls, but I am wanting to integrate these files into my project in such a way that these strings are in the .pot file for translation. Dispite specifying these files in po/POTFILES.in, intltool-update doesn't act on them. >From doing some research and looking at intltool in more depth, I see I am >able to extract these translatable strings and write header files which >xgettext can use for making a pot file. What I'm wondering is whether there is >a way I can integrate things such that the pot file is generated with these >extra strings from my custom key files, and do it all in a way that will allow >the use of rosetta etc in Launchpad. In short, I have something like this, with the file named profile.manifest.in: [profile] _name=Name of profile, transalatable _description=More detailed translatable description. I've already looked into the various rules that intltool.m4 contains, so can easily adapt something for this situation, my primary concern is automating the translation tempate generatino such that Launchpad gets the pot file or whatever it does to allow translation. Thanks. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Trying to reduce our memory and battery footprint
On Wed, Oct 17, 2012 at 07:06:53AM EST, Ted Gould wrote: So then can we really early (right now) rearrange the desktop startup to start upstart when then start dbus and gnome-session? That would give us the ability to start migrating jobs over to being upstart user jobs over time without having to do all at once (like we have done with SysV Init jobs in system startup). I'm sure when we do this at first it'll cause some regressions with things like a11y, but if we start early we can fix them by release time. If using GTK3 apps, a11y is brought up by Dbus activation from within libatk-bridge, which GTK now depends on. In other words, a11y as of GNOME 3.6 is now always on. There is still a .desktop file in /etc/xdg/autostart, but moving forward this is likely not to be needed, at least by GNOME/GTK2. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Trying to reduce our memory and battery footprint
On Wed, Oct 17, 2012 at 08:38:59AM EST, Luke Yelavich wrote: If using GTK3 apps, a11y is brought up by Dbus activation from within libatk-bridge, which GTK now depends on. In other words, a11y as of GNOME 3.6 is now always on. There is still a .desktop file in /etc/xdg/autostart, but moving forward this is likely not to be needed, at least by GNOME/GTK2. Correctino, that should be GNOME/GTK3. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Unity-design] Fwd: What do we do with the file manager?
On Thu, Aug 09, 2012 at 10:54:25PM EST, Sebastien Bacher wrote: Le 09/08/2012 14:50, Georgi Karavasilev a écrit : The three things that Marlin misses are: A) Stability B) Split screen (multiple panes) ... maybe? C) Ability to draw the desktop' (e.g. desktop icons, right click on desktop - context menu) I believe (could be wrong) that those can be solved for 12.10 if the work starts soon enough. Ubuntu one integration as well Is it written in GTK? If not, assistive technology use/accessibility is also a concern. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Gstreamer version to use in 12.10?
On Mon, Jul 23, 2012 at 09:53:38PM EST, Sebastien Bacher wrote: Hey everyone, GNOME said they would try to update their code to use gstreamer 1.0 in 3.6: https://live.gnome.org/GnomeGoals/PortToGstreamer1 I think there is a couple of issues there: - GNOME doesn't give any guarantee it will be done, it might get half done for 3.6 since it's a best effort basis and having to ship 2 gstreamer versions wouldn't be a stopper for them - gstreamer 1.0 is not released yet (gstreamer 0.11.9x candidate versions are available though and packaged in precise,quantal universe) - gstreamer 1.0 is virtually untested - if we don't want to ship 2 gstreamer stacks in quantal we will probably have to port some of our code to the new version (ubiquity, ubuntuone?, ...) as well as help GNOME to finish porting their softwares - there are no fluendo codecs available yet for the new version (there is an ongoing discussion with them on the topic) Based on that I think we should be conservative and avoid surprise and extra work (especially that we don't have gstreamer hackers here to deal with issues we will find) by delaying the update to next cycle (which probably means staying on current totem and rhythmbox) What do others think? No argument from me. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Accessibility always on in GNOME 3.6.
On Fri, Jun 22, 2012 at 06:25:22PM EST, Sebastien Bacher wrote: So I've read the bug upstream and I'm not sure how they are addressing the performances concerns, is the bottom line there gtk3 has no performance issues, a11y will not be turned on for gtk2 but only for gtk3? If that's the case, what does it mean for gtk2 applications? Do we get part of the desktop accessible and some other parts not? Do firefox and libreoffice use enough gtk to rely on the a11y to be turned on in gtk2 to be accessible in an usable way? With regards to performance, upstream knows that there are still issues. If one is running an assistive technology like Orca, and opens a directory with a large number of folders and files in it using nautilus, there is currently a performance hit when the directory is opened, because nautilus/gtk/atk has to iterate through all of those entries, and create atk objects to associate with the GTK widgets in the icon view. How that will be solved long term I don't know, but the client tracking by atk and at-spi has been implemented to work around issues like the above. The only change to the GTK2 module is to be linked against the new libatk-bridge library, which will do all the heavy lifting. The module still has the same symbols that it has always had. The only slight difference is that the GTK2 atk module will get loaded every time, assuming the GTK_MODULES environment variable is set or gnome-settings-daemon tells GTK the list of modules it should load. I think the libatk-bridge library has the smarts to go no further if it can't find the at-spi bus but even then, the same assistive technology client tracking comes into play as above, so no events will be emitted if there is nothing listening for events. Out of those questions I'm fine with follow upstream's lead there, we should just make sure it lands early so we have time to test and have a plan B to disable it again by default if that turns out creating too much issues. It will land this week, and I should have the new libatk-bridge library packaged and ready to go in the archive by the time you and Jeremy get to updating GTK and gnome-shell, at least in source form. It will have to go through binary new due to new binary packages being added. Plan B will essentially involve reverting patches in GTK, GNOME shell, and at-spi2-atk to return to the previous behavior. I am pretty sure the gsettings key will stay around at least for now, and may or may not go away in future cycles depending on how well this a11y always on test works out this cycle. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Accessibility always on in GNOME 3.6.
Hey folks, So some of you who watch the goings on and discussions in GNOME upstream may have noticed this bug(1) and the surrounding discussion about enabling accessibility everywhere in GNOME 3.6. I've decided to start this thread for 2 reasons, first, a heads up that this is coming in both GTK 3.5/3.6, and GNOME shell 3.5/3.6, i.e the required changes to support this have been made in git master for both projects. THe second reason is to start a discussion as to whether we want to carry this, or revert the change and stick to what we have in precise, i.e enable accessibility with a gsettings key. I would like to go with upstream on this change because it allows us much more flexibility in how we can offer accessibility profiles, and it opens up an avenue to create a system upstream to allow projects/organisations and individuals to develope and use their own custom accessibility profiles. There are also recent changes made to make sure there are no performance degredations for the desktop if no assistive technologies are running. In other words, you won't see any slow down in nautilus or other apps that have a lot of GTK widgets in tree views/icon views, unless Orca or some similar technology is running. The other upshot is that it allows anybody to use accerciser or other tools to quickly check their application for accessibility compliance, without having to do the gsettings log out and log in dance to get it enabled. Yes we could revert things and go back to how things were, but it will be harder to carry sed patches in the future, and patches will need to be carried on several packages, at-spi, GTK, and GNOME shell, and maybe even clutter at the least. I welcome further thoughts and discussion. If we decide to carry these changes from upstream, I'll make sure relevant patches are sent to our own projects, unity et al to work with these new changes, and will make sure to have the new atk-bridge library available ASAP when it is released, since GTK and GNOME shell will depend on it. Luke (1) https://bugzilla.gnome.org/show_bug.cgi?id=677491 -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: a dream
On Sun, Jan 29, 2012 at 07:57:33AM EST, Pedro Bessa wrote: steps to reproduce 1. not all keyboards have a Super key, so using a keyboard that has no Super key, hit Super For keyboards that don't have a super key, pressing Alt + F1 then enter will load the dash, since the dash is the first icon on the launcher. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Desktop12.04-Topic] GNOME Version for the LTS
On Fri, Oct 14, 2011 at 12:45:12AM EST, Sebastien Bacher wrote: That would put us in a position where we can upload at least glib and gtk, then we need to figure what we do with GNOME 3.2 against 3.4. If we have an updated stack I would lean toward stay on 3.2 by default, then we can maybe update selected components and use the ppa for other things THis is good news. Newer GTK to me always means at least some accessibility fixes, and given my previous topic about accessibility for Precise, accessibility fixes from infrastructure package updates == win for me. I also plan to update at-spi2 to whatever is latest in GNOME, as fixes in this piece of infrastructure don't impact anything outside of accessibility consumers, i.e Orca, accerciser, etc. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Desktop12.04-Topic] Accessibility pollish.
On Wed, Oct 05, 2011 at 05:07:08PM EST, Didier Roche wrote: Can we add to the list installation and setup process? I had met some people with disabilities during the RMLL in France (French FLOSS event) and tried with them ubiquity, + setup Orca + magnification and I clearly saw that it's was quite buggy and not really helpful when you don't know all the shortcuts. This kind of tracking would be helpful. I have a full detailed list of issues we got. Great to hear, I'd be very interested in having a look at that list, as I am interested to see what you found. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Desktop12.04-Topic] Video playback?
On Wed, Oct 05, 2011 at 06:41:17AM EST, Jeremy Bicha wrote: On 4 October 2011 14:49, Sebastien Bacher seb...@ubuntu.com wrote: We probably don't want to switch video players in a lts cycle but not sure if we should go with the new version (we staying on 3.0 which still uses xv for Oneiric). Clutter-gst might introduce issues (vblank was mentioning as a potential issue with compiz during this cycle when we discussed it), not sure how much it got tested on i.e armel or how much it could be an issue on some video drivers... Should we go for the new version and deal with issues or stay safe with the old version using xv, or look for a different video player to use? Banshee plays videos too. Banshee git just got DVD support so maybe we can use one app for music videos. Because it's new, DVDs probably don't work as well in Banshee yet but maybe it'll be fine once it gets more testing and use. I am of the opinion that we should allow users to play back video separate to their media library, should they choose to do so. This is possible on OS X with Quicktime Player and iTunes. I know if I want to look at a video thats not in my library or from a podcast, its much easier to find the video in Nautilus and open with totem. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Desktop12.04-Topic] Accessibility pollish.
Hey folks, Since Unity has been introduced, many strides have been made with accessibility. Unity 3D is approximately 80% accessible, so far as official oneiric packages go, and unity-2d is 99% accessible, thanks to the great work from the QT a11y folks, and the unity-2d developers. Both are likely to be 100% accessible for the LTS, which is great. However, they are not the only areas of accessibility that need improving. I have already started making a work item list of issues to address, to give the desktop more pollish when it comes to accessibility. Such issues include: * Making sure all indicators have accessible descriptions/labels. * Making sure any icons in indicator menus that need accessible descriptions/labels have them, a prime use case is network manager, to indicate wireless network strength. * Further pollish on Ubiquity's accessibility, particularly selecting a timezone. * Connecting up the rest of the accessibility profiles in the ubiquity a11y indicator. * Further pollish of the unity greeter accessibility experience. * Make sure the accessibility experience between unity 2d and 3d is the same. The list I have is slightly more technical and goes into more detail, but what is listed above is the gist of what I have. Whether this needs a session at UDS I don't know, but a blueprint will likely be needed for work items tracking. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Ubuntu-desktop nautilus packaging branch.
Hi, When working on the nautilus package today as a part of patch pilot, I tried commiting a release and tagging with the appropriate version in debian/changelog, however bzr complained that there was already a tag for that release version. I didn't overwrite it in the lp branch in the event that there was a reason for this, so the latest nautilus package release, so far as the branch goes, is not tagged. Luke -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
