Malcolm Smith

`toga.Icon` doesn't currently use the Android resource system, so you'd have to use a different approach. In Java you'd access the app's icon as `R.drawable.ic_launcher`, but the package of R...

> I tried to use R.drawable.ic_launcher as Icon reference, but got following error: > `type object 'R$drawable' has no attribute 'ic_launcher'` This might work as long as you're using the...

OK, Android 7.0 is BeeWare's minimum supported version anyway, and we want to encourage the programmer to write portable code, so how about this: * In Toga's public API we...

Design discussion: #2108

Thanks, I'll look over this on Tuesday.

Overall this design looks good. Just a few comments: > On GTK, the story is complicated. Philosophically, [GNOME doesn't believe in status icons](https://blogs.gnome.org/aday/2017/08/31/status-icons-and-gnome/). So is the proposal that we simply...

I agree including the standard commands by default is better, because this feature will most often be used in situations where there's one status icon and no visible windows. >...

> While this could be accommodated with "a clear the defaults before adding your own commands" pattern, it strikes me as such a predictable usage pattern that it makes sense...

We talked the other day about what the Group of a status icon command should be, and mentioned 3 options: * MenuStatusIcon inherits from Group * MenuStausIcon has a `group`...

Just now we agreed the following: * MenuStatusIcon would inherit from Group. * `App.status_icons.commands` would be a CommandSet shared between all status icons, which requires all of its commands to...