Last modified: 2014-02-21 00:03:59 UTC
Created attachment 11904 [details] Wikisource mobile Chapter View In Wikisource, we've got a page view like here : https://en.wikisource.org/wiki/Page%3AThe_Voyages_of_Doctor_Dolittle.djvu/354 On top of the page view we could go to the next page or previous page using the < or > buttons. Those buttons are unavailable when you connect from a mobile to the mobile web site of wikisource. Making the reading of a book page by page really complex. When we are in chapter view, we've got n option to go to the next chapter. Dereckson point me to that extension, but we are not sure this is the one responsible. I attached a chapter view and page view for esay references.
Created attachment 11905 [details] Wikisource mobile Page View
Not sure about the best software component either - tentatively moving from ProofreadPage to MobileFrontend.
I believe it should be handle by Proofread Page as it's Proofread Page related features but as long as Mobile Frontend is not merged into core, it's more easy to add mobile related features into Mobile Frontend. than in other extensions.
What needs to happen here is Proofread extension should add its own module to mobile that adds this feature. (alternatively if the javascript that does this is small you may want to test the code you've written on desktop and attempt to enable the same code you use on desktop) We now have full RL support so it should be as simple as: $wgResourceModules['mobile.proofreadpage'] = array( 'scripts' => array( 'mobile.js', ), 'position' => 'top', 'targets' => array( 'mobile' ), // or array( 'mobile', 'desktop' ) if you want to use same module 'mobileTargets' => array( 'stable', 'beta', 'alpha' ), ); MobileFrontend currently adds any modules that have been set to target mobile and set a mobileTargets I'd suggest enabling it on the beta site of wikisource first and spend some time testing it before switching it on on stable. This is as simple as setting: 'mobileTargets' => array( 'beta', 'alpha' ), Word of warning: The mobile environment may be missing parts of the mw library so be careful what you use!
