3 ms·

Unfortunately it is a matter of hours in the day. Accessibility relies on things like focus handling that are just not ready yet. Maybe we released too early or

Unfortunately it is a matter of hours in the day. Accessibility relies on things like focus handling that are just not ready yet. Maybe we released too early or maybe it was sensible to get a basic but solid release together to build on. I expect that time will tell.

zapzupnz 8y ago
For people who don't have any particular accessibility needs, time will tell. For those of us who do, time has told us again and again and again and again and again, and we're kinda sick of time telling us to just hold tight when everything we need is right there in the native frameworks.
- andydotxyz 8y ago
  I’m sorry for the frustration. I agree that these things should not be put off indefinitely. If we are able to get the project to a place where there is some commercial support then it gets much more likely that we could make this happen. Every project has to start somewhere and as you can tell from this comment page there are many groups of users who feel we have not met their expectations...
  - mwcampbell 8y ago
    > Every project has to start somewhere and as you can tell from this comment page there are many groups of users who feel we have not met their expectations... I imagine that level of criticism must be demoralizing. (That's why I didn't pile on, though I've been vocal about accessibility on similar threads about other toolkits.) Just so I can understand where you're coming from, what's your motivation for developing yet another custom toolkit, despite all the challenges and all the table-stakes requirements that haven't yet been met? There must be some reason you feel this is a worthwhile use of your time, but I don't understand what it is.
    - andydotxyz 8y ago
      We’ve tried to share the aims of the project in the wiki[1]. Basically having seen the revolution in usability, software design and raised expectations on mobile it was frustrating that desktop had stagnated. Having a toolkit that was slim, easy to learn, cross platform and sweet looking seemed like a worthwhile challenge :). 1: https://github.com/fyne-io/fyne/wiki/Vision https://github.com/fyne-io/fyne/wiki/Vision
  - flukus 8y ago
    > Every project has to start somewhere and as you can tell from this comment page there are many groups of users who feel we have not met their expectations... I think you've inflated the expectations by creating a 1.0 release, that's a point where you'd expect things like accessibility to be included. Had it still been 0.x then you'd get a lot more leeway on missing features. It would also be great to list these limitations on the main page, anyone that finds those limitation important can then avoid it, they'll be a lot less annoyed than someone who invested a lot of time learning to use Fyne only to discover the limitations.
    - andydotxyz 8y ago
      That’s a fair point. Maybe this should have been 0.1. I can’t rmemeber how the version number got decided...
  - zapzupnz 8y ago
    I'm glad to see you're receptive to the shortcomings, not only in accessibility but other fields. In a world of arrogant GTK+ developers, it's refreshing not to be told "lol no, shut up".

zapzupnz 8y ago

For people who don't have any particular accessibility needs, time will tell. For those of us who do, time has told us again and again and again and again and again, and we're kinda sick of time telling us to just hold tight when everything we need is right there in the native frameworks.

andydotxyz 8y ago
I’m sorry for the frustration. I agree that these things should not be put off indefinitely. If we are able to get the project to a place where there is some commercial support then it gets much more likely that we could make this happen. Every project has to start somewhere and as you can tell from this comment page there are many groups of users who feel we have not met their expectations...
- mwcampbell 8y ago
  > Every project has to start somewhere and as you can tell from this comment page there are many groups of users who feel we have not met their expectations... I imagine that level of criticism must be demoralizing. (That's why I didn't pile on, though I've been vocal about accessibility on similar threads about other toolkits.) Just so I can understand where you're coming from, what's your motivation for developing yet another custom toolkit, despite all the challenges and all the table-stakes requirements that haven't yet been met? There must be some reason you feel this is a worthwhile use of your time, but I don't understand what it is.
  - andydotxyz 8y ago
    We’ve tried to share the aims of the project in the wiki[1]. Basically having seen the revolution in usability, software design and raised expectations on mobile it was frustrating that desktop had stagnated. Having a toolkit that was slim, easy to learn, cross platform and sweet looking seemed like a worthwhile challenge :). 1: https://github.com/fyne-io/fyne/wiki/Vision https://github.com/fyne-io/fyne/wiki/Vision
- flukus 8y ago
  > Every project has to start somewhere and as you can tell from this comment page there are many groups of users who feel we have not met their expectations... I think you've inflated the expectations by creating a 1.0 release, that's a point where you'd expect things like accessibility to be included. Had it still been 0.x then you'd get a lot more leeway on missing features. It would also be great to list these limitations on the main page, anyone that finds those limitation important can then avoid it, they'll be a lot less annoyed than someone who invested a lot of time learning to use Fyne only to discover the limitations.
  - andydotxyz 8y ago
    That’s a fair point. Maybe this should have been 0.1. I can’t rmemeber how the version number got decided...
- zapzupnz 8y ago
  I'm glad to see you're receptive to the shortcomings, not only in accessibility but other fields. In a world of arrogant GTK+ developers, it's refreshing not to be told "lol no, shut up".