(i hope i dont sound too obnoxious) the platform is linux based, google had no choices but open sourced it. :-)
To me, the apps are the interesting bits but they are not fully opened. For example, they referenced codes/packages that were close- sourced or missing (i.e. speech recognition ). Also, as you said, some apps are completely missing. I understand there could be many reasons why they are missing, but I think i wasnt wrong to call the code base crippled. :) On Nov 14, 3:11 pm, Romain Guy <[EMAIL PROTECTED]> wrote: > The entire platform is open sourced. Only some Google apps (YouTube, > Gmail, etc.) are not open sourced. > > What exactly do you find "crippled"? What is missing for you? > > > > On Fri, Nov 14, 2008 at 12:08 PM, zl25drexel <[EMAIL PROTECTED]> wrote: > > > you guys did not open-source everything. it's pretty hard to figure > > out how things work using a cripple code base. > > > On Nov 13, 2:14 pm, hackbod <[EMAIL PROTECTED]> wrote: > >> On Nov 12, 6:38 am, zl25drexel <[EMAIL PROTECTED]> wrote: > > >> > please, put that API to replace the lock screen, i will be more than > >> > happy to use that instead of my little hack. > > >> Yes this would be nice to have, but at this point it is a lower > >> priority for the core android team than a lot of other things. If > >> this is something you really want, you could look into adding the > >> feature to the platform. One warning though: doing complete support > >> for replacing the lock screen is going to be really hard, because all > >> of the security and interaction issues it deals with are quite > >> complicated. > > >> > I am pretty sure toddler is also disguising asHOMEscreen because i > >> > tried restarting the app in the onstop method, the desktop will show > >> > up for half of a second before the app is restarted, that's clearly > >> > not the behavior we see in toddler lock. So i think it does the same > >> > thing. > > >> No, it does another trick, which the system should also protect > >> against but is not so obviously a flaw. > > >> For your idea of forcing your app to be thehomescreen, look at it > >> this way. On android, thehomekey serves as our equivalent of Ctrl > >> +Alt+Delete for the user: it is the one thing they can press, which > >> they are guaranteed will get them out of whatever app they are in and > >> back to a known trusted location. By forcing yourself to be thehome > >> screen behind the user's back, you are causing the system to violate > >> that trust it has established with the user, stepping down the path of > >> simply being malicious. In fact, this API should never have made it > >> in to the platform -- as I said, this is an old approach we did to > >> preferred applications, it completely conflicts with the current model > >> (which allows the user to select the preferred activity for each > >> action), and as such is a pretty big security hole. It will be > >> removed in a future release. > > >> So, uh, thank-you for finding that approach, but please don't use > >> it. :) > > -- > Romain Guywww.curious-creature.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
