On Thu, May 6, 2010 at 7:55 PM, Bob Kerns <[email protected]> wrote: > The lesson there is that if you use Proguard, and something odd goes > wrong, always try disabling that first -- because the amount of time > you can potentially waste is huge! > > Proguard works pretty well, and is pretty useful. But this, together > with its learning curve and setup time, are its big drawbacks. But > shrinking and optimizing apps means phones can do more...
Except that proguard is a required part of the Scala + Android process right now, for Scala 2.8.0.RC1. Android won't take the standard Scala library without proguard (or something else) first stripping it down. It's not something you can bypass easily. -- James Moore [email protected] http://jamesmoorecode.blogspot.com/ -- 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
