webOS Ports hackathon on Wednesday to update Internals apps to Enyo 2 | webOS Nation
 
 

webOS Ports hackathon on Wednesday to update Internals apps to Enyo 2 11

by Derek Kessler Tue, 18 Dec 2012 9:24 pm EST

webOS Ports hackathon to update Internals apps to Enyo 2

Time to get your Enyo on, developers. webOS porting homebrew group WebOS Ports is staging a hackathon tomorrow to migrate a slew of WebOS Internals apps to the modern Enyo 2 app framework. The vast majority of the WebOS Internals apps we know and love, including standards like Preware, are built on the legacy Mojo framework (who would have thought that we'd be describing an app framework that's less than four-years-old as 'legacy'?), the exception being Tweaks, which is an Enyo 1 application.

Seeing as Open webOS does not have support for the old Mojo framework, Mojo being very nearly pure web code, constructed for smartphones like the Pre and Pixi, and not built for modern mobile needs, there's a need for the leading homebrew apps to be built on Enyo. After all, that Samsung Galaxy Nexus Open webOS port isn't going to be much good if it can't run apps like Preware or Tweaks.

So the WebOS Ports team has organized a hackathon kicking off Wednesday, December 19th at 3PM Eastern time (noon Pacific, 20:00 UTC) in the #webos-ports IRC channel with the goal of bringing as many of the classic WebOS Internals mojo apps up to modern standards. On the list for porting: Preware, Govnah, Lumberjack, and Tweaks. Additionally, there's a need for a file manager app, considering that none exist for Enyo 2 and really, that's something we've always thought should have been built into webOS (even if hidden away for power users).
 

Source: WebOS Ports

11 Comments

Excellent! If possible, please add the following to the preware app:
1. Automatic notifications of package updates for installed apps
2. Ability to display current catalog while downloading new catalogs in the background (i.e. instantly display cached catalog)
I'd be happy to alpha/beta test!

Hmm... Concurrent browsing. Have a panel that shows a download queue. I also hope the interface would look nicer. More white backgrounds like App Catalog, but not necessarily all the social stuff.

Maybe WebOS Internals will build an Enyo 2 framework package shared between their apps? I don't want half a dozen separate Enyo builds lying around.

It's unfortunate no one from WebOSPorts even contacted me about my Internalz 2, which I previously publicly stated a month ago I was rewriting in Enyo2...

It is a bummer hearing this as you have always been a good supported to the platform.
Personally I was wondering why you were not even mentioned in the article as well. Especially considering the work you have done towards getting Internalz 2. Perhaps we could blame the slew of Apple products our writer is to involved with now and does not go through the webOS forums as much? :D (I say that question with a smile but partially serious at the same time)

Well, one doesn't expect that you will release it as Open Source; also, Internalz HD (or whatever you called it) was announced many many months ago (more than a year) and you never released something.

theres been plenty of posts tho that show hes 1 busy person on both the schooling/learning and webOS front, its not like hes sat at home chained to his computers doing nothing but programming :)

I wasn't aware that you were still active, development-wise- I must have missed the announcement. Feel free to jump into #webos-ports on Freenode IRC to discuss this.

Please find a way to port webos to new phones, tablets, and PC!

great news, cant wait to see some progress on this front.

quick question springs to mind, if a some or a lot of apps are rewritten in enyo2, is there a possability of some of the apps that arent tied tightly into webOS (such as jasons updated internalZ or anythig else standalone), could they go on sale on opposition markets seeing as enyo is cross platform now, to help bring in some funding? or is that counter productive towards open webOS?

Internalz uses the FileMgr service (at least Internalz Pro does), so the GUI can be rewritten while the backing service can remain the same.