Like Ben, I also work at HP and most recently commited the Compass API Support to PhoneGap. I'm willing to work on some of the outstanding bugs/missing features and maybe also take "ownership" of the Cordova webOS Part. Let's talk about what should be fixed/added and what the priorities are. I think it's very important to keep the webOS Port alive going forward with Open webOS.
Markus -----Original Message----- From: Ben Combee [mailto:[email protected]] Sent: Donnerstag, 14. Juni 2012 18:06 To: [email protected] Subject: Re: Outstanding webOS issues Hey, Ben from Palm/Enyo/HP here. I just caught up on this thread, and I'm talking to our devrel group about seeing what can be done to upgrade webOS support. We've been thinking a lot about how to leverage Cordova on all the Enyo platforms, including webOS. It's likely that we'll be able to get someone internal to do some work to keep this alive as we move towards Open WebOS this fall. On Wed, Jun 13, 2012 at 6:28 PM, Filip Maj <[email protected]> wrote: > Cool. > > I will extract the webOS issues from the parent ones but keep them > around for bookkeeping. > > On 6/13/12 4:18 PM, "Brian LeRoux" <[email protected]> wrote: > >>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. >>>> >>>> >
