Nick

> I don’t understand how this would streamline the `lp` generation? Oh well, this is somewhat orthogonal, but I thought extra type safety might help to deal with this horrible...

I’d love to issue a new release, but I have not extensively used the code introduced by the newer commits, and currently I’m not developing anything on Android, which means...

I don’t think themes can be applied programmatically :( However I’ve never been able to use them effectively — personally I find the whole theme XML API (inheritance, composition, namespacing)...

AFAIK there is no way to create `AttributeSet` programmatically. See for example this [SO answer](http://stackoverflow.com/a/2948483). Yeah, not using the `LayoutBuilding` DSL is another way to approach this :)

This is interesting — we could write an implementation of `AttributeSet` with `+`, etc — as an alternative to _tweaks_... I’ll try to poke with it when I have time.

Any further thoughts on this? I guess it could be “simplified” to ``` scala scalacOptions in (Compile, compile) ++= (dependencyClasspath in Compile).value.files.map("-P:wartremover:cp:" + _.toURL.toString) scalacOptions in (Compile, compile) ++= Seq(...

Great! I think it would also be nice to have the plugin set up globally and use _sbt_’s new `AutoPlugin` feature. Then just listing the traversers should be enough. As...

@michalrus What about opening a work-in-progress PR or a new repo? I’m not an expert on _sbt_ but probably would be able to improve things in an existing code, so...

I considered having a go at implementing `def modifyPoly[T[_], U](obj: T[U])(path: T => U) = ???` to cover the basic use-case, but there are a few problems: 1. A class...

(I am of course assuming that we stick to blackbox macros.)