Re: Get information about Compiz
MENGUAL Jean-Philippe wrote: > Hi, > > How can I know the latest release of Compiz? I see on launchpad 0.9.11 > and 0.9.12, I cannot determine the current released one. Besides, can I > be notified when a new release is done? I hope, from this, to download > .orig and .dsc to see the packaging rules. Assuming that you have a reasonably normal system you will get security updates automatically. I have Compiz 0.9.7 on Ubuntu 12.04. If you want a newer version; start with a newer verison of Ubuntu, enable backports, maybe add an untrusted PPA from Launchpad. If you are despirate for the latest and the greatest you will have to get involved with development - and be prepared fro breakages. > In parallel, how can I do this for Emerald? It's in a PPA but how can I > know the official !elease and be notified of the release? > > Regards, Have you looked at all of the configuration options in your sofware updater? -- blind Pete Sig goes here... -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Get information about Compiz
Hi, How can I know the latest release of Compiz? I see on launchpad 0.9.11 and 0.9.12, I cannot determine the current released one. Besides, can I be notified when a new release is done? I hope, from this, to download .orig and .dsc to see the packaging rules. In parallel, how can I do this for Emerald? It's in a PPA but how can I know the official !elease and be notified of the release? Regards, -- Jean-Philippe MENGUAL accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels Mail: te...@accelibreinfo.eu Site Web: http://www.accelibreinfo.eu -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
MATE & Compiz
Hi, I tried Compiz on Ubuntu 14.04 with MATE. To make it effective, I believe that I need fusion-icon. But on a 64bits system, when I run fusion-icon, it segfaults. Have you heard of this? A solution? Regards, -- Jean-Philippe MENGUAL accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels Mail: te...@accelibreinfo.eu Site Web: http://www.accelibreinfo.eu -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Compiz
On Mon, Aug 04, 2014 at 03:34:46AM EST, MENGUAL Jean-Philippe wrote: > Hi, > > Does Ubuntu has a prospective about Compiz? Is it maintained? who maintains? > My project is packaging it for Debian, and making it work with MATE or > making all its features work with Unity for low-visual impaired people. > > Ideas about the status of Compiz? Longer term, Ubuntu will be dropping the use of compiz, once the rewrite of unity in Qt for both mobile and desktop is complete. Luke -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Compiz
Hi, Does Ubuntu has a prospective about Compiz? Is it maintained? who maintains? My project is packaging it for Debian, and making it work with MATE or making all its features work with Unity for low-visual impaired people. Ideas about the status of Compiz? Regards, -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [ubuntu-us-ma] [OT] compiz crash on Precise beta from cdimage.ubuntu.com/dailylive/current
You're right, The best place to report this issue is on launchpad, the best place to bring the issue up as important is the ubuntu developers mailing list. Martin, On Fri, 2012-03-09 at 14:55 -0500, Dave Hunt wrote: > What is a better place to report this? When trying to start my copy > of > the subject release, from a thumbdrive, I got error messages about > compiz unable to start, and could not get past them. Note: I use > orca > for accessibility, and could not get it speaking; messages > paraphrased > from having someone read the screen. Is the compiz issue a known > problem with today's daily build of Precise Desktop 32-bit Edition? -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[OT] compiz crash on Precise beta from cdimage.ubuntu.com/dailylive/current
Hi, What is a better place to report this? When trying to start my copy of the subject release, from a thumbdrive, I got error messages about compiz unable to start, and could not get past them. Note: I use orca for accessibility, and could not get it speaking; messages paraphrased from having someone read the screen. Is the compiz issue a known problem with today's daily build of Precise Desktop 32-bit Edition? -Dave -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Ubuntu 11.10, Unity, and Compiz eZoom
Hello again. I was unsure as to whether or not I should create a new thread or follow-up on this one, so I decided to play it safe and follow-up. I installed gnome-shell in my virtual machine (Ubuntu 11.10). At the login screen, I was presented with session options for GNOME, Classic GNOME, Classic GNOME (No Effects), Ubuntu, and Ubuntu2D. it seems that I cannot use screen magnification in GNOME or Classic GNOME. It did not even seem as though Compiz was running (I am not sure how to confirm this). However, when I run "compiz --replace" in the Run Applications dialog, the Unity dock appears and zooming seems to work (with the exception of the Unity dock). I'm a bit distraught as I have no idea what to do. Thanks for any suggestions and input. On 10/05/2011 12:36 PM, Robert Cole wrote: Hello, everyone. Sadly, I must report that this magnification issue persists in Ubuntu 11.10 as well. I tested this under a virtual installation of Ubuntu 11.10 with 3D Acceleration enabled. I am going to try to install gnome-shell on the VM and see if it works any better for me. I know that the needs of all users cannot always be met at first, and I am appreciative of all of the hard work which is being put into Unity, but I'm feeling left out right now. :( Sorry. I don't mean to whine or to complain. Hopefully this will change in Ubuntu 12.04, or better yet in an update to Ubuntu 11.10. I just wanted to write back and to confirm that this still persists in case there is anyone else out there who was curious. Take care. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Ubuntu 11.10, Unity, and Compiz eZoom
Hello, everyone. Sadly, I must report that this magnification issue persists in Ubuntu 11.10 as well. I tested this under a virtual installation of Ubuntu 11.10 with 3D Acceleration enabled. I am going to try to install gnome-shell on the VM and see if it works any better for me. I know that the needs of all users cannot always be met at first, and I am appreciative of all of the hard work which is being put into Unity, but I'm feeling left out right now. :( Sorry. I don't mean to whine or to complain. Hopefully this will change in Ubuntu 12.04, or better yet in an update to Ubuntu 11.10. I just wanted to write back and to confirm that this still persists in case there is anyone else out there who was curious. Take care. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Ubuntu 11.10, Unity, and Compiz eZoom
On 09/30/2011 03:01 PM, Mackenzie Morgan wrote: > > Getting the gnome desktop requires manually installing it. Unity 2D, > as you can guess by the name, does not use Compiz,.though. > > Maco > Good point, I didn't realize the issue of the manual installation. One option is start a shell, and install it manually. Although of course, this is not really user-friendly. Yes, Unity2D doesn't use Compiz, and AFAIK, it doesn't have a built-in magnification feature. Thanks for the clarification. BR -- Alejandro Piñeiro Iglesias -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Ubuntu 11.10, Unity, and Compiz eZoom
On 09/29/2011 06:57 PM, Robert Cole wrote: > Hello, everyone. > > I do not have a test machine here at home, so I am not able to try > this for myself as I would like to. > > In Ubuntu 11.04, the Compiz eZoom plugin would only zoom in to the > desktop, but the Unity dashboard/dock would not change; they would > stay zoomed out. Does anyone know if this has changed in Ubuntu 11.10, > as I would really like to upgrade to it when ti is released. But I do > not want to do the upgrade if it will not be accessible to me. > > Thanks for any input heer. It will be much appreciated. > I didn't test it, but unfortunately, the bug opened at launchpad is still open: https://bugs.launchpad.net/unity/+bug/781529 Anyway, take into account that although Unity is the default desktop, AFAIK, you still can choose the old GNOME desktop, like in Natty (11.04). PS: Importance on that bug is still "Undecided". Probably it would be good to add some comments on the bug to comment that the priority should be properly set. BR -- Alejandro Piñeiro Iglesias -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Ubuntu 11.10, Unity, and Compiz eZoom
Hello, everyone. I do not have a test machine here at home, so I am not able to try this for myself as I would like to. In Ubuntu 11.04, the Compiz eZoom plugin would only zoom in to the desktop, but the Unity dashboard/dock would not change; they would stay zoomed out. Does anyone know if this has changed in Ubuntu 11.10, as I would really like to upgrade to it when ti is released. But I do not want to do the upgrade if it will not be accessible to me. Thanks for any input heer. It will be much appreciated. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Keyboard audio feedback and Compiz
Hi Luca, Don't hear any audio feedback, can anyone else confirm this on lucid. Cheers --arky Rakesh 'arky' Ambati| IT Consultant| http://www.braillewithoutborders.org | Blog: http://playingwithsid.blogspot.com - Original Message > From: Luca Ferretti > To: ubuntu-accessibility@lists.ubuntu.com > Sent: Tue, 9 February, 2010 4:59:08 PM > Subject: Keyboard audio feedback and Compiz > > Hi everyone, > > As per bug > https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/514943 > > Here is anybody using a "real" Lucid installation that could check if > the issue still exists? > > Thanks, Luca. > > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/ -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Keyboard audio feedback and Compiz
Hi everyone, As per bug https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/514943 Here is anybody using a "real" Lucid installation that could check if the issue still exists? Thanks, Luca. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Compiz keybinds conflicts
Hi, Mvo promised that this panel switcher problem will be fixed in Lucid, I know that compiz still has some conflicts with application specific keybindings (for example firefox table navigation https://bugzilla.gnome.org/show_bug.cgi?id=578099). Lets work to fix compiz keybinding issues for lucid. :) Cheers --arky Rakesh 'arky' Ambati| IT Consultant| http://www.braillewithoutborders.org | Blog: http://playingwithsid.blogspot.com - Original Message > From: Bill Cox > To: Arky > Cc: ubuntu-accessibility@lists.ubuntu.com > Sent: Mon, 1 February, 2010 9:37:21 PM > Subject: Re: Compiz keybinds conflicts > > Hi, Arky. Someone just pointed out this problem in my Vinux/Ubuntu > Lucid ISO. I turned off "Static Application Switcher", and turned on > "Application Switcher", and reassigned Tab to > next_panel, and Tab to prev_panel. > > The results are awesome. I've been using the Compiz magnifier for > over a year, and I've never been able to access the panels accept with > the mouse. Getting next_panel and prev_panel working in Compiz is > huge. This is the last major accessibility issue I know of with > Compiz. > > I think Lucid would be a good platform to switch to the normal > application switcher, and fixing this key binding should be done as > well. > > Thanks, > BIll > > On Tue, Jan 12, 2010 at 10:17 AM, Arky wrote: > > Hi, > > > > Compiz keybindings often conflit with gnome defaults. Perhaps we can > > provide a > patch to resolve this in lucid. Any ideas? > > > > https://wiki.ubuntu.com/Lucid/CompizDefaults > > > > > > Cheers > > > > --arky > > > > Rakesh 'arky' Ambati| IT Consultant| http://www.braillewithoutborders.org | > Blog: http://playingwithsid.blogspot.com > > > > > > > > The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. > http://in.yahoo.com/ > > > > -- > > Ubuntu-accessibility mailing list > > Ubuntu-accessibility@lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > > Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/ -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Compiz keybinds conflicts
Hi, Arky. Someone just pointed out this problem in my Vinux/Ubuntu Lucid ISO. I turned off "Static Application Switcher", and turned on "Application Switcher", and reassigned Tab to next_panel, and Tab to prev_panel. The results are awesome. I've been using the Compiz magnifier for over a year, and I've never been able to access the panels accept with the mouse. Getting next_panel and prev_panel working in Compiz is huge. This is the last major accessibility issue I know of with Compiz. I think Lucid would be a good platform to switch to the normal application switcher, and fixing this key binding should be done as well. Thanks, BIll On Tue, Jan 12, 2010 at 10:17 AM, Arky wrote: > Hi, > > Compiz keybindings often conflit with gnome defaults. Perhaps we can provide > a patch to resolve this in lucid. Any ideas? > > https://wiki.ubuntu.com/Lucid/CompizDefaults > > > Cheers > > --arky > > Rakesh 'arky' Ambati| IT Consultant| http://www.braillewithoutborders.org | > Blog: http://playingwithsid.blogspot.com > > > > The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. > http://in.yahoo.com/ > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Compiz Accessibility
Hi, Compiz eZoom is wonderful solution for low vision. But using compiz causes numerous problem with gnome desktop keyboard navigation. For instance the compiz application switcher keybindings conflicts with gnome panel switching default 'control + Alt + Tab' With help from #compiz channel member I prepared a patch for this. https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/507964 If you know of other such conflict please bring to my notice or a leave a comment here https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/507962 I hope we can make compiz work together with gnome in next lucid release. Cheers --arky Rakesh 'arky' Ambati| IT Consultant| http://www.braillewithoutborders.org | Blog: http://playingwithsid.blogspot.com The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/ -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Compiz keybinds conflicts
Hi, Compiz keybindings often conflit with gnome defaults. Perhaps we can provide a patch to resolve this in lucid. Any ideas? https://wiki.ubuntu.com/Lucid/CompizDefaults Cheers --arky Rakesh 'arky' Ambati| IT Consultant| http://www.braillewithoutborders.org | Blog: http://playingwithsid.blogspot.com The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/ -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Compiling Compiz from source
On Sat, Jul 04, 2009 at 10:22:17AM -0400, Bill Cox wrote: > Sorry for this newbie package question. > > I am trying to track down some Comiz issues on Ubuntu 9.04 x64 in > communicating with Orca. Compiz is a problem for Orca and it can be simply resolved by removing all compiz-related packages already installed on Ubuntu, doing this will stop with making crash or block Orca at boot time, by me it was stopping with talking at the welcome message (intrepid distro), after I removed all compiz packs I can boot my system and it talks and works again; idem I did the same on the pc of my wife with the same effect. So as blind you don't need compiz, and the best thing to do is removing it asap. Labrador -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Compiling Compiz from source
Sorry for this newbie package question. I am trying to track down some Comiz issues on Ubuntu 9.04 x64 in communicating with Orca. I think I've installed the latest Compiz, as I've added this to my sources.list: ## Proposed deb http://archive.ubuntu.com/ubuntu/ jaunty-proposed main restricted universe multiverse deb-src http://gb.archive.ubuntu.com/ubuntu/ jaunty-proposed main restricted universe multiverse ## Compiz deb http://ppa.launchpad.net/compiz/ubuntu jaunty main deb-src http://ppa.launchpad.net/compiz/ubuntu jaunty main I've build Compiz from source using: sudo apt-get build-dep compiz apt-get source -b compiz This creates a compiz-0.8.2 directory, and builds Compiz with no errors, but lots of warnings. I find it built the executable I'm trying to debug in: compiz-0.8.2/obj-x86_64-linux-gnu/gtk/window-decorator/gtk-window-decorator However, it's only 5,900 bytes, while /usr/bin/gtk-window-decorator is over 90KB. When I run it, it functions properly as a window decorator for Compiz, except that the static switcher then does not work with Orca's hack to work with the switcher. I do not understand why my new gtk-window-decorator is different than the one installed. What should I do to get the most current version for debugging? Thanks, Bill -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: compiz
Hello, Mike. Please try the following and see if it helps things for you. 1) Go to System->Preferences->Appearance to open the Appearance dialog box. 2) Once the Appearance dialog box opens, hit the right arrow key four times to get to the Visual Effects tab. 3) There are (on my system) three visual effects settings in the Visual Effects tab options; these options and how to activate them via the keyboard follow: None (you can hit ALT+N to activate this option) Normal (you can hit ALT+O to activate this option) Extra (you can hit ALT+X to activate this option) Most likely, you will want to hit ALT+N to set the Visual Effects to None. This should set your system back to normal. I hope that this helps you. Please take care. mike wrote: Hi, I turned compiz on by mistake. Does anyone know how to turn it off? The setting I was experimenting with in appearance no longer has any choices since I did this. Mike. -- If you were to die today, are you 100% sure that you would go to heaven? If you are unsure, please read the following plan that God has made for your precious Salvation. 1) We are all sinners, whether we like it or not; sin is something which has existed since the Garden of Eden, when the act of sin was committed by Adam and Eve. The Bible says: For all have sinned, and come short of the glory of God; (Romans 3:23) In order for us to come to the Lord, we must admit that we indeed are sinners. 2) Sin is a very horrible work, and it comes with its wages. The Bible says: For the wages of sin is death; but the gift of God is eternal life through Jesus Christ our Lord. (Romans 6:23) "Death", in the above case, refers to an eternal separation from God and eternal damnation in the "blackness of darkness for ever" (Jude 1:13), also called Hell. God loves all of us, but sin is what keeps us from peace with Him. God is a loving God, but also a just God; thus, sinners who do not repent and believe in God's precious Gift will face Judgment, and then Hell eternal... 3) What is this Gift that is so freely and mercifully given? The Bible states: But God commendeth his love toward us, in that, while we were yet sinners, Christ died for us. (Romans 5:8) Knowing that we would be sinners, a sacrifice NEEDED to be made to establish peace between we and God. God sent His only begotten Son, the Lord Jesus Christ, to be beaten, bruised, and killed by crucifixion on the cross of Calvary--his precious blood being spilled to cleanse those who will simply believe--to be the ultimate sacrifice for our sins. 4) How can one accept this precious gift? Who can receive this precious blessing and peace--an eternal home with God in heaven? The Bible states: For whosoever shall call upon the name of the Lord shall be saved. (Romans 10:13) All that you must do is simply ask the Lord into your heart. Admit that you are a sinner, that you believe that Jesus Christ is the Son of God, and that he died for you to save you from Hell, and to bring peace between you and God. Just pray to the Lord, meaning what you say with all your heart, and with all your mind, and with all your soul, and with all your strength...after this manner... "Dear Heavenly Father, I do realize that I am a sinner, and that I do not have peace with You because of my sins. I believe and I thank you for what Your Son Jesus Christ did for me on the cross. Lord Jesus, I pray and humbly ask you to please come into my heart and save me. I need you in my life, and I need your help. Please Lord Jesus, come into my heart and save me from my sins and from Hell. Thank you, Lord Jesus. Amen." 5) If you truly accept what Jesus Christ did for you, and if you have accepted Him into your heart, you are saved. The prayer does not Save you, but ti is through Jesus Christ and God's divine grace; we must humble ourselves and be thankful for what was done for us. Whatever you do, do not listen to the T.V. or radio preachers or anything else of that matter, but listen to what God has to say from His precious Word--the Bible. Life will not be perfect after Salvation, but you have the assurance that you are just a pilgrim on your way to heaven in your life. No matter what anyone says, you cannot lose your Salvation. Jesus Himself has said: "...and him that cometh to me I will in no wise cast out." (John 6:37b) I pray that whoever of you reads this signature that, if you are not saved, you will come to know the Lord Jesus Christ today. If you make the decision for Christ, please write me and tell me. I would love to know your decision for Christ. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: compiz
On Mon, Sep 22, 2008 at 5:48 PM, mike <[EMAIL PROTECTED]> wrote: > Hi, I turned compiz on by mistake. Does anyone know how to turn it off? The > setting I was experimenting with in appearance no longer has any choices > since I did this. Should be a matter of setting "Visual Effects" in appearance to None. Are you saying this setting is gone? A temporary solution is to start metacity from a terminal with 'metacity --replace'... - Kristian -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
compiz
Hi, I turned compiz on by mistake. Does anyone know how to turn it off? The setting I was experimenting with in appearance no longer has any choices since I did this. Mike. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Orca, AT-SPI and the Compiz zoom project
On 5/1/07, Willie Walker <[EMAIL PROTECTED]> wrote: > > I know pretty much everything I need to know on the compiz-side of > > things, but accessibility is new to me, and I'm hoping for a few > > pointers for where to look for information, or rather what information > > to look for. > > The current API for driving a magnifier is the gnome-mag API. It's a > pretty complex API, and I think there may be opportunity for improvement > with something such as Compiz. From my standpoint (that of a consumer), > the main concepts behind gnome-mag are: > > 1) The magnifier is a system service to be accessed by an assistive > technology (AT). AT's discover (and activate if necessary) the > gnome-mag magnifier and talk to it. > > 2) Each AT needs to write its own configuration GUI for the magnifier. > > 3) The AT tells the magnifier to create one or more 'zoomers', each of > which magnifies an area of the display. Each zoomer can have various > settings associated with it, and the AT can update the region of > interest for each zoomer at any time. > > 4) In use, the AT tells each zoomer to magnify an area of the screen, > typically in response to mouse, object focus, caret movement events, > and/or speech progress. > > With Compiz, I think there's opportunity for the magnifier to be more > autonomous, but continue to offer itself up for interaction with other > assistive technologies. One of the things I wish to accomplish is to let users who otherwise wouldn't use AT's get the benefits of this project. The benefit for the people who truly need this would be that the zoom functionality would receive a lot more attention, both with regards to development time and feedback on features. I can allready do almost everything entirely with compiz' existing functionality; Tracking focus, mouse movement, etc, but the one thing I can't achieve with Compiz alone is caret movement, and the speech progress you speak of. > As a loose analogy to this, one might consider what is done with > BrlTTY/BrlAPI. BrlTTY runs as its own process, providing interaction > with braille displays, most notably for virtual consoles. BrlAPI > provides an interface for other applications to access the braille > display while BrlTTY is running. By default, when Orca detects BrlTTY > is running, it assumes the user wants braille and goes ahead and uses > it. > > Something similar could be done with Compiz. For example: > > 1) Compiz could provide its own sophisticated GUI for the magnifier, > allowing for at least what (and perhaps more than) could be accomplished > with gnome-mag. This UI would also include the ability to > create/destroy/modify new magnifier views of the display. I suspect a > typical use case would be that the user has a main 'dynamic' magnified > region that tracks where they are on the display and 0 or more 'static' > magnified regions that monitor fixed areas on the display. This would > be a HUGE improvement, and would not require all other AT's to write > their own magnifier GUI. Compiz has never had the ability to magnify anything except the entire screen with the zoom plugin(s), so this will be interesting, but shouldn't take too much time. I can imagine a few diffrent attributes for a magnified area; - Comletly static. This would stay focused on the same area, regardless. - Follow focus. - Follow caret/mouse. - Follow both focus and caret/mouse. I imagine writing (or reading) while zoomed in, and then suddenly being thrown to a diffrent area because of focus being a bit of an annoyance. This would allow them to have a generic region to alert them of focus (or new windows, in the case of focus stealing prevention). Since this just occured to me, I haven't thought this out too thoroughly, but it shouldn't be too hard to implement, I'm just concerned with the usability of it. > 2) Compiz itself could more easily provide the support for the various > mouse tracking methods rather than requiring the assistive technology to > do so. I think this is the logical thing to do, specially since the zoom plugin will have to keep track of the mouse for input enabled zoom anyway. In Compiz' case, I don't think it makes any sense to let another application tell it where the mouse is. Compiz knows this better than anything else. > 3) Compiz could expose itself as a simpler service to the screen reader, > with an API that provides mostly hints/recommendations about the area of > the screen to magnify. One would need to engage end users in a > discussion about what they really want to achieve, but I'd guess that > the API would be more for suggesting where the 'dynamic' magnified > region would go. Again, talking
Re: Orca, AT-SPI and the Compiz zoom project
> I've been trying to familiarise myself with the whole world of > accessibility, but I'm having a bit of trouble understanding what I'll > actually need for my Compiz zoom project this summer. Welcome! > I know pretty much everything I need to know on the compiz-side of > things, but accessibility is new to me, and I'm hoping for a few > pointers for where to look for information, or rather what information > to look for. The current API for driving a magnifier is the gnome-mag API. It's a pretty complex API, and I think there may be opportunity for improvement with something such as Compiz. From my standpoint (that of a consumer), the main concepts behind gnome-mag are: 1) The magnifier is a system service to be accessed by an assistive technology (AT). AT's discover (and activate if necessary) the gnome-mag magnifier and talk to it. 2) Each AT needs to write its own configuration GUI for the magnifier. 3) The AT tells the magnifier to create one or more 'zoomers', each of which magnifies an area of the display. Each zoomer can have various settings associated with it, and the AT can update the region of interest for each zoomer at any time. 4) In use, the AT tells each zoomer to magnify an area of the screen, typically in response to mouse, object focus, caret movement events, and/or speech progress. With Compiz, I think there's opportunity for the magnifier to be more autonomous, but continue to offer itself up for interaction with other assistive technologies. As a loose analogy to this, one might consider what is done with BrlTTY/BrlAPI. BrlTTY runs as its own process, providing interaction with braille displays, most notably for virtual consoles. BrlAPI provides an interface for other applications to access the braille display while BrlTTY is running. By default, when Orca detects BrlTTY is running, it assumes the user wants braille and goes ahead and uses it. Something similar could be done with Compiz. For example: 1) Compiz could provide its own sophisticated GUI for the magnifier, allowing for at least what (and perhaps more than) could be accomplished with gnome-mag. This UI would also include the ability to create/destroy/modify new magnifier views of the display. I suspect a typical use case would be that the user has a main 'dynamic' magnified region that tracks where they are on the display and 0 or more 'static' magnified regions that monitor fixed areas on the display. This would be a HUGE improvement, and would not require all other AT's to write their own magnifier GUI. 2) Compiz itself could more easily provide the support for the various mouse tracking methods rather than requiring the assistive technology to do so. 3) Compiz could expose itself as a simpler service to the screen reader, with an API that provides mostly hints/recommendations about the area of the screen to magnify. One would need to engage end users in a discussion about what they really want to achieve, but I'd guess that the API would be more for suggesting where the 'dynamic' magnified region would go. Again, talking with end users would be a requirement. 4) If need be, the assistive technology could provide font/text hints about the portions of the screen being magnified, but I suspect Compiz itself could probably accomplish this by using the AT-SPI directly. I know I'm going to repeat myself, but I think now is the time to really engage end users in terms of gathering their requirements and then develop the architecture from that. Hope this helps. You are going to be exciting and useful stuff for the community. Will -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Orca, AT-SPI and the Compiz zoom project
Hi Kristian, Traditionally, screen reader ATs like gnopernicus originally and now Orca and LSR drive the gnome-magnifier. The magnifier itself is just a "dummy" component which is completely controller by the other ATs. They tell it where to look, how much to zoom, how big a zoom region should be on the desktop, how many zoom regions should exist, how big the cursor should be, etc. The purpose of this design, I believe, is so that magnification can be tied to speech and Braille output by the screen reader. At present, the screen readers communicate with gnome-mag through bonobo/CORBA. http://svn.gnome.org/viewcvs/gnome-mag/trunk/idl/ I hope this helps, Pete -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Orca, AT-SPI and the Compiz zoom project
I've been trying to familiarise myself with the whole world of accessibility, but I'm having a bit of trouble understanding what I'll actually need for my Compiz zoom project this summer. I know pretty much everything I need to know on the compiz-side of things, but accessibility is new to me, and I'm hoping for a few pointers for where to look for information, or rather what information to look for. I understand that Orca allready knows where the cursor is, and what I need to know is how to get to that information. Is it a matter of letting Orca drive the maginifier, or could I use at-spi for instance to get the information directly? I had a quick glance at gnome-magnifier but it seemed it would take more time for me to understand that, than just ask here. -- Regards, Kristian -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [xgl-mag] XGL/compiz screen magnifier planning
Hi all Good news, hardware accelerated magnification works and no special graphic card is needed. Here is my proof of concept: http://poweroftwo.de/magnworks_small.jpg But i have no idea how to implement the cursor tracker ;-) kind regards, Sven -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [xgl-mag] XGL/compiz screen magnifier planning
James King wrote: Up until yesterday, i couldn't see well enought to find out how to move the Magnifier from its initial position attached to the middle of the top of the desktop where it blocked all other dialogs Yes, this bug is annoying. Hopefully we can get get this working before 6.06, but we are anyway moving on to new and better things. I guess a simple, interactive way of moving and resizing the zoom window would help. Could be using the mouse or the arrow keys. that were large enough to be read with the standard cursor using Screenreader with the High-Contrast Big Print Enverted Theme turned on and the Theme's Recommended Font turned on. There is a bug filed on that as well. It should default to the larger font. I want to move "Interaction with screenreadder and Braille systesm":into the above "must-have" list from the following "desirable features" list. The problem is that this is probably also them most complicated feature to implement. When making a magnifier, the primary task is to grab parts of the display and do a simple translation to a larger size. Getting the text information and piping it to a screen reader is a different game, but unquestionably useful. I can understand why this might be a must-have feature for an end-user, but it is probably beyond the scope of the limited Summer of Code project. JK: I agree with Henrik's proposed solution to the problem of keeping the 3-D objects (with the menus, status bars, etc.) the same size while zooming in and out on the written text, calculation cell, database line, etc. in the Open Office productivity applicaitons. Generally, I use the zoom feature from the mouse rather than changing to a new theme. So making this easy with configurability by mouse (with at most, cntrl, alt, and shift key combinations. His hover feature solution -- should be very helpful, and I believe that it would have saved me some of the time that I had to give to customizing separate themes. This reminds me of a general magnification question. Sven mentioned that he had set up the magnifier on a separate X display and was therefore able to use the whole screen. This is probably a bit more tricky to set up (shouldn't be) but it seems to me that it would be the best solution for most people. Is this true, or are there some very good reasons why you would want to have parts of the screen appear in it's original resolution? (ignore reasons relating to the magnifier not functioning as it should, these are bugs that should be fixed). I know some people have a limited field of view and would only be able to use as small region of the screen at any one time, but even then is it not better to move your gaze rather than scroll the content? I'm wondering if perhaps our default mode should use the whole screen, and just make sure that navigation works really well, in different ways that will suit different users. Still, one reason I keep harping on finding some analog to Dragon Naturally Speaking Professional's voice macros is that the voice macro feature can be used to control not only Gnopernicus' Magnifier and Scroonreader configuration changes but also theme changes. Voice macros should be possible, though it is a separate project. Doing voice dictation like Dragon is highly complex, but a few dozen voice macros is much easier. (there is already something on KDE isn't there?) The "Examples" icon on the Gnome desktop was a gateway that was very useful to me when I was totally stuck because I couldn't find a magnifier good enought to tell me how to get to Gnopernicus. If you all can't at any time soon find a way to put a "Highly Visualy Impaired" track under the F5 key, to go along with the "Moderately ...," "Blind," etc. tracks Sorry, I should have replied to your last email about this. We run the risk here of getting an infinately long list of user settings. We could easily add another mobility option, hearing, and more. I would prefer we put some more effort into making the existing options work better. The point of the Live CD is not to have an ideal setup for anyone, but one that works well enough for most people to get it installed. The settings can then be tweaked to suit the individual. You say in effect that the gap between the moderate VI and Blind settings is too big, but it is largely a result of neither of those options working as well as they should. Each tool should be more powerful and more flexible (and less buggy). If someone can write an Accessibility Getting started guide in OpenOffice format in the next week or so, I can arrange to have it placed in the Examples folder for the release. I wish I could help you solve these problems, but all I can do is pose them and ask for help. Testing and feedback is also very important. We cannot do this in a vacuum. When we have a basic working version of the XGL magnifier we will certainly ask for testers :) - Henrik -- Ubuntu-accessibility
RE: [xgl-mag] XGL/compiz screen magnifier planning
Hi Members of the AT List: I've been unable to comment further on Dapper LiveCD for a while because of medical, work, and other problems that forced me to continue usiing Windows XP, ZoomText, and Dragon Naturally Speaking rather than continue trying to complete my dual-boot intall of Dapper by solvinig the Internet connectiion problems -- because I couln't until yesterday find the special preferences dialog for configuring the Gnopernicus Magnifier until I was able -- almost accidentally -- to use Gnopericus' Screenreader to read the Help file that let me know that there is a special separate dialog for Magnifier preferenes and how to get to it. Up until yesterday, i couldn't see well enought to find out how to move the Magnifier from its initial position attached to the middle of the top of the desktop where it blocked all other dialogs that were large enough to be read with the standard cursor using Screenreader with the High-Contrast Big Print Enverted Theme turned on and the Theme's Recommended Font turned on. (I mentioned in one of my previous letters how long it took to find the Recommended Font checkbox without any magnifier, since my visual fields are so damaged by glaucoma that I completely missed the checkbox.) The above story is the context for my comments on the following features lists in Henrik's email on the Subject of magnifier planniing: I shall put "JK:" at the beginning of my comments below. The excerpts from his original are indicated by all the lines beginning with right-arrow symbols. > [Original Message] > From: Henrik Nilsen Omma <[EMAIL PROTECTED]> > To: Ubuntu Accessibility Mailing List > Date: 5/9/2006 6:37:39 PM > Subject: [xgl-mag] XGL/compiz screen magnifier planning > The must-have features: > > * Fixed zoom factors - This could be pre-set by the user, but it should > also be possible to switch zoom levels on the fly with a hotkey > * Ability to follow the text-entry cursor - This requires AT-SPI magic, > but is a vital feature. > * Configurability - As many settings as possible should be configurable > by the user (but it can be a simple config file to start with). > JK: These "must-have" priorites sound good to me, especially the "Configurability of settings." I need the "Giant Green" cursor-pointer that in ZoomText versions 7.0-8.0 (and 9.0 probably) changes from approximately 1.0x1.5 inches in size at 2X magnification to 4x6 inches as the focus changes from 2X to 8X. [I have to use10X-16X to read dialogs with blue or black text on white or other light/bright backgrounds. (I can't read anything on the 3-D objects in the panels in the Knoppix LiveCD because they are all too bright, no matter how large I magnify them.)] I have to change the magnificaiton levels either by the wheel mouse or by voice macros that I have created in Dragon Naturally Speaking Professional Edition. Keyboard shortcuts are too difficult for me to use without making disasterous mistakes. So I need as much configurabilty as possible. I want to move "Interaction with screenreadder and Braille systesm":into the above "must-have" list from the following "desirable features" list. > Some desirable features: > > * Variable zoom factor - Fixed factors may not be exactly want you > want. It would be cool to be able to adjust the zoom level precisely > with the mouse wheel, say. > > * Scriptability - Again Orca has shown that being able to tailor the > behaviour of the AT app to your working application can be very useful. > This might well apply to the magnifier as well. > > * Fit window to zoom area - If you are working in Gedit and you have > zoomed in to a comfortable level, you now want to make sure that the > whole window fits into the viewable area. You then press a hot key and > Gedit's window is resized so that it fits. > > * Jumping between window sections - If you zoom to a fixed level of 3x > you then have in a sense 9 sections on the screen. You could float > around the desktop with the mouse, but there might be cases where you > want to know exactly where you are. On Gnome you can switch between > desktops with the Hotkeys Ctr-Alt-Right/Left/Up/Down. We could do the > same with zoomed sections. > > * Interaction with screen readers and braille systems - This adds > another level of complexity but could potentially be extremely powerful. > You could browse at a moderate zoom level and then have sections of text > read out to you. > JK: As you can see from my personal story, Interaction of Mag with Screenreader and Braille should be in the top-priority list of needed featurres for me. Even the current purely "trackless" access to Screenreader finally allowed me to find Magnifier's controls.
[xgl-mag] XGL/compiz screen magnifier planning
Hello everyone, The application deadline for SoC students has just ended. In the same way that I posted some new thoughts about SOK I will also post some musings on the XGL magnifier. See: https://lists.ubuntu.com/archives/ubuntu-accessibility/2006-May/000371.html Again I've copied in the applicants on Bcc. Feel free to jump in with comments and ideas or just hang back and read the suggestions. To sign up: https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility The advantage in this open approach is that there are many people reading this list who know a great deal about accessibility and others who know much about ubuntu and development. The spec ideas still need a fair bit of fleshing out and input from experienced people. The sooner we start that process the better positioned we will be when it is time to start coding. XGL/compiz screen magnifier -- I'm afraid most student applicants have underestimated this project, thinking we are simply looking for a magnifier window to follow the mouse cursor around. That is trivial to implement, but not very helpful. This misunderstanding is largely my fault for not writing up the project in greater detail before the SoC application process. So let me try to explain better here. The best way to get a feel for what we are looking for is to play with gnopernicus in magnifier mode. It has the basic features we need, but performance is not great and the usability could also do with some love. You'll notice the vital cursor tracking feature. If you open Gedit with the magnifier on, you can see that the zoom window will stay focused on the input cursor as you type along. If you try the same thing with kmag you will see that this feature is missing. The must-have features: * Fixed zoom factors - This could be pre-set by the user, but it should also be possible to switch zoom levels on the fly with a hotkey * Ability to follow the text-entry cursor - This requires AT-SPI magic, but is a vital feature. * Configurability - As many settings as possible should be configurable by the user (but it can be a simple config file to start with). Some desirable features: * Variable zoom factor - Fixed factors may not be exactly want you want. It would be cool to be able to adjust the zoom level precisely with the mouse wheel, say. * Scriptability - Again Orca has shown that being able to tailor the behaviour of the AT app to your working application can be very useful. This might well apply to the magnifier as well. * Fit window to zoom area - If you are working in Gedit and you have zoomed in to a comfortable level, you now want to make sure that the whole window fits into the viewable area. You then press a hot key and Gedit's window is resized so that it fits. * Jumping between window sections - If you zoom to a fixed level of 3x you then have in a sense 9 sections on the screen. You could float around the desktop with the mouse, but there might be cases where you want to know exactly where you are. On Gnome you can switch between desktops with the Hotkeys Ctr-Alt-Right/Left/Up/Down. We could do the same with zoomed sections. * Interaction with screen readers and braille systems - This adds another level of complexity but could potentially be extremely powerful. You could browse at a moderate zoom level and then have sections of text read out to you. Let's look at some use cases to get an idea of the kind of features we need to provide: Use case - Reading a news website: Take this news page: http://news.bbc.co.uk/1/hi/uk/4752819.stm It has some text and pictures and a great deal of non-essential navigation items (most other newspapers are worse). For the sake of example, let's consider a user who might use 2x zoom to get a general overview of a desktop of webpage layout but would need 8x zoom on normal text to read it. It would be useful to be able to zoom in on the different elements separately. Imagine that you could select the picture first. Press some hotkey to skip to the picture, and have the picture by itself displayed at 8x zoom where you can pan around. Another keystroke would give you the caption overlayed at the bottom of the picture in a high contrast colour or it could be read out via the screen reader. You then want to move on to the main body text. You return to the 2x overview page. You press another hot key to highlight some text. The first block of text appears with a heavy bright red (customisable of course) frame around it or with a full rectangle at 50% opacity so you can pick out the block you want. the next hotkey or mouse command would then zoom that text up to 8x, filling most of the screen. It would be wrapped to fit nicely and could be scrolled if needed. It would be as if you selected the text, copied and pasted it into a special app that would magnify it to your liking or rea
