Hi Alan,
mind if I add some questions & comments from the shell PoV?
On 18/07/13 12:27, Alan Griffiths wrote:
>
> So, what do we want from a SceneGraph?
What shell will need is, for every surface, the following properties:
- x, y, z, width, height
- opacity, visible
- scale
- ability to set more
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 the Qt/QML one) in play? Or if there maybe is another way fo
On 23/07/13 19:45, Thomas Voß wrote:
> 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
>
e SG
tree. I think we can do the same. I do need to study QtWayland more closely.
-G
> br,kg
>
>
> On Tue, Jul 23, 2013 at 12:45 PM, Thomas Voß wrote:
>
>> On Tue, Jul 23, 2013 at 6:01 PM, Gerry Boland
>> wrote:
>>> On 19/07/13 13:34, Alan Griffiths wrote:
>&g
Hi folks,
as many of you know, on the current phone/tablet, all the application
switching animations are not done with live surfaces, but instead with
screenshots. This obviously is not ideal, so I want to fix that.
I've been researching ways to more tightly combine Mir surfaces with
Qt/QML, so th
On 26/11/13 12:31, 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 really wants is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/13 14:00, Alan Griffiths wrote:
> I'm trying to summarise some discussions around the need for Mir
> to provide a ABI stable channel of communications to shells and
> client toolkits (such as unity8/platform-api) that make use of it.
> This sh
On 02/06/14 10:08, Alan Griffiths wrote:
> With the current review of "trust session" it is clear that "Session" is
> a bad name for what the scene::Session class represents.
>
> I suggest that we rename it to "Application" as that seems to better
> reflect its role.
>
> Clearly that has the pote
On 09/07/14 16:39, Kevin Gunn wrote:
> First
> Not sure we're still on topic necessarily wrt changing from id's to fd's
> do we need to conflate that with the double/triple buffering topic ?
> let's answer this first...
>
> Second
> while we're at it :) triple buffering isn't always a win. In the
Hey folks,
in working on QtCompositor, I stumbled across a problem ([1]).
Autopilot needs to know the position of items in an application
(buttons, etc) in screen coordinates - not surface. It needs that as it
generates inputs via uevent, which are defined in screen coordinates.
To calculate abso
Hey folks,
this discussion fizzled out and a conclusion wasn't clear to me. I've
taken the liberty to summarize where the discussion got so far.
The options considered possible (1. was dismissed):
2. AP injects events directly into Qt/unity8
Requires unity8 to be in a "testing" mode. Qt would
On 12/08/14 03:33, Christopher James Halse Rogers wrote:
> On Tue, Aug 12, 2014 at 3:09 AM, Gerry Boland
> wrote:
> > Personally I don't like the idea of clients being able to ask for their
> > on-screen position - really there's only a couple of valid use-cases,
>
On 13/08/14 13:59, Daniel d'Andrada wrote:
> I've yet another suggestion:
>
> unity8 provides a D-Bus API for autopilot to ask "hey, what's the
> position/transformation of surface X?". Then AP would apply that
> transformation to a surface local coordinate and send the resulting
> global coordina
On 14/08/14 00:31, Christopher James Halse Rogers wrote:
> Ok. I think we've explored all the relevant options
>
> If I implemented
>
> mir_debug_surface_coord_to_screen(MirSurface, int x, int y, int* outx,
> int* outy)
>
> in libmirclient-debug and hooked it up to a --debug flag, who would
> ob
On 15/08/14 00:56, Christopher James Halse Rogers wrote:
> On Fri, Aug 15, 2014 at 9:32 AM, Gerry Boland
> wrote:
> > On 14/08/14 00:31, Christopher James Halse Rogers wrote:
> >> Ok. I think we've explored all the relevant options
&
On 15/08/14 08:17, Christopher James Halse Rogers wrote:
> On Fri, Aug 15, 2014 at 5:14 PM, Gerry Boland
> wrote:
> > On 15/08/14 00:56, Christopher James Halse Rogers wrote:
> >> On Fri, Aug 15, 2014 at 9:32 AM, Gerry Boland
> >> wrote:
> >> >
On 15/08/14 08:27, Christopher James Halse Rogers wrote:
>
>
> On Fri, Aug 15, 2014 at 5:21 PM, Gerry Boland
> wrote:
> > On 15/08/14 08:17, Christopher James Halse Rogers wrote:
> >> On Fri, Aug 15, 2014 at 5:14 PM, Gerry Boland
> >> wrote:
> >>
Yep, I was aware of this, so was happy that you guys landed the touch
processing stuff. I hadn't noticed that Qt landed this change though, nice to
know.
-G
On 15/09/14 03:20, Daniel van Vugt wrote:
> How very timely. That's exactly the "touch responsiveness" enhancement
> that we just released
On 04/02/15 15:00, Daniel van Vugt wrote:
> Hi all (and this is directed mostly at the wider world outside of
> mir-team), a quick poll:
>
> Which of these names makes more sense to you?
>
> MirTouchInput = read_all_fingers();
> MirTouchEvent = read_all_fingers();
> MirTouchInputEvent = read_all_
On 09/03/15 09:58, Alan Griffiths wrote:
> Background:
>
> I've been looking at our legacy defaults for window management and came
> across the handle_surface_created() method.
>
> This is used to set the focus to a session after a surface has been
> supplied to the client but before that surface
On 23/03/15 13:12, Alan Griffiths wrote:
> On 23/03/15 02:11, Daniel van Vugt wrote:
>> For the benefit of all future shell developers;
>> I'd like to inherit from "SomethingShell" and get
>> something that works in a few lines without writing additional code.
>> Then I would like to be able to ove
On 28/05/15 17:35, Alan Griffiths wrote:
> There's a comment in unity-system-compositor (src/window_manager.cpp)
>
> // We need to wait for the second frame before marking the session
> // as ready. The first frame posted from sessions is a blank frame.
> // TODO: Solve this issue at it
On 19/06/15 11:22, Alexandros Frantzis wrote:
> Hello all,
>
> there have recently been a few occasions where we wanted to experiment with
> performance improvements, but lacked a way to easily measure their effect.
> There have also been a few occasions where different implementations of the
> (s
No objection here
-G
On 22/07/15 02:08, Daniel van Vugt wrote:
> +1
>
> On 21/07/15 18:00, Alexandros Frantzis wrote:
> > Hi all,
> >
> > in the Mir project we are following the standard practice of forking off
> > a new branch from trunk for each (minor) release. The benefits of this
> > approach
On 30/07/15 21:27, Robert Carr wrote:
> Hi Everyone,
>
> This Friday will be my last day at Canonical. I'd love to say good bye
> to everyone in person on some Friday Happy Hour, but alas...mailing
> lists it will be.
>
> I feel so grateful not only to have had these 4 years at Canonical but
> to h
Hey,
so getting anything landed this past month has been a right pain.
If Mir has problems, QtMir is totally blocked from landing any code
until they're resolved. If QA is backed up, we can't land anything.
And right now, the GCC5.0 transition has the train blocked for Wily.
That's a much more un
Hey folks,
a quick announcement, we have initial support for Qt clients on Mir
(i.e. qtubuntu) upstream in Qt! It'll land in Qt5.6.
https://codereview.qt-project.org/#/c/122984/
A huge thanks to Paul Olav Tvete and the Qt Company for all the work done!
Let's do our best to keep all our developme
Hey folks,
chatting with the UITK guys, they need support for UI scaling (i.e. grid
unit value) per display. I think adding a scale parameter to Mir would
make sense for this. I've written up a proposal here, please have a look
and see what you think:
https://docs.google.com/document/d/1Cr-8qz_3DT
On 30/09/15 09:16, Alan Griffiths wrote:
> On 30/09/15 05:04, Christopher James Halse Rogers wrote:
>> Forked from review¹.
>>
>> I think we're currently handling display configuration events
>> incorrectly, or at least in a way that will be surprising to clients.
>
> I totally agree that the exis
On 01/10/15 17:55, Alan Griffiths wrote:
> On 01/10/15 17:20, Gerry Boland wrote:
>> /me suspecting we'll need a doc.
>
> We will, but at the moment we're still brainstorming requirements.
>
> BTW IIRC at the pocket desktop sprint you were interested in additio
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 in Mir's scope as a display server to provide a client api for
configuring mir server settings like those for displays &
On 15/11/15 13:09, Darren Landoll wrote:
> What is the current status of keyboard and touch input for the Mir
> server and Qt QPA ubuntumirclient plug-in on Snappy 15.04?
>
> I can enable touch spots on the Mir server and verify that touches are
> detected, but my Qt/QML application doesn't appear
Hi,
replt inline
On 01/09/16 13:02, 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
33 matches
Mail list logo
