Is there support for deferred navigation to components that aren't yet instantiated in Cairngorm Navigation (Parsley)?
For example, if I issue a navigationEvent to "a.b.c.d", but only a is instantiated so far (therefore landmarks b,c and d haven't yet been registered), will the framework manage this, and control navigation as b, c and d are each instantiated and registered?
Yes, that should fully work. However, we're currently migrating from opensource.adobe.com SVN to SF SVN, and this is causing some issues. We also might have missed some changes of revision 21183 in Navigation in the latest release that affect deferred navigation to some extent. We're trying to fix this ASAP and will do another release once the SVN migration is performed. If you're seeing specific issues on deferred navigation, post here or our bugbase, check the past revisions until 21183 or the patches from Brian Lai from our bugbase.
The migration to SourceForge SVN is complete and the revision error has disapeared. So, currently trunk in https://svn.code.sf.net/adobe/cairngorm/code/cairngorm3/trunk/ contains a fully working nav lib supporting deferred navigation. Over the next days we'll plan to release another Flex 4.1, Parsley 2.4, Swiz 1.1 and then a Flex 4.5 release.
I can't seem to find this 1.6 release anywhere. Is this the repo you were talking about Alex? It only has up to release 1.5 in there
But is it just me or is it still not there?
I'm looking in this repo path: