|
 Originally Posted by Preemptive
I believe Enyo maintains webOS support in their version. As webOS hasn't changed since 3.0.5, the only real issue for them will be adjustments for changes in Enyo - they should be very familiar with both systems. I'm of course ignoring LG webOS and LuneOS. At one point, Open webOS was included as a future option on the supported platforms list, but is no longer there...
As LG is pushing Enyo as the prefered app creation tool, they are probably Enyo's biggest 'customer' at the moment. So both parties are interested in maintaining this and LG webOS is of course listed.
Supported Platforms | Enyo JS
Maybe there will be support for LuneOS - apps for it are currently being written in Enyo2, so there must be basic similarity to 3.0.5. Maybe webOS-Ports will have to maintain a version that provides compatibility.
I'm slightly confused as of course Enyo is supposed to be native on webOS and you can see that it is the other mobile systems that require phonegap. There is a difference between Cordova & phonegap, but they are related. I'll have to look that up again! Obviously, you talking about deployment, not running the program.
Anyhow, in the hope that I might find the time to learn some Enyo, I installed Ares and nodejs. What's the problem?
LuneOS can run Enyo 1.0, Enyo 2.0, QML and Open GL ES(2) apps. Theoretically Mojo might be possible to run, but it could never be included in images due to the fact that it hasn't been open sourced and the team would get into legal issues distributing the Mojo framework. Enyo support on legacy devices might break with upgrades to EnyoJS due to the fact that WebKit on those devices is aging and newly introduced features might stop working on legacy devices. A newer version of WebKit might solve this, but since it's deep on system level, it's not easy to implement (if at all possible with LunaCE/Community Edition, not sure HP open sourced everything required to replace WebKit in LunaCE).
PhoneGap/Cordova is basically used as a layer to access various sensors on various platforms using their API. This way you can build once and deploy to multiple platforms.
|
|
|