09/14/2013, 02:29 PM
Hello webOS folks,
I'm hoping to get some guidance from devs that have been working with Enyo 2.2 (and 2.3 MVC) for legacy webOS devices. I've been lurking around the enyo forums and poking around the edges for some time.
I need this tool to work on webOS 2.2.4 and 3.0.5 as well as desktop browsers (Firefox is my preference, but I can switch to Chrome or whatever if that's what it takes). The webOS support could by either as a web app in the browser or as an installed app, but I'd prefer an installed app.
So I'm writing because I have read a lot of conflicting posts about how well Enyo 2 is working on legacy webOS hardware and was hoping to hear about some of the hurdles, workarounds and no-gos I may be in store for.
The would be a re-write of a completely browser-based PHP/mysql project tracking system that I threw together in a couple of weeks several years ago and which needs a database refactoring and so many new features that a complete re-write is called for. I'm still in planning stages and may shift from mysql to mongodb or another nosql option - I've just started learning about nosql...
So I'm hoping to hear about some experiences of working in Enyo 2 for legacy webOS before I invest too much more time in the framework, because I've read of things like lists not scrolling in 2.2.4, but the London Tube Status App seems to work fine on my Pre 2, so I'm unsure how many of the problems I read about are current or if special workarounds had to be implemented, etc.
I think the only webOS-specific service I would hope for access to besides some sort of local storage would be the camera, but if that isn't possible, I don't think it's a deal breaker...
-Please let me know if you have some experience with Enyo 2 / 2.3 and how it's working on webOS for you.