On Mon, Jun 4, 2012 at 2:03 AM, lbendlin <[email protected]> wrote: > Aren't you the one who put stuff into the asset folder structure? So you > should know what's there, and where.
Heh, an interesting take on data-driven design. ;-) Seriously - I'm writing code that has to work with multiple APKs with different assets/ areas. Even if it weren't for that, I don't like to hardcode paths, names and directory structures into my code. If you hardcode a directory hierarchy and then have to change it, you have to chase down every mention of it in your code and fix it - you can do better than that. -- 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
