You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@royale.apache.org by GitBox <gi...@apache.org> on 2019/01/17 08:29:16 UTC

[GitHub] carlosrovira commented on issue #380: Tutorial: write page on routing

carlosrovira commented on issue #380: Tutorial: write page on routing
URL: https://github.com/apache/royale-asjs/issues/380#issuecomment-455084687
 
 
   @aharui I (as others stated before in various places, I list, Disqus, etc..) think this is important. Routing is something that is inherent today to SPA developments. We don't need to to something that be a solution "to rule them all", but just start some effort that starts in some place. For example something I love in a recent JS application I see was that modules, since are external resources, can be easily given  a path, so when we load a module, we can update browser bar address. Then navigation controls could   have a bead to do the same...my point is that we don't need to take this as "all-or-nothing", I think people is expecting that we bring something to the plate that starts the effort. Just my 2 ;)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services