Closed jzohrab closed 1 year ago
Note with pull request #62 this is far less of an issue, in my own experience.
in the UI being a lot more like the original LWT The idea behind the change was a bit of a quick-fix:
- I had to get rid of the archaic mobile_detect code
- LWT was unusable on phone So, I went for a solution that was a bit quick. Now that I experimented a bit, I think I can proceed to a mixture of the new and old systems: keep sliding frames for small screens, and use fixed frames whenever possible. This way the interface would be much cleaner!
This may be a stylistic choice, but I find the current UI to be distracting/slowing when working with new texts. For example, given the following text window:
When I click on "puesto", the right frame obscures the text I'm working on, and the popup doesn't go away, hiding part of the right frame:
Then when I click save, the frame says "new term saved", but it still blocks the text, and remains present until I click the reading frame again:
If all of this occurred in an ever-present right frame, with the reading frame present, that would probably be a cleaner experience. It would result in the UI being a lot more like the original LWT ... I'm not sure that's a bad thing!
Other options/notes: