Re: Any protocol documentation about premultiplied alpha?

2021-09-29 Thread Hoosier, Matt
protocol documentation about premultiplied alpha? CAUTION - EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust the sender and know the content is safe. On Wednesday, September 29th, 2021 at 15:23, Hoosier, Matt wrote: > Would anybody be interested in some kind

Re: Any protocol documentation about premultiplied alpha?

2021-09-29 Thread Simon Ser
On Wednesday, September 29th, 2021 at 15:23, Hoosier, Matt wrote: > Would anybody be interested in some kind of comment inserted into the > documentation for wl_buffer that expresses this implicit expectation? Yeah, I think it would be nice to mention this. But still allow other protocols to ov

Re: Any protocol documentation about premultiplied alpha?

2021-09-29 Thread Hoosier, Matt
Thanks, Pekka/Carsten/Simon. I consider myself duly corrected ;) Apparently my snapshot of Weston wasn't rebased after the master -> main transition, that shader fragment file didn't exist, and I didn't encounter the comment. I admit I didn't recognize the glBlendFunc() clues that already exis

Re: Any protocol documentation about premultiplied alpha?

2021-09-29 Thread Pekka Paalanen
On Tue, 28 Sep 2021 13:16:36 + "Hoosier, Matt" wrote: > Hi there, > > Is there any definitive word about whether or not clients should be > expected or allowed to premultiply alpha the alpha channels in the > normal EGL and linux-dmabuf buffers they send to a compositor? Hi, yes, this is r

Re: Any protocol documentation about premultiplied alpha?

2021-09-28 Thread Carsten Haitzler
On Tue, 28 Sep 2021 13:16:36 + "Hoosier, Matt" said: premultiplpied is the base assumption. you don't need shaders to deal with it - the gl blend func does... the only time you want a shader to deal with "premultiplied" is if the source buffer is NOT premultiplied - you now have to do the ext

Re: Any protocol documentation about premultiplied alpha?

2021-09-28 Thread Simon Ser
Both Wayland and KMS assume pre-multiplied alpha.

Any protocol documentation about premultiplied alpha?

2021-09-28 Thread Hoosier, Matt
Hi there, Is there any definitive word about whether or not clients should be expected or allowed to premultiply alpha the alpha channels in the normal EGL and linux-dmabuf buffers they send to a compositor? I have never seen this practice used with Wayland -- the shaders in the gl-renderer

Re: [PATCH wayland 0/8] protocol: documentation improvements

2016-08-12 Thread Bryce Harrington
On Thu, Aug 11, 2016 at 02:32:57PM -0700, Yong Bakos wrote: > From: Yong Bakos > > This series "fills in the blanks" of all missing summary attributes in > wayland.xml, and massages some inconsistencies I found along the way. > > Patch 1/8 is the meatiest, and incorporates Pekka's feedback from

[PATCH wayland 0/8] protocol: documentation improvements

2016-08-11 Thread Yong Bakos
From: Yong Bakos This series "fills in the blanks" of all missing summary attributes in wayland.xml, and massages some inconsistencies I found along the way. Patch 1/8 is the meatiest, and incorporates Pekka's feedback from the RFC[1]. Patches 2 - 8 Apply changes for consistency, and some minor

Re: [PATCH] doc: Use enum argument type to make links in protocol documentation

2016-02-19 Thread Bryce Harrington
On Fri, Nov 06, 2015 at 04:44:58PM +, Auke Booij wrote: > On 6 November 2015 at 16:27, wrote: > > From: Bill Spitzak > > This is good preparation for when we'll get cross-interface enums. > > Reviewed-by: Auke Booij Thanks, pushed: To ssh://git.freedesktop.org/git/wayland/wayland 3a25

Re: [PATCH] doc: Use enum argument type to make links in protocol documentation

2015-11-06 Thread Auke Booij
On 6 November 2015 at 16:27, wrote: > From: Bill Spitzak This is good preparation for when we'll get cross-interface enums. Reviewed-by: Auke Booij ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailm

[PATCH] doc: Use enum argument type to make links in protocol documentation

2015-11-06 Thread spitzak
From: Bill Spitzak --- doc/publican/protocol-to-docbook.xsl | 26 +++--- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/doc/publican/protocol-to-docbook.xsl b/doc/publican/protocol-to-docbook.xsl index fad207a..532 100644 --- a/doc/publican/protocol-to-do

[PATCH] doc: Use enum argument type to make links in protocol documentation

2015-11-06 Thread spitzak
From: Bill Spitzak Small difference in my version from the one pushed. The argument docs are produced by their own section rather than an if statement, and include the interface name along with the enum name. --- doc/publican/protocol-to-docbook.xsl | 26 +++--- 1 file change

[PATCH 2/2] doc: Use enum argument type to make links in protocol documentation

2015-04-22 Thread Bill Spitzak
--- doc/publican/protocol-to-docbook.xsl | 20 +++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/doc/publican/protocol-to-docbook.xsl b/doc/publican/protocol-to-docbook.xsl index 7b45969..3c4e140 100644 --- a/doc/publican/protocol-to-docbook.xsl +++ b/doc/public

Re: [PATCH 7/8] doc: Add object types and links to arguments int protocol documentation

2015-01-21 Thread Derek Foreman
This seems like a big win to me. Reviewed-by: Derek Foreman On 02/01/15 08:29 PM, Bill Spitzak wrote: > This makes it a lot easier to figure out what is going on! > --- > doc/publican/protocol-to-docbook.xsl | 35 > ++ > 1 file changed, 35 insertions(+) > > d

[PATCH 7/8] doc: Add object types and links to arguments int protocol documentation

2015-01-02 Thread Bill Spitzak
This makes it a lot easier to figure out what is going on! --- doc/publican/protocol-to-docbook.xsl | 35 ++ 1 file changed, 35 insertions(+) diff --git a/doc/publican/protocol-to-docbook.xsl b/doc/publican/protocol-to-docbook.xsl index 723f5e6..ca1308f 100644 -

Re: Protocol documentation

2013-12-02 Thread Peter Hutterer
On Wed, Nov 27, 2013 at 02:16:55PM -0800, Kristian Høgsberg wrote: > > On Tue, Nov 26, 2013 at 02:25:42PM +0100, Jonny Lamb wrote: > > Hi. > > > > I have recently been working on some Wayland protocol stuff and found > > referring to the XML tiresome. Telepathy's D-Bus protocol has a parser > > w

Re: Protocol documentation

2013-11-27 Thread Kristian Høgsberg
On Tue, Nov 26, 2013 at 02:25:42PM +0100, Jonny Lamb wrote: > Hi. > > I have recently been working on some Wayland protocol stuff and found > referring to the XML tiresome. Telepathy's D-Bus protocol has a parser > which outputs pretty HTML from the XML[0] so I took said parser and > modified it

Re: Protocol documentation

2013-11-27 Thread Jonny Lamb
Il giorno mar, 26/11/2013 alle 11.38 -0800, Bill Spitzak ha scritto: > Could the fact that the "reference" has "(new_id)" in it be used to > further put these into a different section called "constructors"? Good idea, done. > Could objects without constructors (like wl_shm or wl_seat) could also

Re: Protocol documentation

2013-11-27 Thread Jonny Lamb
Il giorno mar, 26/11/2013 alle 12.26 -0600, Jason Ekstrand ha scritto: > Thanks! I think that's far easier to read than the stuff publican > dumps. The only problem is that your doc generator doesn't handle > paragraph breaks properly. For instance, the wl_surface.attach > request documentation

Re: Protocol documentation

2013-11-26 Thread Bill Spitzak
That does seem a lot easier to read. And (YEA!) the section "References" indicates the interface(s) used to create an instance. For instance wl_pointer has under "References" (as the only entry) "wl_seat.get_pointer". That really helps a lot! Could the fact that the "reference" has "(new_id)"

Re: Protocol documentation

2013-11-26 Thread Jason Ekstrand
Jonny, Thanks! I think that's far easier to read than the stuff publican dumps. The only problem is that your doc generator doesn't handle paragraph breaks properly. For instance, the wl_surface.attach request documentation is supposed to have 7 paragraphs and they get smashed into one: http://p

Protocol documentation

2013-11-26 Thread Jonny Lamb
Hi. I have recently been working on some Wayland protocol stuff and found referring to the XML tiresome. Telepathy's D-Bus protocol has a parser which outputs pretty HTML from the XML[0] so I took said parser and modified it for the Wayland XML format: core Wayland protocol (as of 5a019e3)

[PATCH v2 24/28] text: Improve protocol documentation.

2013-04-18 Thread Jan Arne Petersen
From: Jan Arne Petersen Signed-off-by: Jan Arne Petersen --- protocol/input-method.xml | 98 +++ protocol/text.xml | 52 - 2 files changed, 106 insertions(+), 44 deletions(-) diff --git a/protocol/input-method.xml b/pr

[PATCH 4/5] text: Improve protocol documentation.

2013-04-15 Thread Jan Arne Petersen
From: Jan Arne Petersen Signed-off-by: Jan Arne Petersen --- protocol/input-method.xml | 87 +++ protocol/text.xml | 6 ++-- 2 files changed, 70 insertions(+), 23 deletions(-) diff --git a/protocol/input-method.xml b/protocol/input-method.xm

[PATCH 14/18] doc: add some more text protocol documentation

2013-01-16 Thread Jan Arne Petersen
From: Jan Arne Petersen Signed-off-by: Jan Arne Petersen --- protocol/text.xml | 26 +- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/protocol/text.xml b/protocol/text.xml index 2b31b01..1871619 100644 --- a/protocol/text.xml +++ b/protocol/text.xml @@ -

[PATCH 3/3] doc: add some more text protocol documentation

2012-12-06 Thread Jan Arne Petersen
From: Jan Arne Petersen Signed-off-by: Jan Arne Petersen --- protocol/text.xml | 26 +- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/protocol/text.xml b/protocol/text.xml index f366d37..6a658e0 100644 --- a/protocol/text.xml +++ b/protocol/text.xml @@ -

Re: [PATCH] text: Improve text protocol documentation

2012-09-13 Thread Kristian Høgsberg
On Thu, Sep 13, 2012 at 12:55:14AM +0200, Jan Arne Petersen wrote: > From: Jan Arne Petersen > > Add some missing descriptions to the text protocol file. Thanks, that looks better. Kristian > --- > protocol/text.xml | 35 --- > 1 file changed, 32 insertions(+),

[PATCH] text: Improve text protocol documentation

2012-09-12 Thread Jan Arne Petersen
From: Jan Arne Petersen Add some missing descriptions to the text protocol file. --- protocol/text.xml | 35 --- 1 file changed, 32 insertions(+), 3 deletions(-) diff --git a/protocol/text.xml b/protocol/text.xml index eded1c8..857fd83 100644 --- a/protocol/text