01/25/2012, 02:05 PM
|
#1 (permalink) |
|
News Contributor
![]() |
Finally for Sept 2012 webOS 1.0 open source
From webosnation front pages: http://www.webosnation.com/hp-s-open...-webos-roadmap http://www.webosnation.com/hp-announ...en-sources-1-0
Last edited by akitayo; 02/08/2012 at 12:13 AM. |
01/25/2012, 02:42 PM
|
#5 (permalink) |
|
Member
![]() |
I would rather them take time and get it right, than rush something out the door and mess up. Realize, every line of this code has to be reviewed to make sure its not infringing on someone else's intellectual property. If this were released with some Apple, or Google, IP in it, we could see any new device held up for, literally, years as they tie up things in court.
Gargoyle |
01/25/2012, 03:33 PM
|
#9 (permalink) |
|
Member
![]() |
Really looking forward to this, I'm just hoping there will be some form of on-screen keyboard because there are very few portrait sliders out there for us to port to.
Dave
__________________
Proud webOS supporter! My Palm history: Vx, Centro, Pre-, Pre 2, Veer, Pre 3, Touchpad 32Gb & Panda Veer |
01/25/2012, 03:57 PM
|
#10 (permalink) |
|
Homebrew Developer
![]()
Posts: 761
|
I imagine Open webOS 1.0 will be a unifying release, so all the devices'll get the same features. Aka the keyboard from the tablet version on phones
so happy with this news.
__________________
webOS Ports' UI Architect & luna-sysmgr guru. |
01/25/2012, 04:26 PM
|
#11 (permalink) |
|
Member
![]()
Posts: 157
|
This is a reasonable timeline and probably better thought out than I expected. Maybe I'm jaded about HP but I suspect WOSI played a large part in making this good.
There are 4 big points I took from this simple schedule: 1. This maintains the viability of the WebOS ecosystem in the short term. Releasing Enyo first in a way that lets apps be cross-compiled to other environments (cough Android) gives the devs a revenue stream from their existing apps and, since there's no need to learn a new way of coding, encourages the creation of new WebOS apps (even if the real profit comes from sales to Android users) 2. It leverages existing platforms that have quite a few developers (Qt & Linux). Using a standard linux kernel means it becomes easier to compile replacements as you don't have to add any WebOS-specific libraries. More importantly, we get to use all the open source drivers as well as any redistributable closed-source drivers that work on the platform. Qt has quite a few followers, particularly in the Moblin/Meego crowd that was orphaned by Nokia/Intel/MS, so this may convince them to port apps to WebOS. 3. Supports new hardware. Barring the release of Enyo, the release schedule appears to be working from the kernel up to the final complete OS. That means any touch-screen hardware that boots a Qt-enabled Linux can be tested for WebOS compatibility. 4. Official release is early enough (September) that if any of the smaller ODMs were planning on releasing a WebOS device that they could have it in a usable state for CES. Heck, they could probably have hardware ready for Christmas. (Assuming final validation/tweaks to the software September while the pre-qualified hardware is being assembled, finalized WebOS flashed & shipped from Asia in October, starts shipping to users mid/late November) |
01/25/2012, 06:21 PM
|
#13 (permalink) | |
|
Member
![]() |
Quote:
![]() I like the roadmap....as long as HP sticks to it. Gives devs from all walks a chance to play with Enyo, and hopefully there will be a plethora of apps available once September rolls around. What will be interesting is Windows 8 - as Metro uses html/css/js as its programming base. I wonder if HP releasing Enyo first on the eve of Windows 8 coming out was a calculated move to get Enyo apps into the Windows Store? |
|
01/25/2012, 07:00 PM
|
#14 (permalink) |
|
News Contributor
![]() |
January is almost ending, then 8 months for a final time frame for webOS 1.0 Open source is good. Just thinking in a quality output.
Did anyone play with PiratePig yet: http://enyojs.com/samples/piratepig/ |
01/25/2012, 07:07 PM
|
#15 (permalink) |
|
Member
![]() |
where does Mojo framework fit into this?
I guess I'm just wondering because eventually I would like to upgrade my Pre 2 with the latest and greatest open source OS... and it seems that Mojo is the way to go for the small screen. Plus I want my gesture area! Although I guess with open source, anything can happen. Also, what about HP Maps (or any of the built in apps)? Will that be open sourced? |
01/25/2012, 07:14 PM
|
#16 (permalink) | |
|
Member
![]()
Posts: 511
|
Quote:
|
|
01/25/2012, 07:41 PM
|
#17 (permalink) |
|
Member
![]()
Posts: 159
|
Hey, I've been a launch day Sprint webOS convert and waited this long, so I'm pleased to see they actually released a roadmap as opposed to Ruby's old cryptic very soon pitch. I am excited at the fact the platform won't be device dependent per se, and would be shocked if people around here or xda, for example, don't start cranking out roms / ports for some awesome new phones. Sort of reversing the TP situation with duel booting android.
A boy can hope... |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|



