incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <>
Subject [PROPOSAL] Orientation Interface
Date Mon, 24 Oct 2011 19:22:36 GMT
This proposal is intended to be a discussion, so if you have strong feelings
about anything here, or any recommendations or corrections, this thread
should be the outlet for that.  Upon reaching some general consensus, and
having the concept sit with everyone for a bit, we will put it to a vote.

The proposal (in brief):
Add a JavaScript interface to allow developers to specify at runtime what
orientations they allow.

A simple use-case :

- an app with 2 views, managed by manipulating the DOM, and showing/hiding

View 1 is a list of flickr images with a thumbnail, title, date + author
This view should not re-orient and should always be displayed in portrait.
Selecting an item shows View2.

View 2 is an image view of the selected image
User should be allowed to freely re-orient the device to their pleasing, for
viewing the picture.
Clicking a close button returns the user to View1

The current implementation:

- all major CallBack devices support orientation, but the method that you
use to specify which orientation your app will allow are different.
- supported orientations are uniformly mapped on devices to 0,-90,90,180
- orientations are a build time setting, and there is no way to change what
you support at runtime.


 - plist specifies supported orientations


 - manifest.xml specifies
    <activity android:configChanges="orientation|keyboardHidden"> ...

BB WebWorks



  SupportedOrientations="Portrait" Orientation="Portrait"
  ... ></phone:PhoneApplicationPage>

The proposal (in detail):

1. All devices should support a runtime getter/setter on the static JS
PhoneGap object.
2. The 'property' should be called supportedOrientations and should be an
array of integer values.
    // allow the device to orient to Portrait or PortraitUpsidedown
    PhoneGap.supportedOrientations = [0,180];

3. Orientation events should NOT be sent when the device is moved to an
unsupported orientation.
4. supportedOrientations should be considered to be in order of preference.
5. setting supportedOrientations to a value that would preclude the current
physical device orientation should trigger an immediate orientation change
and subsequent change event.
    // Device is currently in landscape left
    PhoneGap.supportedOrientations = [0,180];
    // result : Native view reorients to Portrait and triggers orientation
change event.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message