Soumya, My guess is whatever Google is implementing might show up in the next version of Android, FroYo, but that's just a guess on my part..I don't remember when FroYo was scheduled to be released..
Regards -- Ashwin On Sun, May 16, 2010 at 9:45 AM, Soumya <soumyakanti...@gmail.com> wrote: > Hi Ashwin, thank you for the explanation. I wanted to query about it > because, our team is implementing some enhancements for android of > which PIN based lock was one of them, for this reason I wanted to > query. I guess our team can wait for another week or two, and see what > they offer. > > On May 16, 6:10 pm, Ashwin Bihari <abih...@gmail.com> wrote: >> The reason Dianne is asking you to wait is most likely that Google is >> implementing something that might directly address what you are trying >> to do, so rather than implement something that is already being done >> by Google, you might as well just wait and see what they have to offer >> and change it only if it doesn't completely do what you need.. >> >> Not hard to read between the lines.. >> >> -- Ashwin >> >> >> >> On Sun, May 16, 2010 at 8:45 AM, Soumya <soumyakanti...@gmail.com> wrote: >> > Sorry but I could not understand from what you just mentioned. Can you >> > please elaborate. I can wait but can you let me know as to what and >> > why to wait. I will be very thankful if you could let me know. >> > Actually if anything related to the lock screen (PIN based) is going >> > to be released by Android soon, then I can surely wait and stop >> > working in it. >> >> > On May 16, 1:02 pm, Dianne Hackborn <hack...@android.com> wrote: >> >> Well best would be to not spend any more time on this particular thing >> >> right >> >> now, if you can wait a week or two. >> >> >> On Sat, May 15, 2010 at 10:43 PM, Soumya <soumyakanti...@gmail.com> wrote: >> >> > > Yes, and this is okay because the lock screen is not an activity. >> >> > > Activities go in layers below, whose position is dynamically >> >> > > assigned by >> >> > > the window manager. >> >> >> > Ok so as Android maintains these layers, the application layer can >> >> > never come on top of the lock screen and the application layer is >> >> > handled by the activity manager. But what is this layer called and how >> >> > does lock screen use it. Can I not be used in the same way so that >> >> > another lock screen can be made in keeping other two lock screens >> >> > untouched. >> >> >> > > You'd need to modify the platform's lock screen code. >> >> >> > > I suggest waiting a few weeks, though. >> >> >> > I actually don't want to modify the present lock screens but is it >> >> > possible that inside the pattern lock screen I can modify the view >> >> > part of the code such that either pattern lock or PIN based lock can >> >> > be displayed based on some settings option? As for the waiting >> >> > suggestion, I could not get it.Is Google releasing next version of >> >> > Android or some lock based API's or a PIN based lock screen. Please do >> >> > let us know. >> >> >> > On May 15, 10:01 pm, Dianne Hackborn <hack...@android.com> wrote: >> >> > > On Fri, May 14, 2010 at 10:49 PM, Soumya <soumyakanti...@gmail.com> >> >> > wrote: >> >> > > > Thank you for the reply. In PhoneWindowManager there are many layers >> >> > > > defined and keyguard has a higher layer priority. Is this the >> >> > > > process >> >> > > > that is being used by keyguard to be on top of other windows such as >> >> > > > application layer. Is this the process that has been followed. >> >> >> > > Yes, and this is okay because the lock screen is not an activity. >> >> > > Activities go in layers below, whose position is dynamically >> >> > > assigned by >> >> > > the window manager. >> >> >> > > > If implementing our lock screen is not possible with activity due to >> >> > > > our requirement then what process can we follow so that we can >> >> > > > display >> >> > > > a lock screen (PIN based) along with the default lock screens of >> >> > > > android. >> >> >> > > You'd need to modify the platform's lock screen code. >> >> >> > > I suggest waiting a few weeks, though. >> >> >> > > -- >> >> > > Dianne Hackborn >> >> > > Android framework engineer >> >> > > hack...@android.com >> >> >> > > Note: please don't send private questions to me, as I don't have time >> >> > > to >> >> > > provide private support, and so won't reply to such e-mails. All such >> >> > > questions should be posted on public forums, where I and others can >> >> > > see >> >> > and >> >> > > answer them. >> >> >> > > -- >> >> > > unsubscribe: >> >> > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> >> >> > > website:http://groups.google.com/group/android-porting >> >> >> > -- >> >> > unsubscribe: >> >> > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> >> >> > website:http://groups.google.com/group/android-porting >> >> >> -- >> >> Dianne Hackborn >> >> Android framework engineer >> >> hack...@android.com >> >> >> Note: please don't send private questions to me, as I don't have time to >> >> provide private support, and so won't reply to such e-mails. All such >> >> questions should be posted on public forums, where I and others can see >> >> and >> >> answer them. >> >> >> -- >> >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> >> website:http://groups.google.com/group/android-porting >> >> > -- >> > unsubscribe: android-porting+unsubscr...@googlegroups.com >> > website:http://groups.google.com/group/android-porting >> >> -- >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> website:http://groups.google.com/group/android-porting > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
