Does AOSP ship on Android phones? Not generally. Carriers and vendors tailor the Android source code to their specific requirements.
Same thing applies here. If Telefonica want to supply additional functionality to their target Brazilian market, they have the option of taking the source and augmenting it with proprietary codecs.
Even if developers absolutely love developing for FirefoxOS, there won't likely be a market for it.
There's very little 'developing for' going on here. These are standard web pages. Written in HTML and JS. The same web page that will run on your desktop browser. All that changes is skinning for a smaller screen.
Any 'native' functionality is called by invoking a library built into the JavaScript engine. All of these libraries are slated for submission to the web standards authority, W3C.
I think it's important to recognise the goals of the Mozilla project and hence the overall goals of Firefox OS. Mozilla isn't a commercial venture in the traditional sense. Netscape crashed and burnt. What remains is one of the larger open source hacker cultures whose mission is to advance the web.
Firefox OS exists because the existing developers of Firefox decided it would be fun. Any 'market' gained by this venture will see revenue channeled back into development. The coders keep receiving paychecks for writing open source.
When these WebAPI modules trickle into webkit and Android, mission accomplished. Developers will then be able to target mobile devices with full functionality using standard web technologies.
Any commercial risk of establishing a market to compete with Android and iPhone is outside the Mozilla organisation. A telco is putting up the cash.
The cheapest discount price online in Australia currently is around $AU469 for an unlocked Lumia 900. Or $10 a month on a $30 plan from Optus - for the equivalent of a $20 a month BYO phone plan.
So the true cost of the phone to the consumer is in the same ball park as the $450!
Mer inherits its infrastructure from Meego, so is rpm based.
Being free software, nothing is stopping the community from repackaging the software, submitting them to the debian repositories and creating phone boot images.
You're invoking -X, which implies an X session. I wouldn't expect it to 'display natively' as Wayland.
However, they do talk about embedding X servers on top of wayland, so wrapping a remote application by spawning a X session on your local Wayland desktop seems feasible.
If the vision is true, such teething problems in backwards compatibility should disappear. Remoting 'Wayland-specific applications' without an X11 fallback is a different matter.
This implementation doesn't use share any Xorg legacy but rather cobbles together an implementation based on the graphics APIs exposed by the Android SDK.
An eventual goal might be to replace the display technology - Google proprietary (aosp) SurfaceFlinger with a Wayland compositor. Thus with, say, CM13 your tablet would be able to run Android apps seamlessly alongside KDE Plasma apps. On the desktop, Android apps would thus interact with Unity on Ubuntu Wistful Wombat.;-)
Is there such a thing as a "Wayland app"? My understanding is that the ability to run GUI applications depends on the various toolkits such as GTK+ and Qt being ported to be Wayland native. Such applications thus don't have any direct dependency on X11 nor Wayland.
Rather, the application would load a shared library which selects a display backend seamlessly at runtime. The choice to utilize Wayland, local X or remote could be handled more or less transparently, e.g. as the DISPLAY variable currently does.
X11 support isn't going to disappear overnight from the common toolkits any more than Qt and GTK+ will cease to exist on non Unix platforms. e.g. Gimp and Pidgin run fine on Windows, Qt runs on the Playbook.
A 1Ghz P3 with a decent amount of RAM and a non-sucky video card should run Kubuntu 12.04 adequately - if not at warp speed.
Anyway, hardware sold in 2010 (512MB, 800Mhz CPU) should be fine to run something newer than Gingerbread. My phone's support ran out at Froyo, however. Chugging along with CM 7.2.0, though it might be a few months before volunteers release 9.0
I turned off MS Word's after too many false positives such as eliminating the passive voice - I don't need some bullshit rule telling me my thoughts are invalid.
Slashdot Mirror
Does AOSP ship on Android phones? Not generally. Carriers and vendors tailor the Android source code to their specific requirements.
Same thing applies here. If Telefonica want to supply additional functionality to their target Brazilian market, they have the option of taking the source and augmenting it with proprietary codecs.
There's very little 'developing for' going on here. These are standard web pages. Written in HTML and JS. The same web page that will run on your desktop browser. All that changes is skinning for a smaller screen.
Any 'native' functionality is called by invoking a library built into the JavaScript engine. All of these libraries are slated for submission to the web standards authority, W3C.
I think it's important to recognise the goals of the Mozilla project and hence the overall goals of Firefox OS. Mozilla isn't a commercial venture in the traditional sense. Netscape crashed and burnt. What remains is one of the larger open source hacker cultures whose mission is to advance the web.
Firefox OS exists because the existing developers of Firefox decided it would be fun. Any 'market' gained by this venture will see revenue channeled back into development. The coders keep receiving paychecks for writing open source.
When these WebAPI modules trickle into webkit and Android, mission accomplished. Developers will then be able to target mobile devices with full functionality using standard web technologies.
Any commercial risk of establishing a market to compete with Android and iPhone is outside the Mozilla organisation. A telco is putting up the cash.
The cheapest discount price online in Australia currently is around $AU469 for an unlocked Lumia 900. Or $10 a month on a $30 plan from Optus - for the equivalent of a $20 a month BYO phone plan.
So the true cost of the phone to the consumer is in the same ball park as the $450!
Mer inherits its infrastructure from Meego, so is rpm based.
Being free software, nothing is stopping the community from repackaging the software, submitting them to the debian repositories and creating phone boot images.
Around the time yanks learn to spell 'metre'.
meter = A thing to put coins in when parking a car.
metre = A measurement of length.
Do LAN even fly to Asia?
I know they fly all over South America, to Europe and AUS/NZ...
You're invoking -X, which implies an X session. I wouldn't expect it to 'display natively' as Wayland.
However, they do talk about embedding X servers on top of wayland, so wrapping a remote application by spawning a X session on your local Wayland desktop seems feasible.
If the vision is true, such teething problems in backwards compatibility should disappear. Remoting 'Wayland-specific applications' without an X11 fallback is a different matter.
Well in the case of Android, Wayland is coming!
This implementation doesn't use share any Xorg legacy but rather cobbles together an implementation based on the graphics APIs exposed by the Android SDK.
An eventual goal might be to replace the display technology - Google proprietary (aosp) SurfaceFlinger with a Wayland compositor. Thus with, say, CM13 your tablet would be able to run Android apps seamlessly alongside KDE Plasma apps. On the desktop, Android apps would thus interact with Unity on Ubuntu Wistful Wombat. ;-)
Is there such a thing as a "Wayland app"? My understanding is that the ability to run GUI applications depends on the various toolkits such as GTK+ and Qt being ported to be Wayland native. Such applications thus don't have any direct dependency on X11 nor Wayland.
Rather, the application would load a shared library which selects a display backend seamlessly at runtime. The choice to utilize Wayland, local X or remote could be handled more or less transparently, e.g. as the DISPLAY variable currently does.
X11 support isn't going to disappear overnight from the common toolkits any more than Qt and GTK+ will cease to exist on non Unix platforms. e.g. Gimp and Pidgin run fine on Windows, Qt runs on the Playbook.
A 1Ghz P3 with a decent amount of RAM and a non-sucky video card should run Kubuntu 12.04 adequately - if not at warp speed.
Anyway, hardware sold in 2010 (512MB, 800Mhz CPU) should be fine to run something newer than Gingerbread. My phone's support ran out at Froyo, however. Chugging along with CM 7.2.0, though it might be a few months before volunteers release 9.0
Hackers wanted: Replicant
As opposed to the Kelsey Grammar School featured in Little Britain!
"For whom"?
Touche - such is the over-reliance on defective tools that don't differentiate between homophones.
Grammar checkers can die a miserable death.
I turned off MS Word's after too many false positives such as eliminating the passive voice - I don't need some bullshit rule telling me my thoughts are invalid.
Crazy or just plain HOT? You decide :)
Many of us have never seen webOS - e.g. the Palm Pre series was never sold in my country.
Hildon is being revived as a sub project of Mer.
Cordia Hildon-Desktop.
If Android apps, there's always BB10 on the horizon - if it ever ships...
All desktops have wifi? Those that bother to have wifi on the motherboard will probably have Bluetooth too.
A bluetooth dongle for usb will cost you a few dollars on ebay.
I want to know why kim.com just has a blank 'Coming Soon' page.
The late Steve declared keyboards were bad, so every second-rate Jobs wannabe declared keyboards had to go.
Nokia's last horizontal slider phone, I believe, was the E7 released in Feb 2011.
RIM, for the time being, offers vertical sliders.
Of course MS will benefit. Their ARM Surface computers will fail due to lack of win32 x86 compatibility.
2015 will be the year of Office on 64bit Android.
Yes, software patents accelerate climate change.
Petition presidential hopeful Mitt Romney to abolish them on environmental grounds? :)
Haha.The American language forked from 'English' in 1776. Any mutual intelligibility is purely coincidental! :)