Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of simon.macdonald@gmail.com
 designates 209.85.220.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOBL_k72x7HCTA3x9ToL80dXQTy1WMQzkxNbRjOPH6P1QEsJwg@mail.gmail.com>
References: 
 <CAOBL_k72x7HCTA3x9ToL80dXQTy1WMQzkxNbRjOPH6P1QEsJwg@mail.gmail.com>
From: Simon MacDonald <simon.macdonald@gmail.com>
Date: Wed, 3 Oct 2012 16:05:07 -0400
Message-ID: 
 <CAM1AYQBYbxDcjRncPJ0OR6VNvLgGyj5ijR67mXapgbopeLCQjg@mail.gmail.com>
Subject: Re: [Android] Preview and one activity too far?
To: callback-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I kinda think we need a preview. Here is some new plugins that have
just been submitted that do what we are looking to do:

https://github.com/phonegap/phonegap-plugins/tree/master/Android/ForegroundCamera
https://github.com/phonegap/phonegap-plugins/tree/master/Android/ForegroundGallery

One of my other thoughts about this endeavour is that it is a lot more
work than we first thought. I don't see this making 2.2.0 as we'll
need to test the hell out of it before replacing the current camera.

Simon Mac Donald
http://hi.im/simonmacdonald


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