On Fri, Sep 18, 2015 at 9:15 AM, Daniel van Vugt
wrote:
> For mobile it totally makes sense.
>
> For desktop I think you will find people will want to run
> "unsigned/untrusted" "legacy" apps quite a lot :)
>
>
Maybe, and if a terminal app is unconfined/unconditionally trusted,
that property woul
For mobile it totally makes sense.
For desktop I think you will find people will want to run
"unsigned/untrusted" "legacy" apps quite a lot :)
On 18/09/15 15:13, Michał Sawicz wrote:
W dniu 18.09.2015 o 09:05, Daniel van Vugt pisze:
Sounds like an improvement, thanks. In the long term thoug
W dniu 18.09.2015 o 09:05, Daniel van Vugt pisze:
> Sounds like an improvement, thanks. In the long term though, I think you
> will find power users (and even some apps) want to launch non-Qt apps by
> simply executing them. Eventually (as with any other desktop OS) they
> will need to /just work/.
Sounds like an improvement, thanks. In the long term though, I think you
will find power users (and even some apps) want to launch non-Qt apps by
simply executing them. Eventually (as with any other desktop OS) they
will need to /just work/. So any wrapper will need to go away.
On 18/09/15 15
W dniu 18.09.2015 o 06:01, Daniel van Vugt pisze:
> Admittedly that's a bit hackish. So coming in Mir 0.16.0 more of the
> demo clients will understand the '--' option allowing for graceful
> command line augmentation. Although it would be even better if Unity8
> didn't have the requirement.
It do
Some might have figured this out already, but you can actually trick
Unity8 into accepting regular Mir clients like those from the mir-demos
package. All you need to do is hide the magic desktop_file_hint string
on the command line in such a way that the client itself does not reject it:
mir_d
