incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Combee <>
Subject Re: Outstanding webOS issues
Date Thu, 14 Jun 2012 16:06:13 GMT
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 <> 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" <> 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 <> wrote:
>>> I say we leave it dormant until open webos 1.0 is released in September
>>> until HP decides to definitely kill it sometime in July. Since we're
>>> touching the VERSION file for every release maybe we should just remove
>>> from the cordova distribution. That could also apply to Bada 1.2 that I
>>> 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 <> 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
>>>> to the next point release.. Are we putting any more effort into webOS?
>>>> JS API-level changes, we usually have a single parent task tagged for
>>>> JS with each implementation set up as a sub-task to implement the
>>>> 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
>>>> API cordova-js introduced for accel, adding stuff (HTTP status code to
>>>> FileTRansfer Error object) that webOS is tagged for. They've been
>>>> 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
>>>> specific versions and also not including webOS in any of the API-level
>>>> changes (because they never get done anyhow).
>>>> My $0.02.

View raw message