core
State related to ContainerView.
A io.udash.core.View which can render child view.
ViewFactory creating ContainerView.
State related to FinalView.
A io.udash.core.View which does not have any child view.
ViewFactory creating FinalView.
The Presenter should contain all business logic of a view: user interaction callbacks, server communication.
The class which should be used to present the state for io.udash.routing.RoutingEngine.
Creates view with io.udash.core.EmptyPresenter.
Creates view with io.udash.core.EmptyPresenter. Useful for static views.
Url wrapper - just for avoiding strings.
Abstract view which should be used in order to implement View for io.udash.core.ViewFactory.
Abstract view which should be used in order to implement View for io.udash.core.ViewFactory. The View implementation usually gets the model and the io.udash.core.Presenter as constructor arguments.
The ViewFactory has to prepare model, io.udash.core.View, io.udash.core.Presenter and link them together.
The ViewFactory has to prepare model, io.udash.core.View, io.udash.core.Presenter and link them together.
State for which this pair is defined.
The implementation of this trait should be injected to io.udash.routing.RoutingEngine.
The implementation of this trait should be injected to io.udash.routing.RoutingEngine. It is used to map State to ViewFactory.
Ignores state changes.
Ignores state changes. Useful for static views.
The Presenter should contain all business logic of a view: user interaction callbacks, server communication. It should not call any methods of a View class. The View and the Presenter should communicate via Model properties. When implementing Presenter, you should remember, that a handleState method can be called not only on view initialization.
State for which this presenter is defined.