Cocoa (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
momijizukamori) wrote2021-06-20 05:00 pm
momijizukamori) wrote2021-06-20 05:00 pm
Entry tags:
More Ao3Reader things
I figured out how to take screenshots within the app without having a menu in the way! First off, some aesthetic tweaks to the reader overlay:
View for a work with chapters:
View for a work without chapters:
Mostly because it seemed silly to pop up an empty chapter overlay. I could remove the greyed-out chapter button when it has none but the UI math is easier if I keep it there.
Aaaaand I got the first step of the 'about work' overlay done, which is to take a list of tags and turn them into clickable elements, with wrapping. Which is actually kind of complicated when you have to manually set breakpoints and define locations absolutely!
Example of a taglist - ignore the bit where it's overlapping other elements, that's because I was maximizing the space the taglist used for testing.
And then visual feedback on toggle, before the view is replaced - at the moment the hooks to load the new views don't work so it doesn't actually replace yet.
I'd really appreciate feedback on the element size - on one hand they feel REALLY big, but on the other, the touch resolution on eink screens are not great, and you can't pinch-zoom to get around it like you can on a phone etc. On the OTHER other hand, I'm on a Kobo Glo, which is like, the second-oldest series that's still supported, and the second-lowest resolution available out of these devices - it's 1024 x 758/4 3/4" x 3.5" for 212ppi, so it's possible that 'barely okay' on the Glo is plenty acceptable on all the other models.
View for a work with chapters:
View for a work without chapters:
Mostly because it seemed silly to pop up an empty chapter overlay. I could remove the greyed-out chapter button when it has none but the UI math is easier if I keep it there.
Aaaaand I got the first step of the 'about work' overlay done, which is to take a list of tags and turn them into clickable elements, with wrapping. Which is actually kind of complicated when you have to manually set breakpoints and define locations absolutely!
Example of a taglist - ignore the bit where it's overlapping other elements, that's because I was maximizing the space the taglist used for testing.
And then visual feedback on toggle, before the view is replaced - at the moment the hooks to load the new views don't work so it doesn't actually replace yet.
I'd really appreciate feedback on the element size - on one hand they feel REALLY big, but on the other, the touch resolution on eink screens are not great, and you can't pinch-zoom to get around it like you can on a phone etc. On the OTHER other hand, I'm on a Kobo Glo, which is like, the second-oldest series that's still supported, and the second-lowest resolution available out of these devices - it's 1024 x 758/4 3/4" x 3.5" for 212ppi, so it's possible that 'barely okay' on the Glo is plenty acceptable on all the other models.
no subject
And then I don't.