Open WebOS Releases Core Apps; Reveals Touchpad Won't Be Supported 49
Caught via the H is news that more components of webOS have been released: "The core applications provide a comprehensive set of platform user applications, including Email, Calendar, Contacts, Memos, Accounts, Clock and Calculator." Additionally, HP has opened up the development branch of system manager: "We are excited to open up the active development branch of our upleveled System Manager. This major upgrade incorporates the latest QtWebKit and Qt technologies in an improved architecture. Modern QtWebKit now underlies all applications, providing state-of-the-art support for HTML rendering and I/O. The latest stable release of Qt has been integrated across the system, eliminating alternate rendering paths and providing a clean base for the future. These changes bring enhanced stability and performance to Open webOS." As always, source can be had from the Open webOS github. A bit of bad news for existing device owners, however: "...we are aiming for support on future hardware platforms where SoC’s support Linux 3.3+ kernel and where open source replacements for proprietary components are integrated. Existing devices cannot be supported because of those many proprietary components, including graphics, networking and lack of drivers for a modern kernel." Existing device owners will have to live with the "webOS community edition."
Cyanogen Mod [Android] (Score:1, Interesting)
I've been running it since it became available on the touchpad and loving it. Fie on WebOS.
ARM'd with new code (Score:2)
Will it run on Surface?
Re: (Score:2)
surface rt? no.
Cool (Score:5, Insightful)
Re: (Score:3)
an OS that won't run on any hardware it was developed for! The programmatic equivalent of locking your keys in your car.
Not that I'm exactly sanguine about WebOS's chances; but 'the hardware it was developed for' is sufficiently banal that(crypto lockdowns excepted) finding other targets shouldn't be that difficult. The OS doesn't require any particularly notable button layout(the phones did have hard keys, to make typing more pleasant; but a servicable soft keyboard was added for the tablet, and the only other requirement is a single 'back-to-home-screen' button).
It does kind of suck for owners of the current hardware(me in
Re: (Score:2)
The Touchpad hardware is a deadend, but why let that limit the future of the OS? Is it a bad thing that OSX won't run on a Mac Classic or Windows 8 won't run on an IBM PC/XT? By the way, WebOS was originally developed for Palm phones so it already won't run on the hardware it was developed for.
Of Mice and Men (Score:3, Funny)
> touchpad won't be supported
"What?!? We only started supporting the mouse in January."
Re: (Score:1)
I'm quite sure they meant the HP Touchpad [wikipedia.org]
Re: (Score:3, Funny)
I'm quite sure they meant the HP Touchpad [wikipedia.org]
Ever heard the joke about the airplane? Never mind, way over your head.
will open webOS support PDK applications? (Score:3)
this is a big question for me (as a developer).
or will open webOS will only support enjo (HTML5, CSS et al) with no native application support (existing webOS applications).
Re: (Score:3)
Re: (Score:2)
i did already :)
http://www.webosnation.com/dereks-sunnyvale-pilgrimage-what-do-you-want-know#comment-290805
what hardware WILL be supported? (Score:5, Interesting)
"we are aiming for support on future hardware platforms where SoC’s support Linux 3.3+ kernel and where open source replacements for proprietary components are integrated. Existing devices cannot be supported because of those many proprietary components, including graphics, networking and lack of drivers for a modern kernel"
Are there any tablets that meet those requirements? Are there even any planned?! I think this just became another hypothetical OS ... good for contributing to if you just want to pad your resume.
Re: (Score:2, Insightful)
When android development was started, there weren't ANY devices available that would run it.
Do you really assert that this is a vaild reason?
Re: (Score:3)
When android development was started, there weren't ANY devices available that would run it.
Do you really assert that this is a vaild reason?
..and android doesn't have open gpu drivers now so?
the real question is are they doing anything which would warrant hope that tomorrows pad's will ship with gpu's with non-proprietary drivers?
it would actually sound more viable if they were doing work on targeting proprietary driver socs and systems - for example by doing active work to target android kernels/systems as the target. now it really does sound like a pi in the sky dream.
Re: (Score:2)
I think the intel ones for Android on x86 are open. There are some open drivers coming along to replace the proprietary ones as well.
Re: (Score:2)
the real question is are they doing anything which would warrant hope that tomorrows pad's will ship with gpu's with non-proprietary drivers?.
You are putting the cart before the horse. It's pointless to start targeting hardware before any vendors make commitments to hardware.
There's no point in developing drivers for a framework if you don't have a stable and solid framework in the first place.
Having a solid framework is how you sell the vendors on the software, THEN you can start talking about hardware and drivers.
Re: (Score:2)
Re: (Score:2)
Valid reason for what? Huh?
My understanding is that Android has become fractured between all the different companies' versions of the OS (as they correspond to their different hardware releases). So maybe their aim is to make WebOS be "another Android". Different companies will take their, vanilla, "WebOS" and fragment it out onto their devices.
Re: (Score:2)
When android development was started, there weren't ANY devices available that would run it.
Yes there were, although they were clunky developer boards with touchscreens attached. Once there was a shipping version, future versions were developed on the hardware that the current generation used, until new hardware was built, and then development continued there. In contrast, WebOS was shipped on several devices, none of which can run the new version, and there are no new devices available to replace them.
Re: (Score:2)
so you are saying I am right, there were no devices on the market
today we use virtual machines for developing operating systems, you don't need hardware for application development.
so you see, lack of hardware doesn't have to slow down development of a new platform
Re: (Score:3)
If you really think about it (Score:1)
This needed to happen for webOS to grow as an OS and as a community.
Re: (Score:2)
It's going to grow by not being able to run on anything?
Re: (Score:2)
Test it in a modified VM?
Re: (Score:2)
sell it to hardware vendors just like any other os would do
Re: (Score:1)
And which phone or tablet is that VM going to run on?
Re: (Score:2)
HP saying "bye WebOS" (Score:4, Insightful)
I submit a conspiracy theory (Score:3)
and it goes like this: "HP was encouraged by MS to buy up palm to take webos and palm out of the market once and for all. HP agreed by getting huge discounts in Windows licensing, enabling them to turn net income of 1.5 billion in a quarter when they're doing bad. HP Touchpad fits as a prototype WinRT device and once it became apparent WinRT was going to take longer than expected and the released in unison with Win8-desktop HP dumped all their arm tablets off."
of course it doesn't fit too well with some per
Call to Arms for the webOS Community! (Score:5, Informative)
Yeah, it is a slap in the face, but understandable since the old hardware needed proprietary drivers to work.
However, there is good news, as mentioned in this post at webOS Nation [webosnation.com] :
"There are two things to keep in mind moving forward. One: there's a large and growing number of Android devices out there that offer support for the Linux Standard Kernel 3.3, and given the number of devices supported by the open source CyanogenMod Android project there are plenty of drivers available for those components. Two: The webOS homebrew community cannot and will not be held back. They've already started working on the webOS Community Edition release of LunaSysMgr to see how well they can get it to work on the Pre3, and it'll only be a matter of time before they figure out how to get the goodness of Open webOS to work on our current webOS devices, HP be damned."
Re: (Score:2)
But what would drive adoption? I can see a small body of WebOS (and FirefoxOS) fans, myself among them, trying this out for fun. But what will make the market share of either move from 0.0001% to 0.001%, let alone 1% or 5%?
New Speak garbage (Score:3)
Re: (Score:2)
You obviously never G'd the N. Pity.
Re: (Score:2)
Re: (Score:2)
I have an HP Touchpad (Score:3)
I have not booted into WebOS for two months. The Cyanogenmod android is grreat. Only hangup left is the camera, which apparently is stymied by a closed-source Qualcomm driver. Why Qualcomm will not release driver info is beyond me - what do they have to lose?
Anyway, WebOS is history.
Re: (Score:2)
what do they have to lose?
Maybe a lawsuit to the company that wrote it?
Re: (Score:2)
What makes a Qualcomm camera different from some generic Chinese camera? The hardware? Probably not. The only differentiating factor may be the driver which does special stuff.
Therefore, releasing the driver is effectively ending the product and turning any future profits in that area over to a Chinese company.
Touchpad (Score:2)
...we are aiming for support on future hardware platforms.... Existing devices cannot be supported because of those many proprietary components....
Good thing that it was so easy to install ICS on my Touchpad. I feel sorry for all those not-too-technically-savvy folks who bought one but will never be able to upgrade their devices. HP still sucks.