<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><span style="font-family:arial,sans-serif">On 6 April 2016 at 14:12, Daniel Stone </span><span dir="ltr" style="font-family:arial,sans-serif"><<a href="mailto:daniel@fooishbar.org" target="_blank">daniel@fooishbar.org</a>></span><span style="font-family:arial,sans-serif"> wrote:</span><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span>> Just a fly by shed color thought. If we in the future want to add more<br>
> generic debug tools (for example something like xev that is a bit more<br>
> nice than "WAYLAND_DEBUG=1 weston-terminal |& grep -e '[insert complex<br>
> expression here]'") then maybe "wayland-tools" or "wayland-utils"?<br>
> Then again "wayland-info" is nice because it sounds more like a<br>
> "read-only" thing than "-tools" and "-utils".<br>
<br>
</span>+1 for something like that - and the tool you're thinking of (though<br>
incredibly unpolished) is weston-eventdemo. ;)<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Oh right, nice...</div></div><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><joke></div></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline">... let's rename it "wev" </div> <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline">:-)</div></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline"></joke></div></div><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">I'm sure polishing can come later, but I dunno how bundled <span style="font-family:arial,sans-serif">weston-eventdemo is with weston code though, i.e. how hard it would be to make that a standalone tool. Seems for the most part, weston code is used for the parsing of options.</span></div></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I'd prefer they weren't split into one repo per tool. I think, and<br>
this is pretty much the general consensus of upstream and distributors<br>
both, that we went too far with unbundling during Xorg modularisation.<br>
It doesn't give anyone any practical benefit, and just makes life a<br>
bit more difficult.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Cheers,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Olivier</div><br></div></div></div></div>