Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

I admit I haven't studied them very much (I'm still a bit behind, on Qt4.8) but AIUI QtQuick controls are meant to be for all kinds of interfaces

for example
http://doc-snapshot.qt-project.org/q...ols/touch.html

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

..lay down the weeds, Dude. They aren't healthy.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

Great, and since these are supposedly common Qt components, one could expect to find those available on each Qt enabled platform, which makes applications more generic. It makes sense for those who aim at crossplaform reach (for example for IPC Embedlite Firefox). I guess in some cases specific components like Silica can be a plus too, but they tie the result to them and their availability.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

No I can't because you seems to not understand that X11/XWayland IS deadend. Compabiltiy wrappers makes more stuff to debug.

But why on earth should they stick with X11 on a new embedded Linux platform? its 2013 for got sake not 1990 with server/client thinking on desktop.

But I am sure there will be thirdparty packaget to install for those who wanna play with such "toys"

X11 has been broken for long even on desktop linux. The biggest drawback for Linux IS X11 escpecially for 3D(And yes thats a bigg issue on embedded) rendering for gamers, graphics but also video rendering. Fact stand the X11 technology is to old and def not for embedded or desktop. Its for remote server administration machines from the begining and then it has been "hacked" for years to make it work better on desktop but now it has come to the fact that it need to be replaced.

Seriously it sounds more like people want X11 to tell others "hey I can run foobar X11 app on my phone" even if that X11 app will be a pointless toy cause it is unusable on a phone anyway.


Wayland or/and maybe MIR IS the future of Linux on embedded. And even on dekstop Wayland/Mir is the future if it want to be a competitor for games and graphics etc... And the biggest reason is again 3D Graphics.


Ofcourse there will be apps that will not work, especially apps that is not written in Gtk or Qt but most are anyway. And port apps from Qt4 -> Qt5 should not be an big issue for most developers AFAIK most of the API is not changed and QTQuick1(means harmattan components shoudl work) still exist in Qt5.

And Qt team gave tip already 2011 what Qt API should be avoided to be compatible in the future.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

To late check now but if I remember correct there is also some kind of "theming API" in QtQC to make a custom look and feel on the widgets.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

@wayland vs X11
There is still the issue of network transparency. While not really that important in out case (mobile/embedded application development), it still stands that it is something X11 has and Wayland is lacking so far.

Yes, this has been already discussed elsewhere quite heavily and yes, it should be possible to do it with Wayland using pixel scrapping.

But it still stands there is no such implementation in the current Wayland/Weston implementation.

Network transparency use-cases
From personal experience these work just fine on local (100 Mb Ethernet) network & are quite handy(as the application context stays on one machine, but the application can be used on many other machines):

• graphical terminal emulators
• Geany (wrote my bachelors thesis like this) and other editors
• Thunderbird
• Inkscape
• modRana :)

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

Wayland will implement its own network transparency, which will even allow using Wayland natively for stuff like what Nx (Nomachine protocol) does today, where X11 is just a performance hog. It's just that Wayland doesn't prioritize that aspect.

See https://www.youtube.com/watch?v=L8zwnqKysfI&t=1h11m51s

By the way. Weston is not part of Wayland - it's a reference compositor. Actual DEs, including the mobile ones will implement their own compositors, and I guess they'll have to support such features if Wayland will define a stable protocol for network transparency.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

Note this in the Sailfish video (at 16:10)

Similar to what Stskeeps said, but sounds a bit more optimistic (he said "that will not remain as such", whatever that means).

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

Why I think I've already seen the same back in 2010-2011?

Scratch GTK in favor of Qt. Scratch Maemo, rush for Meego. Debian packaging is working fine? So what, go for rpm.

Toldya, no way to make a new whorehouse with the old whores :)

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

The same what? Switch to Qt and RPM was in Meego. Mer continues it. Nothing new in this aspect. You are several years late to complain.