Yeah, includes playbook. Im thinking once we graduate from incubation we undertake the administrative work necessary to split out the webworks-for-smartphone and webworks-for-playbook implementations. It's getting gnarly in the BB repo right now.
On 6/13/12 4:21 PM, "[email protected]" <[email protected]> wrote: >I assume BlackBerry includes playbook >Sent on the TELUS Mobility network with BlackBerry > >-----Original Message----- >From: Brian LeRoux <[email protected]> >Sender: [email protected] >Date: Wed, 13 Jun 2012 16:18:45 >To: <[email protected]> >Reply-To: [email protected] >Subject: Re: Outstanding webOS issues > >Agree for removing from distribution. Would like to propose we only ship: > >- iOS >- Android >- BlackBerry >- Windows Phone >- Bada > >...for the moment. > > >On Wed, Jun 13, 2012 at 3:59 PM, Anis KADRI <[email protected]> wrote: >> I say we leave it dormant until open webos 1.0 is released in September >>or >> until HP decides to definitely kill it sometime in July. Since we're >>only >> touching the VERSION file for every release maybe we should just remove >>it >> from the cordova distribution. That could also apply to Bada 1.2 that I >>am >> no longer working on. >> As far as I know, webos doesn't use cordova-js. >> >> On Wed, Jun 13, 2012 at 3:45 PM, Filip Maj <[email protected]> wrote: >> >>> Hey all, >>> >>> There are issues in JIRA from like, months back, still outstanding, for >>> webOS. For the past couple point releases we have just been punting >>>them >>> to the next point release.. Are we putting any more effort into webOS? >>>For >>> JS API-level changes, we usually have a single parent task tagged for >>>the >>> JS with each implementation set up as a sub-task to implement the >>>changes >>> necessary, webOS among them. >>> >>> I am not sure cordova-js is fully integrated into webOS. We still have >>> tasks like normalizing accelerometer return values, updating the >>>changed >>> API cordova-js introduced for accel, adding stuff (HTTP status code to >>> FileTRansfer Error object) that webOS is tagged for. They've been >>>around >>> for a long time. >>> >>> What's the deal? >>> >>> I would like for us to stop supporting webOS.. Not sure there is much >>> value anymore. Or, at the least, not tag the webOS issues to be fixed >>>for >>> specific versions and also not including webOS in any of the API-level >>> changes (because they never get done anyhow). >>> >>> My $0.02. >>> >>>
