Nick

@xeno-by I meant doing `scala-workflow` as one.

> Ui(new EditText(context, null, R.attr.myEditStyle)

Yes, definitely! _Macroid_ was born as I factored out some pieces of a relatively big application, and I ended up developing both of them very closely and effectively using that...

Hmm, not sure what happened there :( I’ll try this when I have some time. Feel free to suggest improvements to the current docs: - http://macroid.github.io/guide/Contexts.html#including - http://macroid.github.io/guide/Fragments.html#contexts

Do you suggest to use this approach for all size queries?

Hmm, that’s weird! I don’t have a `2.x` device around, but I can try running this in the emulator over the weekend.

There isn’t, but I’ll gladly accept a contribution :)

The way _Macroid_ is structured now is as follows: - features are grouped in small `private[macroid]` `trait`s - these `trait`s are mixed into various bigger `object`s. Here is an approximate...

See https://groups.google.com/forum/#!topic/macroid/P-cn8l4kzls.

> Things require ActivityContext when they don't appear to need it I’m pretty sure that creating widgets with the application context doesn’t work very well. It makes sense, because for...