incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <...@adobe.com>
Subject Re: [Android] Preview and one activity too far?
Date Wed, 03 Oct 2012 17:10:44 GMT
Joe I'm interested in going through what a plugin like that would look
like, gather more use cases for the plugin.xml spec + cli tools

On 10/3/12 7:17 AM, "Andrew Grieve" <agrieve@chromium.org> wrote:

>Sounds like a great test of doing things that other plugin developers will
>have to do. If it's painful for us, then it will be more painful for
>third-party plugins. If it's painful for us, we should fix it. Maybe this
>is an example of something that will be made easier with the command line
>tools, but not before?
>
>
>On Tue, Oct 2, 2012 at 5:15 PM, Joe Bowser <bowserj@gmail.com> wrote:
>
>> Hey
>>
>> I'm still hacking on the Camera UI, trying to get it looking better,
>> and I'm wondering if we should implement Preview.  The easiest way of
>> doing this on Android is by having a preview activity and allowing the
>> user to save or cancel, which would send the user back to the Camera
>> Activity.  The downside of this approach is that we have to add
>> another activity to the manifest just to view the image that was
>> produced by the Camera, and this is one more thing that would break
>> when we introduce the new camera.
>>
>> How do people feel about implementing a Preview Activity? We could
>> avoid it, but I think that this would be more code, since we'd have to
>> hide the Surface View and show the UI underneath somehow.
>>
>> Any thoughts?
>>
>> Joe
>>


Mime
View raw message