Create Navigation system for Framework about gjallarhorn HOT 5 CLOSED

@willsam100 I'd love any feedback you might have on this, as well.

from gjallarhorn.

Just to document a couple of things discussed in over chat:

• Avoid (if possible) circular dependencies declaring Component with msg and model
• A mapping between Pages and Components would need to given to the framework during construction

Things to consider:
How many update functions to have e.g. one per app or one per component. I've built an app with one, but this could be the cause of circular dependencies.

from gjallarhorn.

A single update cycle in an app often leads to too many concerns all in one place and also makes the logic loop involved rather large. I would prefer a series of coordinators which act as the navigation between the various parts of the app.

from gjallarhorn.

The other problem is abstracting the navigation, the differing systems make this pretty hard to do. I know Xamarin Forms attempts this, albeit in a fairly naive manner, its not that suitable for an intuitive platform facing app.

from gjallarhorn.

Moving to ReedCopsey/Gjallarhorn.Bindable#3 , since it belongs in that project.

from gjallarhorn.