Deprecate $.mobile.defaultPageTransition and $.mobile.defaultDialogTransition

[gabrielschulhof]

The replacement can be the following:

1. The page widget gets

   1. An option "transition"

   2. Defaults: $.mobile.page.defaults.transition: { page: "fade", dialog: "pop" }

   3. A method getTransition():

      getTransition: function() {
      // the value of the transition option has highest precedence
      return this.options.transition ||
      
      // Otherwise use the value stored in the defaults for the widget
      $.mobile.page.defaults.transition[ this.options.dialog ?
          "dialog" : "page" ] ||
      
      // Finally, for backwards compatibility with 1.4, consult the deprecated values
      $.mobile[ "default" +
          ( this.options.dialog ? "Dialog" : "Page" ) +
          "Transition" ];
      }

2. When the pagecontainer decides which transition to use for the page it's about to bring in, it first consults the transition specified on the link and, if that is undefined, then it grabs the transition to use by calling toPage.page( "getTransition" )

This way, we retain the dialog-gets-pop-page-gets-fade setup and the default configuration options modifiable at mobileinit time.

[gabrielschulhof]

OK, so based on our discussion, the conclusion is that the pagecontainer widget will get an option called "transition", which it will consult whenever it decides on which transition to use. Its value serves as the default transition, but you can override the value per-link by adding data-ui-transition to the link.