Understanding the practical implications of the Cairngorm 3 Navigation Library

Question

Hi there again,
Based on the discussion from yesterday:
http://forums.adobe.com/thread/897088?tstart=0
... I forgot to mention that I have difficulties to find practical use cases for the Navigation Library. What does the Navigation Library solve when it will be used in the development architecture? Nothing explicit seems to be mentioned about it in your documentation:
http://sourceforge.net/adobe/cairngorm/wiki/HowToUseCairngormNavigation/
When speaking in theory I also have the concern that the Navigation Library is breaking the separation of concern between the Presentation Layer and the Domain Layer (when using the Domain Driven Design language):
http://sourceforge.net/adobe/cairngorm/wiki/UnderstandingCairngorm/
... or the separation of concern between the View Layer and the Data Layer (when using my language):
http://code.google.com/p/masuland/wiki/NanoarchitectureMVCb
Practically speaking again, I usually store the application state (or the waypoints/landmarks of the application) in the Application Model ... see:
     public class AppModel
          // States
          [Publish(scope='appModel', objectId='loginBoxState')]
          public var loginBoxState:String;
          [Publish(scope='appModel', objectId='appStackState')]
          public var appStackState:String;
          [Publish(scope='appModel', objectId='settingsBoxState')]
          public var settingsBoxState:String;
For more information please check out these two versions:
http://code.google.com/p/masuland/wiki/LoginExample#Flex_4_(Halo)_with_MVCbCtl_PInj
http://code.google.com/p/masuland/wiki/LoginExample#Flex_4_(Halo)_with_MVCbCtl_PInjDdd
... of my Login Example:
http://code.google.com/p/masuland/wiki/LoginExample
I hope you can help me clarify this!
Thank you,
masu

Answer 1

I managed to reproduce this issue in the NavigationParsleyProject. After the NavigationParsleySample1 application is started the active view is content.dashboard.nested.child1. However if you try to navigate to content.tasks.timetracking view, it will redirect you to content.tasks.expenses view which is the first child in the content.tasks ViewStack. All Timetracking view's enter and exit handlers as well as interceptors will be executed though.
After I commented out the metadata for all event handlers and both interceptors in TimeTrackingPM class, I was successfully navigated to the content.tasks.timetracking view.
This issue occurs only once and I believe it has something to do with the deferred instantiation. I tried to debug the source of the navigation library but haven't had any success yet.