Re: [android-developers] Resource generator is too flaky...

2011-11-27 Thread Mark Murphy
On Sun, Nov 27, 2011 at 10:35 AM, Christopher Van Kirk
 wrote:
> Importing android.R breaks it.

I mostly see that with students that try using Eclipse's Ctrl-Shift-O
while they have a resource bug that inhibited R from being generated.

One solution to that would be for aapt to not get rid of the old R if
resource errors failed in generating a fresh R. This would also help
the "OMG my whole project's busted" effect you get from a failed R
build that therefore causes compile errors for every R reference in
the project.

> Having anything.out.xml in the resources area breaks it. Inexplicably,
> Eclipse tries its best to stick .out.xml files whenever you edit resource
> docs, so this one constantly crops up.

I haven't run into that recently. It used to happen to me a lot. And I
still occasionally run with an XML editor in the active tab, so
something fixed this for me -- in fact, I just tried it and could not
reproduce the problem. What Eclipse are you on (I'm on Galileo)? And
are you on the latest ADT?

> Intermittently compilation somehow misses resource declarations without
> generating any errors, requiring a complete rebuild, even though there are
> no errors.

FWIW, I haven't run into that, unless you mean the "R constants
changed and the inlined numbers in already-compiled classes didn't"
issue.

> It sometimes doesn't copy changed resources into the output apk, again
> requiring a complete rebuild.

FWIW, I haven't run into that. How are you determining that this has
occurred, vs. the R values simply being out of sync as in my previous
point?

> Please consider dedicating one or more human resources to ferret out and
> solve these problems.

Check b.android.com for existing issues on these, and filing ones if
you don't see them. Prefix Eclipse specific ones with ADT, as that
seem to help them show up on the tools team's radar. Also, if you do
file issues, you might cross-post links to them to the adt-dev Google
Group, particularly for non-Eclipse-specific ones, to increase the
odds that they'll get properly assigned.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to *Advanced* Android Development_ Version 2.1
Available!

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Resource generator is too flaky...

2011-11-27 Thread Christopher Van Kirk
Hi there. This one goes out to Google with nothing but the best of 
intentions:


The resource compiler is just plain too fragile. I think you guys should 
put in some time to iron out the weirdness from it to save us developers 
from hours and hours tearing our remaining hair fighting with it.


Let's take a look at just a few of the problems:

Importing android.R breaks it.
Having anything.out.xml in the resources area breaks it. Inexplicably, 
Eclipse tries its best to stick .out.xml files whenever you edit 
resource docs, so this one constantly crops up.

Setting build output to verbose breaks it.
Intermittently compilation somehow misses resource declarations without 
generating any errors, requiring a complete rebuild, even though there 
are no errors.
It sometimes doesn't copy changed resources into the output apk, again 
requiring a complete rebuild.


Because of the last two problems, one finds oneself constantly 
rebuilding from scratch. With larger projects, this can be an onerous 
constraint indeed. My project, for example, takes about 10 minutes to 
completely rebuild, so doing a clean rebuild is something I want to 
avoid at all costs. A button or a doc showing how to rebuild just the 
R.x would be terrific.


Please consider dedicating one or more human resources to ferret out and 
solve these problems.


Pretty please. With a cherry on top.

Chris...


--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en