Plasma Active, Sailfish, and Ubuntu Phone Developers Discussing Common APIs
Jolla's Sailfish, Canonical's recently announced Ubuntu Phone, and KDE's Plasma Active environments are all using Qt5's QML for interface design. Unfortunately, the set of UI components provided by each, although similar, are incompatible with the others. After a chat on IRC between developers of all three platforms, they've decided to discuss the reasons behind each implementation, in the hopes that they can work toward a common architecture. "There are also discussions underway regarding other aspects of the bigger puzzle such as common package formats and delivery strategies. We are poised, should we keep our heads straight and our feet moving, to evolve that holiest of grails in the mobile space: an open and vendor neutral application development strategy built around the commonality of QtQuick and Linux. This is our Rome, which will not be built in a day, but which can become something significant in the world if we keep our heads and follow through."
I was pleasantly surprised to see Ubuntu pushing QML/QtQuick on its phone, it's really a great platform.
A great advantage of using pure QML for apps is that it requires no linking, just source compatibility. So Ubuntu's GUI elements could look very different from KDE's, but using the same property names a single app would work and look native on both. If only they agreed on this, it's probably the only way anyone except free software enthusiasts would write software for any of these platforms.
PlusFive Slashdot reader for Android. Can post comments.
This is our Rome, which will not be built in a day, but which can become something significant in the world if we keep our heads and follow through."
Rome died due to lead poisoning and excessive military expenditures. If we're going to become Rome, I suggest BSD instead -- their mascots are a bit more menacing than a penguin. Also, the licensing terms are less restrictive.
#fuckbeta #iamslashdot #dicemustdie
A common architecture would mean the phone manufactures couldn't keep their users locked to the platform where they have all their apps.
Which is why Android has been such a market failure.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
umm...
I can only guess at this, but your comment seems to be lacking vast amounts of FACT... being that I have used Windows for ages and have used MANY different UI's... so saying using Windows is being forced into one UI is a very incorrect statement, and sadly shows great amounts of ignorance on your part (using an alternative UI at the moment on Windows 8 even)
If you where looking for an options limited OS, Mac and iOS are where you need to look. IIRC there where a few for an older version of Mac, but I know of none that fit the definition for iOS
You realize it's possible for two different pieces of software to have quite different UIs, even if they use the same base set of widgets to build that UI, right?
Oh, you're bitching about whether or not the window chrome suits your preferred aesthetics? Then we can safely disregard your bitching in its entirety.
This is why Windows will never be ready for the desktop, with its fragmented UI. Until all the developers working on different UIs for Windows standardize on a single UI it'll just never take off.
an open and vendor neutral application development strategy
That sounds like the near future of HTML5 and more advanced browsers. But when you add...
... well, hmm, ok, the first part sounded great. What's with the second part?