<div dir="ltr"> <pre style="margin:0px">On Mon Jul 2 09:10:21 UTC 2018 </pre><pre style="margin:0px">Pekka Paalanen <ppaalanen at <a href="http://gmail.com">gmail.com</a>> wrote: </pre><pre style="margin:0px">> On Fri, 29 Jun 2018 10:05:58 -0500</pre> <pre style="margin:0px">> Matt Hoosier <matt.hoosier at <a href="http://gmail.com">gmail.com</a>> wrote:</pre> <pre style="margin:0px">> </pre> <pre style="margin:0px">> > Hi all,</pre> <pre style="margin:0px">> > </pre> <pre style="margin:0px">> > Pekka's recent comments about wanting to enable set-top boxes built with</pre> <pre style="margin:0px">> > libweston to do DRM content got me to wondering:</pre> <pre style="margin:0px">> > </pre> <pre style="margin:0px">> > Who all is using libweston directly (as opposed to running /usr/bin/weston</pre> <pre style="margin:0px">> > possibly with custom shells plugins or similar)? For my own purposes, I</pre> <pre style="margin:0px">> > just use the full compositor because it's pretty lean and mean anyway, and</pre> <pre style="margin:0px">> > I can do what I need by loading plugins.</pre> <pre style="margin:0px">> </pre> <pre style="margin:0px">> Hi Matt,</pre> <pre style="margin:0px">> </pre> <pre style="margin:0px">> I wouldn't be surprised if there weren't many users yet. There is a</pre> <pre style="margin:0px">> huge amount of things I'd like to do before I could comfortably propose</pre> <pre style="margin:0px">> using libweston. I still think it needs to be a goal in mind all the</pre> <pre style="margin:0px">> time though, otherwise we'll never get there. :-)</pre> <pre style="margin:0px">> </pre> <pre style="margin:0px">> IMO the major point of using libweston instead of weston is to be able</pre> <pre style="margin:0px">> to customize the UX any way you want - all the stuff and policy that is</pre> <pre style="margin:0px">> currecntly hardcoded in main.c and the desktop-shell plugin. Making all</pre> <pre style="margin:0px">> configurable is probably not feasible.</pre> <pre style="margin:0px">> </pre> <pre style="margin:0px">> My hope with gaining set-top box etc. use cases is to gather more people</pre> <pre style="margin:0px">> developing for Weston, people who could be dedicated in the long run.</pre> <pre style="margin:0px">> Maybe that could gain us more upstream maintainers.</pre><div> </div><div>Hi,</div><div> </div><div>We are using libweston for a prototype touch interactive entertainment system. We chose this because we wanted to be free to implement any desired behaviour without facing any limitations of the weston shell interface. This is particularly important for us because the actual UX that will be used in the production system is not yet finalised and we'd rather not discover those limitations later down the track.</div><div> </div><div>Using libweston has certainly been a challenge. The lack of documentation has meant that we constantly dive into the weston code to get pointers on how the library should be used. At the least a small example application that handles the basics of mapping a surface, handling touch input, etc. would make it much more approachable. The API doesn't feel finished, (for example, should we be setting is_mapped in weston_surface and weston_view directly), and when we have issues our approach to solving them often boils down to trial and error.</div><div> </div><div>So, count us as a user. We certainly hope to see the library continue to improve.</div><div> </div><div><div class="gmail_signature"><div dir="ltr"><div style="font-family:arial;font-size:small">Best Regards,</div><div style="font-family:arial;font-size:small">Martin.</div><div style="font-family:arial;font-size:small"><a href="http://www.qinetic.com.au" target="_blank">www.qinetic.com.au</a></div><div style="font-family:arial;font-size:small"> </div></div></div></div> </div>