You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not clear, in terms of layering, whether gomobile should re-use shiny, or shiny re-use gomobile, or whether they should both depend on some other library factored out.
Yes, x/mobile should probably translate key events, although the intent of the x/mobile/app package is to develop mobile apps, and mobile apps aren't usually primarily driven by key events. If you want to write a desktop app, the x/mobile probably isn't the solution.
i like to write mobile apps, but would test it in desktop.
i like to use x/mobile for now, perhaps shiny will have nice widgets in the future. so i would like it to be as abstract as it could get.
still trying to understand shiny though, but i need shiny to be customizable that i can add custom layout. example, what if cassowary is ported to golang, i like to use it in the future.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?1.7 (sorry i am using windows at the office, the issue occurs at home)
What operating system and processor architecture are you using (
go env
)?ubuntu amd64 (sorry i am using windows at the office, the issue occurs at home)
What did you do?
run flappy gopher
What did you expect to see?
key events are triggered
What did you see instead?
no key events triggered, and close button not functional.
key events are not yet implemented at
but shiny have implemented this:
https://godoc.org/golang.org/x/exp/shiny/driver/internal/x11key
Should gomobile reuse shiny?
The text was updated successfully, but these errors were encountered: