Re: The case for a "SceneGraph"

2013-07-23 Thread Thomas Voß
On Tue, Jul 23, 2013 at 6:01 PM, Gerry Boland wrote: > On 19/07/13 13:34, Alan Griffiths wrote: >> On 19/07/13 10:55, Michał Sawicz wrote: >>> I'm sure it was discussed before, but can you guys please give me a >>> summary why it's not possible to just keep the shell's scenegraph (in >>> our case

Re: Old package mir Saucy

2013-07-25 Thread Thomas Voß
Hi Igor, nope, the system-compositor-testing ppa is the place where we cherry pick the latest changes from the staging ppa, so it's a bit behind right now to keep it stable. However, we hopefully land in distro soon. HTH, Thomas On Thu, Jul 25, 2013 at 9:32 PM, Игорь Зубарев wrote: > Hello,

Re: Component clarification

2013-11-05 Thread Thomas Voß
On Tue, Nov 5, 2013 at 11:34 AM, Alexandros Frantzis wrote: > On Mon, Oct 28, 2013 at 10:41:29AM +0800, Daniel van Vugt wrote: >> Yeah, very good point about "gbm". That confused me when I joined to >> project too. It should be called "dri", I think. > > What about just "mesa"? I think "mesa" is m

Re: Untangling EventHub/InputReader

2013-11-11 Thread Thomas Voß
On Mon, Nov 11, 2013 at 1:33 PM, Daniel d'Andrada wrote: > Hi Christopher, > > The job of EventHub, in short, is multiplexing the event streams from all > those /dev/input/event* files into a single output stream of events (those > events then having device ids to identify from which device they c

Re: Hold on

2013-11-12 Thread Thomas Voß
Hey all, just following up here and reporting that a fix has been committed: https://code.launchpad.net/~robertcarr/mir/fix-1249210 Cheers, Thomas On Fri, Nov 8, 2013 at 10:19 AM, Daniel van Vugt wrote: > There seems to be a significant performance regression crept into the Mir > code thi

Re: Component clarification

2013-11-19 Thread Thomas Voß
On Tue, Nov 19, 2013 at 3:18 PM, Alan Griffiths wrote: > I think the natural domain name is "scene". > +1. > It was the first suggestion and was only doubted because we've it > misinterpreted as implying that it /is a/ scenegraph (rather than /has a/ > scenegraph). > > In the absence of a cleare

Re: Subsurface support, or delegated compositing

2013-11-24 Thread Thomas Voß
On Mon, Nov 25, 2013 at 7:51 AM, Christopher James Halse Rogers wrote: > One of the architectural things that I want to get done at the sprint > next week is a solid idea of how we want to do nested > compositing/out-of-process plugins/subsurfaces - which all seem to me to > be aspects of the same

Re: screenshotting, screencasting & unity8+mir

2013-11-26 Thread Thomas Voß
On Tue, Nov 26, 2013 at 1:31 PM, Daniel d'Andrada wrote: > Hi, > > On November 26th I (Unity8), Kevin Gunn, Chris Gagnon (Autopilot) and > Alexandros Frantzis (Mir) had a meeting on the requirements and > implementation of screenshotting and screencasting. > > Chris told us that what autopilot rea

Re: screenshotting, screencasting & unity8+mir

2013-11-26 Thread Thomas Voß
On Tue, Nov 26, 2013 at 4:12 PM, Alexandros Frantzis wrote: > On Tue, Nov 26, 2013 at 01:13:28PM +, Gerry Boland wrote: >> Hey, >> The system compositor will probably not be using the Qt scenegraph, but >> instead Mir's own compositor. I don't know if using >> QQuickWindow::grabWindow() will w

Re: screenshotting, screencasting & unity8+mir

2013-11-26 Thread Thomas Voß
On Wed, Nov 27, 2013 at 2:38 AM, Daniel van Vugt wrote: > On an implementation note... > > I think adding yet more library dependencies (dbus) to Mir would be a > mistake. It's already quite bloated in that respect. > +1, Mir should expose the required functionality via its server-side interfaces

Fwd: screenshotting, screencasting & unity8+mir

2013-11-27 Thread Thomas Voß
-- Forwarded message -- From: Thomas Voß Date: Tue, Nov 26, 2013 at 2:15 PM Subject: Re: screenshotting, screencasting & unity8+mir To: Daniel d'Andrada Cc: mir-devel@lists.ubuntu.com On Tue, Nov 26, 2013 at 1:31 PM, Daniel d'Andrada wrote: > Hi, > > On

Re: Shell communication channel: simple, half-assed or fully-arsed?

2013-12-12 Thread Thomas Voß
On Thu, Dec 12, 2013 at 5:46 AM, Christopher James Halse Rogers wrote: > On Thu, 2013-12-12 at 10:01 +0800, Daniel van Vugt wrote: >> "Half-assed" is inaccurate I think. Under that heading you describe >> what we had already agreed to do (as much as the team can agree on >> something). > > *I* tho

Re: Shell communication channel: simple, half-assed or fully-arsed?

2013-12-12 Thread Thomas Voß
On Thu, Dec 12, 2013 at 11:02 AM, Alan Griffiths wrote: > On 12/12/13 09:34, Thomas Voß wrote: >> I don't see why we need a way to extend the protocol. We own every >> part of the stack, top to bottom, and I don't see why the shell would >> need a way to communica

Re: Shell communication channel: simple, half-assed or fully-arsed?

2013-12-12 Thread Thomas Voß
On Thu, Dec 12, 2013 at 11:11 AM, Christopher James Halse Rogers wrote: > On Thu, 2013-12-12 at 10:34 +0100, Thomas Voß wrote: >> On Thu, Dec 12, 2013 at 5:46 AM, Christopher James Halse Rogers >> wrote: >> > On Thu, 2013-12-12 at 10:01 +0800, Daniel van Vugt wrot

Re: Shell communication channel: simple, half-assed or fully-arsed?

2013-12-12 Thread Thomas Voß
On Thu, Dec 12, 2013 at 11:42 AM, Thomas Voß wrote: > On Thu, Dec 12, 2013 at 11:11 AM, Christopher James Halse Rogers > wrote: >> On Thu, 2013-12-12 at 10:34 +0100, Thomas Voß wrote: >>> On Thu, Dec 12, 2013 at 5:46 AM, Christopher James Halse Rogers >>> wrote:

Re: Input latency

2013-12-15 Thread Thomas Voß
On Mon, Dec 16, 2013 at 7:30 AM, Daniel van Vugt wrote: > Yes indeed. I did think about that, but if you look at the merge proposal > it's all about using the existing reports unmodified right now. And my > primary task was to assess the feasibility of nesting vs non-nested. > > I wasn't going to

Re: Input latency

2013-12-15 Thread Thomas Voß
LTTNG talk in London but was trapped in a > meeting at the time :) > > > > On 16/12/13 14:44, Thomas Voß wrote: >> >> On Mon, Dec 16, 2013 at 7:30 AM, Daniel van Vugt >> wrote: >>> >>> Yes indeed. I did think about that, but if you look at the merge

Re: Nested servers frame rate

2013-12-18 Thread Thomas Voß
On Wed, Dec 18, 2013 at 9:43 AM, Daniel van Vugt wrote: > At first glance, comparing frame rates between direct (single) and nested > (double) server configurations reveals nothing unexpected... > > Full screen > Direct (bypass) 2600 > Direct (bypass off) 2400 > Nested (bypass) 2450 > Nested (bypa

Re: Nested servers frame rate

2013-12-18 Thread Thomas Voß
the client as > soon as they're available. > Fair, but I would like to see numbers on the roundtrip penalty you are suspecting here, first :) Cheers, Thomas > > > On 18/12/13 16:58, Thomas Voß wrote: >> >> On Wed, Dec 18, 2013 at 9:43 AM, Daniel van Vugt >>

Call For Testing: Valgrind update

2014-03-31 Thread Thomas Voß
Hey all, Matthias is preparing an update of valgrind in the archive. As both mir and unity-scopes-api are heavy users of valgrind, he asked us for testing if the current build setups still work with the update. The overall request including links to a PPA is available here: https://bugs.launchp

Re: Clients reading their surface position on screen

2014-07-22 Thread Thomas Voß
Hey all, so reading Gerry's initial mail, it seems to me that autopilot does not actually want to deal with absolute screen coordinates (and take on the burden of figuring out multi-monitor, multi-dpi cases on its own) but instead wants to say: Please Mr. Mir, for this surface with ID id, send an

Re: Clients reading their surface position on screen

2014-07-22 Thread Thomas Voß
On Tue, Jul 22, 2014 at 11:11 PM, Thomi Richards wrote: > Hi, > > On Tue, Jul 22, 2014 at 8:01 PM, Thomas Voß > wrote: >> >> so reading Gerry's initial mail, it seems to me that autopilot does >> not actually want to deal with absolute screen coordinates (an

Re: Clients reading their surface position on screen

2014-07-22 Thread Thomas Voß
On Wed, Jul 23, 2014 at 5:05 AM, Christopher James Halse Rogers wrote: > On Wed, Jul 23, 2014 at 7:11 AM, Thomi Richards > wrote: > … >> >> >> This may, or may not all be true, but none of it helps solve the problem >> :) >> >> >> I think this conversation is drifting away from the original point

Re: Client API philosophy

2014-11-10 Thread Thomas Voß
On Mon, Nov 10, 2014 at 10:58 AM, Alan Griffiths < alan.griffi...@canonical.com> wrote: > On 10/11/14 03:31, Daniel van Vugt wrote: > > > > Sounds like a response to one of my merge proposals. So please put > > arguments in the code reviews... > > There's a good reason to discuss this outside of a

Re: RFC Playground

2015-04-01 Thread Thomas Voß
On Wed, Apr 1, 2015 at 6:50 PM, Cemil Azizoglu wrote: > I agree with Alberto that we should try to get (people) away from using > playground as a validation tool and onto mir_demo_server (after 0.13). We > then move the renderer related things to the public realm. > > Reiterating the original int

Re: RFC Playground

2015-04-02 Thread Thomas Voß
On Thu, Apr 2, 2015 at 4:36 AM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > All the features are useful. And use of the word "playground" was not my > choice (I was outvoted). They have all been used to develop other features > or to diagnose bugs in Mir, or soon will be used when I

Re: Mir support in Qt5.6 upstream!

2015-08-10 Thread Thomas Voß
Awesome \o/ Thanks for taking care of it Gerry :) Cheers, Thomas On Tue, Aug 11, 2015 at 3:46 AM, Daniel van Vugt wrote: > Nice work. > > On the Mir side we should also upstream the Mesa work. Although there are > some bugs open there that we should fix first. > > > > On 10/08/15 21:58, Gerry

Re: Fun with Unity8

2015-09-18 Thread Thomas Voß
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

Re: Client display configuration notification

2015-10-21 Thread Thomas Voß
On Wed, Oct 21, 2015 at 12:21 PM, wrote: > On Tue, Oct 20, 2015 at 11:16 PM, Gerry Boland > wrote: >> >> Hey folks, >> it appears this topic has gone stale, without any consensus being reached. >> A core issue impacting this discussion which remains undecided is the >> following: >> >> - Is it i

Re: Client display configuration notification

2015-10-21 Thread Thomas Voß
On Wed, Oct 21, 2015 at 4:38 PM, Alan Griffiths wrote: > On 21/10/15 11:38, Thomas Voß wrote: >> Well, we always need to satisfy the case of handing configuration up & down a >> nested shell scene. If we don't add the respective functionality to >> the client api, we

Re: Regarding running Android LXC guest in Ubuntu touch by using Mir

2016-01-08 Thread Thomas Voß
On Fri, Jan 8, 2016 at 2:55 AM, Daniel van Vugt wrote: > That all said, there might be a short-cut. If you accept that it may > only work on Ubuntu phones that were formerly Android phones, then with > maybe some weeks/months of effort you might be able to build the > required translation layers f

Re: Regarding running Android LXC guest in Ubuntu touch by using Mir

2016-01-08 Thread Thomas Voß
with attachment now :) T On Fri, Jan 8, 2016 at 2:49 PM, Thomas Voß wrote: > On Fri, Jan 8, 2016 at 2:55 AM, Daniel van Vugt > wrote: >> That all said, there might be a short-cut. If you accept that it may >> only work on Ubuntu phones that were formerly Android phones,

Re: What we do and don't expose to client toolkits

2016-09-02 Thread Thomas Voß
On Thu, Sep 1, 2016 at 1:02 PM, Alan Griffiths wrote: > When clients toolkits provide hints to place child surfaces using the > existing functions: > > mir_surface_spec_attach_to_foreign_parent(); > mir_connection_create_spec_for_tip(); > mir_connection_create_spec_for_menu(); or the proposed, > m