Re: [Tutor] Interactive editing of variables.
Allan, That is what I have done before I went to bed. Installed ActiveState and using Python 3.6 as that is the release build they have up on their site. -Original Message- From: Tutor On Behalf Of Alan Gauld via Tutor Sent: Sunday, 2 June 2019 5:01 AM To: tutor@python.org Subject: Re: [Tutor] Interactive editing of variables. On 01/06/2019 09:52, mhysnm1...@gmail.com wrote: > the underlying graphic library. Win32 could work if I could load it. > Since then I could use standard windows objects. If you are running windows then you can access the Win32 DLLs via ctypes. The win32 package should also be easily installable as a binary. If not try using the ActiveState distribution of python because it bundles all the windows tools in the installer. Personally I always use ActiveState pyton for my Windows boxes. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
Re: [Tutor] Interactive editing of variables.
Mike, Allan and Matt, Thanks for the information and help. I will check out Mike's code and have a play. Allan you provided some good resources and based upon what Matt stated before and using Easegui. This is not a path I can use. Thanks for the help anyway. Matt, a shame. I am not sure what can be done in this area for TK, as it is open source other than someone with the knowledge introducing accessibility. At the level required to provide the required accessibility framework for different platforms for the default UI controls , is far beyond my skill level. I believe later versions of QT support iaccess2 framework which is an accessibility framework. I know from a legal point of view. If a developer or company built a product based upon the GUI environments and sold it to the USA Government or to the public. They are opening themselves to potential legal action. This concept applies in other countries. Accessibility is on a up swing and Microsoft, Apple, Google, Cisco and others are focusing on this area due to the change in the landscape. What I do not know, how this applies to open source. If there is no commercial transaction. Then this is the area I am unsure if any of the laws I am indirectly referring to impact. Anyway, this is getting off scope. Just highlighting so people are aware. Accessibility is a part of best practice for UX, UI and development. -Original Message- From: Tutor On Behalf Of Mats Wichmann Sent: Sunday, 2 June 2019 5:24 AM To: tutor@python.org Subject: Re: [Tutor] Interactive editing of variables. >> The issue I have with a lot of GUI programs built for Python they >> generally fail in the accessibility department for a screen reader. > > I can't help there I have nearly zero experience of using > accessibility tools. But I'd expect any GUI toolkit to work with the > standard OS tools. After all they are ultimately all built using the > underlying primitive GUI API On the gui front, tk developers make no bones about tk not having been built with accessibility considerations tk (and thus tkinter which is just the Python binding to tk), is not going to work with a screen reader. wxPython is probably the best choice, it explicitly has support (although sadly only for Windows): https://docs.wxpython.org/wx.Accessible.html possibly some of the other toolkits do - I wouldn't rule out Qt either, but haven't any experience. ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
Re: [Tutor] Interactive editing of variables.
On 02/06/2019 01:10, mhysnm1...@gmail.com wrote: > What I do not know, how this applies to open source. If there is no > commercial transaction. Then this is the area I am unsure if any of the laws > I am indirectly referring to impact. Caveat: I am not a lawyer... I know it has a big impact on commercial software but that has some potential return on investment in terms of increased market share. For open source it is hard to see the return and the most likely scenario would be to greatly reduce the availability of such software. Consider the potential impact of applying such requirements to open source or other "free" software. This would potentially mean that any software that was shared or distributed in any way would need to comply. That would include a bit of code I knocked together for my own benefit and my friend wanted to get a copy. I've got to say, sorry I need to make it accessible first... now consider that my friend and I are working on some scientific research, maybe even medical research into treatments for blindness or cancer or whatever. Now I can't share my research tools with other researchers because I lack the time and or knowledge to convert the software to be accessible. The implications are that a lot of software would never see the light of day regardless of the potential benefits it could deliver. It would be a foolish law which prevented (or even substantially delayed) progress in the name of making all software accessible. It would also be very difficult to enforce since you would need to either prohibit the sharing of all non-accessible software or somehow, arbitrarily, define what constitutes regulated "distribution". Legislating for commercial distribution is much easier and more justifiable since profits are available to pay for the extra effort/costs. Where no profit exists then distribution is much less easily defined; it would be a legal minefield I suspect. > Anyway, this is getting off scope. Just highlighting > so people are aware. Accessibility is a part of best practice > for UX, UI and development. Indeed, and in an ideal world all of the building blocks would incorporate it at the foundation level. Unfortunately we are a long way from that. Also, in most cases the supporting hardware is not readily available to deliver the potential accessibility options that could be provided. It is very difficult to write software for features that you cannot test (think cursor control via blow tube or eye movement or command input by tones. All possible now but need specialist kit which individual developers won't have.) It is hard enough testing software for all the "standard" forms of input - mice, pens, touch screens, keyboards, voice, etc -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos ___ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
