Skip to content

Latest commit

 

History

History
90 lines (53 loc) · 2.55 KB

README.md

File metadata and controls

90 lines (53 loc) · 2.55 KB
Raw

Presentation

An architecture for Android as a replacement of MVC.

Why should I use Presentation?

Because you want to have more readable, testable code.

Avoid "God Objects", mainly your Activities or Fragments.

How does it work?

Separation of responsibilities by module:

  • Presenter: Get a Business Object from the DataProvider and give instructions to the ViewProxy
  • DataProvider: Communicate with the "outside" to set and get the data, following the instructions of the Presenter
  • ViewProxy: Convert Presenter instructions and set values to Android Views.

Architecture

Leak safe. Don't hold a strong reference to the DataProvider, Presenter, or ViewProxy.

Sample

The goal is to make this application:

Each public method of the modules are defined into an interface:

public interface FormDef {

    interface IPresenter extends Base.IPresenter {

        void onClickSaveButton(String value);
    }

    interface IDataProvider extends Base.IDataProvider {

        String getValueSaved();

        void saveValue(String value);
    }

    interface IView extends Base.IView {

        void setValueSaved(String text);
    }

}

Then you have your:

  • FormPresenter that extends BasePresenter and implements FormDef.IPresenter
  • FormDataProvider that extends BaseDataProvider and implements FormDef.IDataProvider
  • FormViewProxy that extends BaseViewProxy and implements FormDef.IView

Go further

Presenter into an Adapter

This library has a dependency on Efficient Adapter to use the same view cache mechanism.

This allows to apply the Presentation pattern to object in an Adapter as well. Your ViewHolder should extend PresenterViewHolder and your Presenter should extend BaseItemPresenter.

Proguard

Nothing special needed.

Gradle

dependencies {
    compile 'com.skocken:presentation:1.0.0'
}

License

Contributing

Please fork this repository and contribute back using pull requests.

Any contributions, large or small, major features, bug fixes, unit/integration tests are welcomed and appreciated but will be thoroughly reviewed and discussed.