dojox.mobile.currentView no longer tracks current view

[ben hockey]

from #14602

In [27586/dojo]:

Refs #14602 !strict. To support nested views and split views, set a comma-separated list of visible view IDs to the hash value. The new 'viewRegistry' module provides a quick access to the existing views. The hash handling functions are factored out into the new 'bookmarklable' module.

this seems to remove some of the support for dojox.mobile.currentView in _doTransition. it's hard to determine if this was intentional since in dojox/mobile/_compat.js there is still support for dojox.mobile.currentView in _doTransition for browsers that are not webkit (​http://bugs.dojotoolkit.org/browser/dojo/dojox/trunk/mobile/_compat.js?rev=27586#L176).

if dojox.mobile.currentView is deprecated, is there an alternative way to do programmatic transitions? up until this point, the way it had been done was dojox.mobile.currentView.performTransition( ... );

[ben hockey]

hmm... it looks like r27594 was partially responsible for this too.

[ykami]

In 1.7, for dojox.mobile.currentView, there was a comment like

dm.currentView = _this; //TODO:1.8 reconsider this. currentView may not have a currently showing view when views are nested.

because it was unreliable. After experiencing various cases, it turned out that the idea of 'current view' didn't work. (dojox.mobile.currentView in _compat.js should have been removed.)

If you have a reference to one of your views, you should be able to get a reference to the currently showing view with View.getShowingView() method. It searches the sibling views for the currently visible view.

If your application is more complex, you may want to subscribe the "/dojox/mobile/afterTransitionIn" topic to keep the last shown view. Please see tests/test_transition-pubsub.html for examples.

[ykami]

In [28385]:

Refs #15040 Removed assignment to dojox.mobile.currentView, which was unreliable way of keeping the current view, to avoid confusion. !strict

[ykami]

Did the comment above solve your problem?

[ben hockey]

Replying to ykami:

Did the comment above solve your problem?

it confirms that the intention is to remove dojox.mobile.currentView. thanks. you can close this if you've got nothing else to do with it.