This is an automated email from the ASF dual-hosted git repository.

andreww pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-docs.git


The following commit(s) were added to refs/heads/master by this push:
     new 286d0c3  Update routing.md
286d0c3 is described below

commit 286d0c32f14bacf911578e9c7a95e435be5d6b7a
Author: Andrew Wetmore <[email protected]>
AuthorDate: Mon Mar 2 19:37:14 2020 -0400

    Update routing.md
    
    moved information from this page to the features/routing.md page
---
 .../application-tutorial/routing.md                | 31 +---------------------
 1 file changed, 1 insertion(+), 30 deletions(-)

diff --git a/create-an-application/application-tutorial/routing.md 
b/create-an-application/application-tutorial/routing.md
index 831eb2a..dfd76a4 100644
--- a/create-an-application/application-tutorial/routing.md
+++ b/create-an-application/application-tutorial/routing.md
@@ -24,37 +24,8 @@ permalink: 
/create-an-application/application-tutorial/routing
 
 About Routing
 
-*needs editing and formatting*
-## Basic Router
-````
-<js:Router id="router" stateChange="hashChanged()"/>
-````
-In the above example, any time the route changes, the `stateChanged` function 
will be called.
+_This information is not yet available_
 
-The state of the router can likewise be changed directly by modifying the 
`router.routeState` and calling `router.setState()` `router.renderState()` is a 
similar method, but it will dispatched the `stateChanged` event as well and 
cause any attached beads to react to the state change as well.
-
-## Router Beads
-The full power of the Router becomes apparent when you use beads. Router can 
automatically sync the route state with componet state. It can change which 
component is shown by creating and removing components. It can handle 
parameters etc. Here are some examples:
-````
-<js:Router localId="router">
-    <js:RouteToState component="{footer}"/>
-    <js:RouteTitleLookup lookup="{getTitleLookup()}"/>
-</js:Router>
-````
-
-In this example, the router syncs the state of the footer with the route path. 
The RouteTitleLookup allows changing the window title based on the state. The 
`lookup` property is an object whose keys are the state names and the values 
are the corresponding titles.
-
-Routers and RouteTotState can be declared on and for more than one component, 
so state can be changed and synced across multiple components with ease.
-
-Another example which routes to components: (in progress)
-````
-<js:Router localId="router">
-    <js:RouteToComponent component="{footer}"/>
-    <js:RouteTitleLookup lookup="{getTitleLookup()}"/>
-</js:Router>
-````
-
-*Instructions and sample code will appear here soon to show how you can map 
URL parameters to different initial values in the application, and vice versa.*
 
 
 {:align="center"}

Reply via email to