You are not logged in.
Hello all,
Time for another project has come :-).
This one was born due to BurntSushi's wingo lack of status bar. The README said that you won't need one and I said "What?!". So here it is. And I finally have a status bar with working anti-aliasing, huh. I am yet to come up with a neat way to integrate it with wingo itself (displaying workspaces, etc.), but should be doable with some bash and wingo-cmd for now.
All (I hope) the necessary usage details are in the README, right on https://github.com/KenjiTakahashi/gobar.
BTW: Does anybody here know of a good way to automate testing of X apps? I mean the actual drawing part, i.e. draw something and check that it is there and is good. I'd love to have a test suite for something more than parser before I start breaking it again :-).
Offline
BTW: Does anybody here know of a good way to automate testing of X apps? I mean the actual drawing part, i.e. draw something and check that it is there and is good. I'd love to have a test suite for something more than parser before I start breaking it again :-).
Run the application in Xvfb, take a screenshot and compare it with a reference rendering.
Or try half-automation with automatic test starts and manual confirmation with yes/no dialogs.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
BTW: Does anybody here know of a good way to automate testing of X apps? I mean the actual drawing part, i.e. draw something and check that it is there and is good. I'd love to have a test suite for something more than parser before I start breaking it again :-).
For testing user interaction with the interface:
https://gnu.org/software/xnee/
Offline
Thank you guys for the suggestions. I think xnee might be a bit overkill as there's no real "interaction", it just sits there and tells stuff :-). But nice to know, might come in handy in the future. I'll probably go the screenshot comparison way here, will look into it more soon.
Offline