Naming on variables/methods in Presenter class about mortar

[loganj]

Speaking for myself, not for @rjrjr: The names we have come from MVP, so they still seem reasonable to me despite the namespace clash with Android's View. More often than not, a Mortar view is an Android View.

That's my best argument for the names we have, but my best argument against adopting other terminology is just that I haven't heard anything better. I could be convinced by a decent proposal for specific terminology that's accurate and not horribly contrived..

[rjrjr]

Remember that view is a very generic term, much older than Android. (And older than MVP, for that matter. Model View Controller from Smalltalk 80). Mortar is agnostic as to whether a view class extends View, Activity, Fragment, or whatever else. That's why the ViewPresenter convenience class is separate from the base Presenter.

We have a decent handful of Presenters hanging off of our main activity. We try to minimize how much we do that, preferring that only code with actual depenencies on Activity itself lives in such a presenter. But it's definitely a supported use case.

I'm not crazy about the idea of changning any of the names, but improved Javadoc is always welcome.