#107 Flux example JavaDoc
This commit is contained in:
@ -13,18 +13,23 @@ import com.iluwatar.flux.view.MenuView;
|
||||
* applications. Flux eschews MVC in favor of a unidirectional data flow. When a user interacts with
|
||||
* a React view, the view propagates an action through a central dispatcher, to the various stores that
|
||||
* hold the application's data and business logic, which updates all of the views that are affected.
|
||||
*
|
||||
* <p>
|
||||
* This example has two views: menu and content. They represent typical main menu and content area of
|
||||
* a web page. When menu item is clicked it triggers events through the dispatcher. The events are
|
||||
* received and handled by the stores updating their data as needed. The stores then notify the views
|
||||
* that they should rerender themselves.
|
||||
*
|
||||
* <p>
|
||||
* http://facebook.github.io/flux/docs/overview.html
|
||||
*
|
||||
*/
|
||||
public class App {
|
||||
|
||||
/**
|
||||
* Program entry point
|
||||
* @param args command line args
|
||||
*/
|
||||
public static void main( String[] args ) {
|
||||
|
||||
// initialize and wire the system
|
||||
MenuStore menuStore = new MenuStore();
|
||||
Dispatcher.getInstance().registerStore(menuStore);
|
||||
|
@ -4,6 +4,11 @@ import org.junit.Test;
|
||||
|
||||
import com.iluwatar.flux.app.App;
|
||||
|
||||
/**
|
||||
*
|
||||
* Application test
|
||||
*
|
||||
*/
|
||||
public class AppTest {
|
||||
|
||||
@Test
|
||||
|
Reference in New Issue
Block a user