andydotxyz

9 ms·

61.
by andydotxyz 5y ago
Yeah so much of the fresh look is a technical aspect at the moment - like being able to develop it on any OS, or the simplicity of the module system. Once we have some more time developing we will be able to get the fresh look better surfac
62.
by andydotxyz 5y ago
Thanks, fixed :)
63.
by andydotxyz 5y ago
Oh man there is a 0.3 release right around the corner which has so many new features added. We should post again when some more of the "fresh look" aspects are clearer :)
64.
by 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,
65.
by 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...
66.
by 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. E
67.
by andydotxyz 8y ago
Well the obvious reason would be if your users may not have Chrome installed? On a more basic level it comes down to whether you want to code pure Go or HTML/CSS as well...
68.
by andydotxyz 8y ago
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
69.
by andydotxyz 8y ago
Thanks, I think there is a patch nearly ready for that, will roll out a hotfix as soon as that is done and I expect a 1.0.1 in a few days
70.
by andydotxyz 8y ago
The biggest reason is that we have not implemented shadows yet... once we have that things may look more like you expect.
71.
by andydotxyz 8y ago
Can you help us and report the issue on GitHub please? There must be something different about your interaction or setup as the developers have not seen that app crash in a long time...
72.
by andydotxyz 8y ago
For the simple text markup views we will support markdown as it has those features. After that we could consider HTML...
73.
by andydotxyz 8y ago
None of those are in yet. Tree views and data grids require a data binding API that we have not yet decided on. HTML view is going to be difficult on Linux as we don’t want to bring in GTK or Qt - but we will get there.
74.
by andydotxyz 8y ago
A fair point. At this time it is desktop only but the design of the API does not limit this. People are looking at mobile and web drivers but this will be a fair distance off I expect.
75.
by andydotxyz 8y ago
At the moment that is lacking - we intend to add it in a future version as accessibility is important