>1. Should we allow platforms to expose API that is not common across >all platforms or should API always be in common and the platform coded >to fail gracefully if the API is not supported?
Seems like backwards compatibility is a common theme right now so I suppose in the interim its acceptable to have platform-specific stuff. However I would stress that we should strive really hard to factor this stuff out as much as possible and instead put efforts into extending the cordova API (down the road; post-1.6) >2. If we allow platform specific API, is the merge mechanism >preferable over options in [2]? Yeah it's convenient, I don't mind it. More declarative than stacking things into the initialize() method of the platform definition. Although the include() method signature is getting a little hairy with us tacking on extra boolean parameters ;D > >[1] >https://github.com/apache/incubator-cordova-blackberry-webworks/blob/maste >r/javascript/notification.js >[2] >http://markmail.org/search/?q=drew+walters+exec&q=list%3Aorg.apache.incuba >tor.callback-dev#query:drew%20walters%20exec%20list%3Aorg.apache.incubator >.callback-dev+page:1+mid:eep4cruewmepbr4t+state:results >[3] >https://github.com/deedubbu/incubator-cordova-js/commit/acb6263838f4b31829 >09ae775935d4d7f0bac286 >[4] >http://markmail.org/search/?q=drew+walters+exec&q=list%3Aorg.apache.incuba >tor.callback-dev#query:drew%20walters%20exec%20list%3Aorg.apache.incubator >.callback-dev+page:1+mid:p4v5bvri77qtbkpm+state:results
