IssueTracker

This is a must!

To give a little context to the need for this.  For projects where multiple
applications are involved and they share quite a few custom views, it would be nice
to allow whatever version control software someone is using to dynamically link a
library of these views.  The problem is that you can't just pre-generate the R file
for these custom views since it may overlap with the R file for the application.
Currently, the only way to manage this is to copy files from the library over to the
project needing the custom views.  This is a nightmare for version control.

A simple solution for this would be to allow subfolders.  This would allow, say,
someone using svn to just set externals inside the values folder, so different files
may be included which would be compiled as part of the app's R.java file.

So, this would allow someone to set externals for custom views in the source folder
and then set resource dependencies as externals inside the subsequent res subfolders,
and voila, it would be easier to manage the custom views library and any change to
the library, through svn, would be reflected next time someone syncs with the repository.

This is not a tool issue but a framework issue. That's how the framework and aapt are
designed.

This is ridiculous in massive applications - it's a must.

This should change priority, it's very hard to maintain something with a lots of view, custom or otherwise.

for the love of all that is sane... allow me to organize my large project better and more easily