It seems that there is such a package
although this stopped being shipped after 15.10. Not sure why
In any case I plan to have a look at it at some time.
Anbox appeared (https://anbox.io/) so there are guys who will try the same, maybe even in a better way.
That's interesting. Maybe it can be seamless integrated in Yunit in a similar way that X11 apps are integrated
Qt Quick Controls should be took as a base.
Why not kirigami?
I was actually hoping to investigate that option in Yunit sometime in the future.
I want just to have the ability to migrate running applications from desktop to phone and vice versa. Obviously in order to do that, as a start you need to have the same OS/apps in both systems (see convergence).
Also an important issue for me with today's phones is that applications come from different vendors and there are no common frameworks for interoperability, especially related to context information each application can handle. For example I would love to have a phone that based on my current status (ie on a meeting), which can be inferred by the calendar application's context, automatically switches to silent mode, or if it automatically switches to vibration mode if you are in a noisy environment, or if during the night turns to silent mode (based on the lights level and location) and allows only calls from people in your contact list to wake you up, etc.
Hope yuniy will get there
So. Should I make it a priority to have yunit compiled against Qt 5.7 on top of ubuntu 16.04? If I have a working set of deb (and deb-src) packages, can you take it from there, or do I need to do something else?
My biggest concern is who's going to maintain UITK - we can consider it stable enough, although UITK devs were planning a huge rewrite for v2.0 (performance issues and bugs, mainly)
Well.... I guess yunit should maintain it as it is a build dependency
In any case yunit should maintain it until it is not needed any more
@jsalatas Can I presume that you're working on Debian Sid then?
Yes. that is correct! I have already a working desktop in sid (using qt 5.7)
Using Qt packages built by Plasma Mobile (5.7) or KDE Neon
I would suggest this for now. Given that we want to run it on top of 16.04 and given that KDE Neon already has 5.7 packages that are running on top of 16.04, I believe this is the safest path to follow.
In fact, I already proposed that I could try to backport the desktop part to 16.04 if that will be of any help to you.
Having QtQuick Controls 2 would be a great thing, as:
We could stop maintaining Ubuntu UI Toolkit, which is quite huge
Are we talking about this https://launchpad.net/ubuntu-ui-toolkit ?
If so then, it is still a dependency for yunit.
To recap: my opinion is that we should go one step at a time. I would suggest that the first step should be to backport the code I currently have (from ubuntu 17.04) to 16.04 and I believe I can have it pretty soon for the desktop part if that would be of any help to you.
Qt 5.9 is a no go from my part, as we don't have yet a CI infrastructure so we eventually cannot touch any code, yet
Edit: After discussing a bit with @jsalatas and rereading messages from @bshah, I found that this discussion had a grave flaw. Namely, Plasma isn't working on 5.9 yet, but 5.7. It turns out that Yunit compiles under 5.7 as well. More discussion of this point is still needed, but I thought this was a big enough issue to warrant a strikethrough.
I just had an extensive chat with @UniSuperBox. To be honest after that discussion I realized what you were trying to achieve
Anyway! Currently I confirm the whole Yunit stack can be built against qt 5.7.1. So the issue here is to backport the whole Yunit stack to ubuntu 16.04 which comes with qt 5.5 if I'm wrong. Right?
If this is the case, then I guess I could try to have it done for the desktop. Will that be in any help for you? I mean if I could provide you with a ppa with latest yunit compiled against qt 5.7 that runs on top of ubuntu 16.04, would that be enough for you?
@WebDrake I like the idea of keeping Mir alive
we will not keep it alive. Canonical will do. Until further notice
@WebDrake Actually I would say that my speculation is based on actual facts. What would happen for example if we asked them about unity8 and convergence let's say 3 months ago? They would assure us that everything is set up for 18.04 and stuff like that.
It is obvious to me that whatever they say now about mir xan probably change in the near future.
In any case can we stick to the collaboration between yunit and UBPorts in this topic? And maybe have a different one to discus the mir vs wayland think?