Malcolm Smith
Malcolm Smith
[Here](https://stackoverflow.com/questions/77166637) is some example code of recording audio from the microphone on Android.
If Material 3 is based on Jetpack Compose, which appears to be the case, then that would have to be a completely separate backend.
Yes, it could share some of the low-level parts of the existing Android backend, but the widgets themselves would be quite different, and the layout system too.
Sorry for taking so long to respond. I like the way this is going, but I think the `main_window` property is getting a bit overloaded. Here's an alternative idea: **UI...
> * The alternative would be to say that Window has no menubar by default, but MainWindow does... but that then complicates the process of adding commands to a Window,...
> it's really a question of whether _not_ having the core menu set would be more platform appropriate. Including them allows an easy to understand implementation as laid out in...
> this would (a) require the reintroduction of DocumentApp I never proposed removing it, I only pointed out that if there was an `on_open` event, then DocumentApp could be written...
>> `Window` >> * Has a title bar on desktop platforms but not mobile ones >> * Has no menus or toolbar (the existing `Window.toolbar` property would be moved to...
Replaced by a number of smaller PRs listed in the top comment.
For some example code, see https://github.com/beeware/rubicon-java/pull/49.