Fred's idea looks good, though lot of code bytes to it. How many users read a license any way ? Each application adding license asset files can eat up space.... :-)
On Jan 25, 6:10 pm, "Fred Grott(shareme)" <[email protected]> wrote: > A better solution for the end user is to set up some display > indicating wher ethe library licenses are to read, for example my > Xspot app : > > http://www.youtube.com/watch?v=wiPDOrkPCxQ > > ...it displays the name of libraries used and than points users to > wards the license for that library > > On Jan 24, 7:06 am, Kavita <[email protected]> wrote: > > > Hi, > > > I'm working on an Android app that's licensed under Apache Software > > License 2.0. As recommended in best practice, I would like to display > > the license to the end user for acceptance before proceeding. However, > > the ASL text is large and I'm not sure whether it's a good idea to > > show the entire license. I would like to know if there are any > > recommendations for apps under ASL on what license text to use > > (perhaps an abbreviated version of ASL)? Pointers to actual license > > text would be quite helpful. > > > At a minimum, I was thinking to show the "Disclaimer of Warranty" > > section and for the whole license include the link to ASL site. Any > > better ideas? > > > Thanks, > > - Kavita --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
