Created a small app which shows the dialog and the contents of the Downloads folder.
Teaser screenshot attached (has some ways to go before looking like the mocks) and doesn't implement selection yet.
Re-factored the code to support showing a RecyclerView per storage (one for screenshots, one for camera, etc), as shown in mocks.
Also uploaded the code in its current state to git-hub:
https://github.com/finnurbreki/picker-dialog
(still no selection implemented)
Really coming along! 3 comments (assuming they're not already being addressed):
1. Will this become a full-screen dialog by the time it's finished (i.e. no padding and scrim around the edges)?
2. There needs to be a little more spacing between the icon and label in the Camera and Browse buttons (10dp according to my notes).
3. What is that Stormtrooper's deal? ;)
Yes, I'm hoping to get it to use all the available width by the time it is finished. I was experimenting with it earlier, I think there's a missing flag somewhere. I'll take a look at the spacing as well.
As for the Stormtrooper; it is keeping me company out here in the wilderness. There's also Darth Vader, but last time I tried to take his photo he grabbed me by the neck! :)
Hi, I became aware of this feature that launches a sandboxed child process in the renderer from a code review.
For long term maintenance, chrome on android should not have two different ways to launch child processes. There are a lot of shared concerns, like setting the right "oom order", setting up basic things like sandbox and crash reporting.
I understand this is a service that's meant to be java only, but I think long term, it's easier to teach content layer to launch java-only child processes rather than maintaining two separate code paths.
Comment 1 by finnur@chromium.org
, Oct 14 20162.1 MB
2.1 MB View Download