DOCSLIB.ORG

"Wayland" Or Mir Support of Awesome #159 New Issue

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
awesomeWM / awesome Dismiss Join GitHub today GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together. Sign up "Wayland" or Mir support of awesome #159 New issue Closed zaxebo1 opened this issue Mar 6, 2015 · 23 comments zaxebo1 commented Mar 6, 2015 Assignees No one assigned As X will be discarded in a short time by Fedora and Ubuntu etc. GNOME, KDE etc are being directly compatible with Wayland (or Mir ). Even with e19 release the enlightment window manager also directly Labels supports wayland. enhancement Is there any plan /roadmap for awesome for porting to wayland need info wontfix 3 Projects Elv13 commented Mar 6, 2015 • edited Member None yet X wont be discarded for at least 15 years. It will be supported as an alternate protocol in Wayland and Mir Milestone just as it is on OS X. No milestone Awesome doesn't have the heavy handed abstraction layers some other WM may have. It is a lean XCB based WM. The Awesome core probably cannot be extended to support Wayland (let alone Mir). A rewrite 10 participants is AFAIK the only viable option. The lua layer could probably be re-used with some changes. There is currently no plan to do that. Wayland support is going to happen. We built those abstractions, 3 actionless commented Mar 6, 2015 Member talking about rewriting -- can it be just a lua wrapper for an already existing library like https://github.com/Cloudef/wlc or https://github.com/michaelforney/swc ? Elv13 commented Mar 6, 2015 Member MayTODO: [ ] Pixman backend [ ] FB backend [ ] Wayland backend The FB and PixMap backends would be quite useful, one less layer of abstraction. I guess it will stay a "wait and see" approach for some time (and well, patches welcome). 1 zaxebo1 commented Mar 6, 2015 @Elv13 you are right that X will not discarded in that sense. But once wayland becomes mainstream, then the X apps will run on X; and that X will itself run on XWayland , which will then run on Wayland. HENCE, X which was running directly on machine, will then run on top of wayland (using XWayland). So, awesomeWM which prides in fast execution , will become inefficient as "awesomeWM->X->XWayland- >Wayland" when compared" with itself as the situation today is just "awesomeWM->X". This four layer situation ( "awesomeWM->X->XWayland->Wayland" ) may or may not make it a CPU hog, but it will definitely make it a laptop battery draining hog compared to today's situation :-( 1 2 zaxebo1 commented Mar 6, 2015 we can not avoid wayland issue, one way or other - it is going to meet us very soon: Fedora 20 with Wayland preview (post of year 2013) http://www.phoronix.com/scan.php?page=article&item=fedora20_wayland_preview&num=1 roadmap of Wayland and Fedora (post of year 2013) https://lists.fedoraproject.org/pipermail/devel/2013-March/180546.html Fedora 22 even more emphasis on Wayland (post of year 2015) http://www.phoronix.com/scan.php?page=news_item&px=Fedora-Workstation-22-Features Elv13 commented Mar 6, 2015 Member "patches" welcome zaxebo1 commented Mar 7, 2015 okk :-) ff2000 commented Mar 16, 2015 AFAIK XWayland is only used when running a legacy X application in a wayland powered environment. So for asesome nothing will change: it will just run directly on X as it did before, no XWayland involved. zaxebo1 commented Mar 16, 2015 @ff2000 : as of now Awesome window manager uses XCB (X protocol C-language binding), which is client of X11 display server protocol. ==> So yes, awesomeWM is X application ===>So, awesomeWM is a legacy X application in wayland powrred environment ===>So, Xwayland will be involved ff2000 commented Mar 16, 2015 Awesome is a special application - it's a window manager, so it IS the "environment". wayland is used in the compositor, but awesome DOES NOT composite. For compositing you need special applications like compton (and AFAIK they also don't have a wayland roadmap). It is the WM/compositor who decides if it can run wayland or not. And as long as the login manager is not entirely stupid it won't force wayland on legacy X sessions. XWayland is something the compositor has to deal with - run X applications in an embedded X server. In short: I really don't see a reason that you should be worried about performance issues because awesome won't run inside XWayland. blueyed added the enhancement label Mar 17, 2015 aignas commented May 20, 2015 Contributor Just a thought... would it be possible to use the upcoming libweston , which from what I understand could be used as a compositing library? Elv13 commented May 20, 2015 Member Code is code, so I guess with unlimited effort and respect for the laws of physics and economics, everything is possible. It would still take monumental effort and a full rewrite of the C code. kierun commented Nov 26, 2015 +1 for Wayland support. I would hate to go look for another WM. I can offer some time to test and report bugs if that helps. I'd offer time to code as well but having twins, I have no time to even sleep. zaxebo1 commented Nov 26, 2015 I'd offer time to code as well but having twins, I have no time to even sleep. Ha. I can really empathise with you :-D psychon added wontfix need info labels Feb 10, 2016 psychon closed this Jul 4, 2016 actionless commented Aug 19, 2016 Member found in the news one more interesting project related to the topic https://github.com/Immington-Industries/way-cooler 6 Elv13 commented Aug 20, 2016 • edited Member I took a look too. It is based on https://github.com/Cloudef/wlc. If we had to port Awesome, this would be the way to go too. It is a WM core just like Awesome own CAPI. It has most of the base APIs we need to create the CAPI lua interface Awesome awful/wibox/gears depends on. We can steal some of https://github.com/SirCmpwn/sway code to get the wiboxes showing properly. They mostly do that same as us (cairo surfaces + events). The third step is to port Awesome events to libinput (for both X11 and Wayland). After those 3 steps, 80% of Awesome features should work properly in Wayland. It isn't that much work, but I don't have the time or motivation to do it myself for the foreseeable future. WLC is dead, long live wlroot-rs 1 Timidger commented Apr 14, 2017 Hey, owner of Way Cooler here. Just found this thread. Although Way Cooler isn't designed to be an exact successor for Awesome on Wayland, we definitely will try to support the same level of customization that Awesome has using a similar mechanism (i.e: Lua). Most of the work so far has been to make it usable and to use my favourite type of tiling scheme (i3-style), though I have plans to have add a tiling system that works like Lua by defining the placement of windows using user-defined Lua code. Feel free to make suggestions or pull requests on the project. I'm open to adding any of the features you might want to bring over from Awesome. 3 8 ❤ 7 zaxebo1 commented Apr 14, 2017 @Timidger : saw "Way Cooler" which you referred, just now. Thanks for the link. It seems really a great project, esp as it is written in rust and supports wayland. I hope it as good as i3 and awesome. Is there some quick comparison somewhere? Timidger commented Apr 14, 2017 @zaxebo1 I don't have any write up comparing them feature by feature, whether planned or not, but here's a quick run down of how I envisioned the influences come from: The layout is primarily i3-based (e.g, there's a tree consisting of Outputs, Workspaces, Containers, and Views). This was chosen because the awesome layout's can be considered a subset of i3 (it's just a special way to layout the children of a container). This was also chosen because I personally like i3- style tiling more, but I want to incorporate the awesome-style by allowing containers to defer to Lua for tiling Heavy focus on using D-Bus clients to extend the window manager. I know Awesome uses D-Bus, though I'm not sure how it compares to Way Cooler's. In Way Cooler, it's designed so that core functionality, such as the lock screen, notification system, and top bar are all swap-able client programs. For example, we don't currently have a top bar but I envision at least two being made by me: one simpler that uses a static configuration file, and a more dynamic one that will use the Lua thread. I made this design decision because while I like Lua, I found it difficult to use conflicting extensions for Awesome because they didn't play nicely with each other. As well, because many X-utilities no longer work it serves to help replace some of the functionality that is lost. Lua is the main configuration language right now. It has a very tight integration with Way Cooler, being able to do everything a D-Bus client can do (but much faster!) and more (e.g it will eventually be the way clients are given permissions to access D-Bus. You can think of the Lua API exposed by Way Cooler as a super-set of the D-Bus commands we expose).
Load more

Recommended publications
  • X11 and Wayland
    X11 and Wayland A tale of two implementations 1 / 20 Concepts What is hikari and what am I trying to achieve? and Goals window manager / compositor started 1.5 years ago written from scratch stacking / tiling hybrid approach inspired by cwm tiling algorithmX11 inspired and by Waylandherbstluftwm keyboard driven, for fast navigation modal, inspired by vim waste little screen space allowsA tale to arbitrarily of two group implementations windows minimal dependencies energy efficient target FreeBSD X11 and Wayland implementation 2 / 20 Concepts What is hikari and what am I trying to achieve? Concepts What is hikari and what am I trying to achieve? and Goals window manager / compositor started 1.5 years ago written from scratch stacking / tiling hybrid approach inspired by cwm tiling algorithm inspired by herbstluftwm keyboard driven, for fast navigation modal, inspired by vim waste little screen space allows to arbitrarily group windows minimal dependencies energy efficient target FreeBSD X11 and Wayland implementation 3 / 20 X Window System Architecture 4 / 20 X Window System Architecture X Window System Architecture // TinyWM is written by Nick Welch <[email protected]> in 2005 & 2011. // // This software is in the public domain // and is provided AS IS, with NO WARRANTY. #include <X11/Xlib.h> #define MAX(a, b) ((a) > (b) ? (a) : (b)) int main(void) { Display * dpy; XWindowAttributes attr; XButtonEvent start; XEvent ev; if(!(dpy = XOpenDisplay(0x0))) return 1; XGrabKey(dpy, XKeysymToKeycode(dpy, XStringToKeysym("F1")), Mod1Mask, DefaultRootWindow(dpy),
    [Show full text]
  • Distribution Choice and Preferred Method of Coffee Making with A
    Distribution choice and preferred method of coffee making with a quick look at bean-grinding behavior among humans Distribution choice and preferred method of coffee making with a quick look at bean-grinding behavior among humans A quick comment of the results 2 Summary of linux usage 2 Distro usage 2 DE usage, total 4 DE usage by distro 5 Ubuntu 5 Manjaro 6 Fedora 6 Debian 7 Mint 7 Elementary 8 Pop! OS 8 Open SUSE 9 Zorin 9 Coffee making methods 11 Summary 11 Bean-grinding preferences 12 Bean handling and distro usage 13 Coffee making method by distribution choice 14 Distribution choice by coffee making method 15 Case study: Elementary 16 Conclusion 16 End of the document 17 1/20 Distribution choice and preferred method of coffee making with a quick look at bean-grinding behavior among humans A quick comment of the results We have 182 responses, which clearly is a representative sample of all linux users globally, so the results obtained can be considered accurate, valid, significant and scientific. In the following chapters, we display graphs of the data. The data is provided in tabular form for more science in the end of the document. The raw data and this report can be downloaded at https://rampantpanda.com/coffee-and-distro/ ​ Summary of linux usage Distro usage 2/20 Distribution choice and preferred method of coffee making with a quick look at bean-grinding behavior among humans DE usage, total Excluding Windows, MacOS and all the ones I didn’t recognize. From the data (see the end of the document) we can conclude that Cinnamon users can’t really type and i3 users are really specific.
    [Show full text]
  • Understanding Standing Christopher Storey Louisiana Tech University
    Louisiana Tech University Louisiana Tech Digital Commons Doctoral Dissertations Graduate School Winter 2007 Understanding standing Christopher Storey Louisiana Tech University Follow this and additional works at: https://digitalcommons.latech.edu/dissertations Part of the Biomedical Engineering and Bioengineering Commons Recommended Citation Storey, Christopher, "" (2007). Dissertation. 545. https://digitalcommons.latech.edu/dissertations/545 This Dissertation is brought to you for free and open access by the Graduate School at Louisiana Tech Digital Commons. It has been accepted for inclusion in Doctoral Dissertations by an authorized administrator of Louisiana Tech Digital Commons. For more information, please contact [email protected]. UNDERSTANDING STANDING by Christopher Storey, BS MS A Dissertation Presented in Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy College of Engineering and Science Louisiana Tech University March 2007 Reproduced with permission of the copyright owner. Further reproduction prohibited without permission. UMI Number: 3259725 Copyright 2007 by Storey, Christopher All rights reserved. INFORMATION TO USERS The quality of this reproduction is dependent upon the quality of the copy submitted. Broken or indistinct print, colored or poor quality illustrations and photographs, print bleed-through, substandard margins, and improper alignment can adversely affect reproduction. In the unlikely event that the author did not send a complete manuscript and there are missing pages, these will be noted. Also, if unauthorized copyright material had to be removed, a note will indicate the deletion. ® UMI UMI Microform 3259725 Copyright 2007 by ProQuest Information and Learning Company. All rights reserved. This microform edition is protected against unauthorized copying under Title 17, United States Code. ProQuest Information and Learning Company 300 North Zeeb Road P.O.
    [Show full text]
  • Desktop Environments Jeffery Russell and Tim Zabel
    Desktop Environments Jeffery Russell and Tim Zabel Please sign in! http://bit.ly/ritlug-2020 Keep up with RITlug outside of meetings: ritlug.com/get-involved, rit-lug.slack.com Desktop Environments: when terminals just won't do it What makes a desktop environment (DE)? A desktop environment typically contains two major components: - Window Manager Manages windows, icons, menus, pointers - Widget Toolkit - Used to write applications with a unified look and behavior GNOME 3 - Easy to use - “Most” Popular - Great Companability - Nautilus as default file manager KDE Plasma - Uses Dolphin file manager - Easy to use - Very uniform software stack like GNOME Xfce - Lightweight - Easy to use - Thunar file manager Cinnamon - Fork of GNOME 3 - Nemo File Manager - Crist look - Tons of desklets - Very stable MATE - Extension of GNOME 2 - Caja File Manager Unity - Not technically its own DE but a shell extension for GNOME - This is known for giving Ubuntu its iconic sidebar LXQt - Very Lightweight - Easy to use Pantheon - DE designed for Elementary OS - OSX like interface - Looks amazing - Due to simplicity, it is missing some things that are commonplace in other DEs (limited customizations) Deepin - Simple - Very elegant - Developed by a Chinese community Performance? Source: https://itsfoss.com/linux-mint-v s-ubuntu/ Equinox (EDE) - Very lightweight - Last stable release was in 2014 - Reminiscent of windows 9x interface Questions? Window Managers WMs ● Specifically controls placement and appearance of windows ● Doesn’t come with any other integrated tools
    [Show full text]
  • Behavioral Finance Micro 19 CHAPTER 3 Incorporating Investor Behavior Into the Asset Allocation Process 39
    00_POMPIAN_i_xviii 2/7/06 1:58 PM Page iii Behavioral Finance and Wealth Management How to Build Optimal Portfolios That Account for Investor Biases MICHAEL M. POMPIAN John Wiley & Sons, Inc. 00_POMPIAN_i_xviii 2/7/06 1:58 PM Page vi 00_POMPIAN_i_xviii 2/7/06 1:58 PM Page i Behavioral Finance and Wealth Management 00_POMPIAN_i_xviii 2/7/06 1:58 PM Page ii Founded in 1807, John Wiley & Sons is the oldest independent publish- ing company in the United States. With offices in North America, Europe, Australia, and Asia, Wiley is globally committed to developing and marketing print and electronic products and services for our cus- tomers’ professional and personal knowledge and understanding. The Wiley Finance series contains books written specifically for fi- nance and investment professionals as well as sophisticated individual in- vestors and their financial advisors. Book topics range from portfolio management to e-commerce, risk management, financial engineering, valuation, and financial instrument analysis, as well as much more. For a list of available titles, please visit our web site at www.Wiley Finance.com. 00_POMPIAN_i_xviii 2/7/06 1:58 PM Page iii Behavioral Finance and Wealth Management How to Build Optimal Portfolios That Account for Investor Biases MICHAEL M. POMPIAN John Wiley & Sons, Inc. 00_POMPIAN_i_xviii 2/7/06 1:58 PM Page iv Copyright © 2006 by Michael M. Pompian. All rights reserved. Published by John Wiley & Sons, Inc., Hoboken, New Jersey. Published simultaneously in Canada. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopy- ing, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior writ- ten permission of the Publisher, or authorization through payment of the ap- propriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600, or on the web at www.copyright.com.
    [Show full text]
  • Creation Or Evolution
    Abilene Christian University Digital Commons @ ACU Stone-Campbell Books Stone-Campbell Resources 1930 Creation Or Evolution W. W. Otey Follow this and additional works at: https://digitalcommons.acu.edu/crs_books Part of the Biblical Studies Commons, Biology Commons, Christian Denominations and Sects Commons, and the Christianity Commons Recommended Citation Otey, W. W., "Creation Or Evolution" (1930). Stone-Campbell Books. 485. https://digitalcommons.acu.edu/crs_books/485 This Book is brought to you for free and open access by the Stone-Campbell Resources at Digital Commons @ ACU. It has been accepted for inclusion in Stone-Campbell Books by an authorized administrator of Digital Commons @ ACU. CREATION EVOLUTION ByW . W. OTEY ' CREATION OR EVOLUTION I I Creation or Evolution By W. W. Otey 1930 + FIRM FO UNDATION PUBLISHING HOUSE Au stin , Texas . Copyr ight, 1930 Firm Foundation P ubli s hing House Austin, T exas CREATION OF EVOLUTION 5 PREFACE I offer no apology for the publication of the follow­ ing pages. Without a doubt the world is in the midst of the greatest revolution of thought since the es­ tablishment of the kingdom of Christ. Old forms of political government have crumbled. New forms are being tried. Unrest is everywhere in evidence. Dis­ satisfaction with the old and a determination to ex­ periment with the new fills the minds of the multitude. The outstanding characteristic of the present age uni­ versally is a revolt against constituted authority . Man seems determined not to be longer fettered by old standards. While this revolt against constituted au­ thority was against oppresive political governments, pagan religions and humanly formed creeds, it was not greatly to be lamented : But the revolt' has broken over these bounds, and now is arrayed against the au­ thority of the Creator, as revealed through His word written by inspiration.
    [Show full text]
  • System Fundamentals
    System Fundamentals System and Network Administration Revision 2 (2020/21) Pierre-Philipp Braun <[email protected]> Table of contents ▶ What is a server? ▶ UNIX history ▶ Linux distributions ▶ Terminal tips & tricks ▶ Lab: install Slackware Linux Legal notice & guidelines ▶ Originally designed for 3rd year bachelors at Innopolis University ▶ Modified and enhanced since then ▶ Downgraded lab, much easier now ▶ Open and public knowledge – resources in the appendix ▶ This course is practice and industry oriented What’s a server? What’s the difference between a server and a desktop computer? in terms of packaging?… Rackmount - DL380 gen 10 DL380 gen 10 (w/o cover) ==> Enterprise-class ▶ Fault-tolerant storage disks ▶ Fault-tolerant Power Supply Units (PSU) ▶ Out-of-band management (Lights-out) Fault-tolerant storage disks RAID controller there is… RAID-1 DL380 gen 10 top view Fault-tolerant Power Supply Units (PSU) DL380 gen 10 rear slots DL380 gen 10 rear filled Racks More racks Datacenter cooling A self-made PC is fine too, as long as it is dedicated! ▶ low-cost PC with some AMD Ryzen inside same goes for a 500 RUB SoC ▶ TI BBB ▶ RPi4 ▶ Nvidia Jetson Nano Developer Kit ▶ … By the way, who’s selling more desktop computer CPUs, Intel or AMD?… ==> AMD took over end 2020 // hardwaretimes.com Still loosing the laptop market // hardwaretimes.com Lights-Out Management (LOM) ▶ THIS IS NOT ABOUT SSH ▶ Dedicated daughter board –or– ▶ Hardware integrated in the mobo Low-level console Reach it through ▶ Serial console ▶ Java ▶ HTML5 Remote management engines HP ▶ Management Processor (MP) on HP9000 systems ▶ HPE Integrated Lights-Out 2 (iLO2) IBM ▶ Baseboard Management Controller (BMC) ▶ e.g.
    [Show full text]
  • Practical Linux Forensics by Bruce Nikkel! As a Prepublication Title, This Book May Be Incom- Plete and Some Chapters May Not Have Been Proofread
    P R A C T I C A L LINUX FORENSICS A GUIDE FOR DIGITAL INVESTIGATORS BRUCE NIKKEL EARLY ACCESS NO STARCH PRESS EARLY ACCESS PROGRAM: FEEDBACK WELCOME! Welcome to the Early Access edition of the as yet unpublished Practical Linux Forensics by Bruce Nikkel! As a prepublication title, this book may be incom- plete and some chapters may not have been proofread. Our goal is always to make the best books possible, and we look forward to hearing your thoughts. If you have any comments or questions, email us at [email protected]. If you have specific feedback for us, please include the page number, book title, and edition date in your note, and we’ll be sure to review it. We appreciate your help and support! We’ll email you as new chapters become available. In the meantime, enjoy! PR CA T IC A L L INU X FOR E N SI C S BRUCE N IK KE L Early Access edition, 6/18/21 Copyright © 2021 by Bruce Nikkel. ISBN-13: 978-1-7185-0196-6 (print) ISBN-13: 978-1-7185-0197-3 (ebook) Publisher: William Pollock Production Manager: Rachel Monaghan Production Editor: Miles Bond Developmental Editor: Jill Franklin Cover Illustrator: James L. Barry Technical Reviewer: Don Frick Copyeditor: George Hale No Starch Press and the No Starch Press logo are registered trademarks of No Starch Press, Inc. Other product and company names mentioned herein may be the trademarks of their respective owners. Rather than use a trademark symbol with every occurrence of a trade- marked name, we are using the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark.
    [Show full text]
  • Openoffice.Org News Highlights (2004/2005)
    OpenOffice.org News Highlights (2004/2005) October 2005 Open Source Attracts Public Sector Avanquest distributing StarOffice 8 Why multi-party stewardship of the OpenDocument Format matters so much KOffice 1.4.2: Improved OpenDocument Support ISO to review OpenDocument as a standard OASIS submits OpenDocument as standard Microsoft 'must support OpenDocument' 141,624 PCs with OpenOffice.org in China AbiWord gets OpenDocument support from Nokia Microsoft denies PDF support is a reaction to Massachusetts decision RedMonk's Stephen O'Grady about Sun, Google and OpenOffice.org Lenovo bundles StarOffice OpenOffice.org & Google's SOC eWeek: 1xExcellent plus 3xGood for StarOffice 8 CRN: Five Stars for StarOffice 8 September 2005 OpenOffice.org 1.1.5 announced SISSL retired Estonian Native-Lang project announced University of Toronto at Scarborough Standardizes on StarOffice for all Student Computing Resources Commonwealth of Massachusetts moves to open document formats OpenOffice.org distributed at state conference of lawyers "OpenOffice is great alternative to Microsoft" "Plan by 13 Nations Urges Open Technology Standards" Indonesia adopts the Java Desktop System (and StarOffice / OpenOffice.org) for its national open-source desktop OpenOffice.org Conference 2005 in Koper / Capodistria, Slovenia Raising the bar on patents and standards August 2005 OpenOffice.org announces version 2.0 public beta 2 NeoOffice gets $25,000 donation Linux pumps up fitness retailer's network, desktops Kenosha Finds Big Savings in Linux CheckStatus.net Switches To
    [Show full text]
  • An Infinite-Pane, Zooming User Interface Window Manager and Survey of X Window Managers
    An Infinite-Pane, Zooming User Interface Window Manager and Survey of X Window Managers Submitted by Evan Bradley Computer Science To The Honors College Oakland University In partial fulfillment of the requirement to graduate from The Honors College Mentor: Serge Kruk, Professor of Mathematics Department of Mathematics and Statistics Oakland University (02/15/2018) Abstract: This thesis describes a zoomable user interface window manager for the X Window System that aims to provide mechanisms for easily managing a large number of windows. This is motivated in part by greatly increased memory capabilities provided to modern computers as well as the relative stagnation of window managers since the desktop metaphor was first implemented. To address this, a window manager was written that allows the user to zoom over an infinite plane, on which windows may be arbitrarily placed. Taking advantage of the properties emerging from this model, algorithms were written to manage the windows using their associated Euclidean coordinates. Furthermore, a menu system similar to those employed in Oberon and Acme was written to provide the user with the ability to exercise greater control over the window manager. To ensure that it is usable on standard systems for a typical user workflow, it was developed on the X Window System, despite the system’s shortcomings. While this is the first window manager developed for the X Window System with the synthesis of these features, it takes inspiration from other window managers, user interfaces, and HCI research. As such, a brief discussion on other research interfaces is included alongside a more extensive survey on X11 window managers, which provide a substantial source for contemporary window management research.
    [Show full text]
  • Modular Wayland Compositors with Wlroots
    Modular Wayland compositors with wlroots Drew DeVault et al ∗ December 28, 2017 Abstract wlroots is a flexible and modular library upon which Wayland com- positors can be built. It is designed to maximize several factors: code reusability, interoperability between Wayland compositors, and flexibility for use in novel compositor designs. ∗Complete list available at https://github.com/swaywm/wlroots/graphs/contributors 1 Contents 1 Background 3 1.1 Alternatives . 3 2 High-level Design 4 2.1 Backends . 4 2.2 Shells . 4 2.3 Wayland Protocols . 5 2.4 Convenience Utilities . 5 2.5 Rootston . 5 3 Promoting an Interoperable Ecosystem 6 3.1 Security Considerations . 7 4 Project Status 7 2 1 Background Wayland is a protocol used to communicate between user applications and a compositor. The compositor has ownership over input and output resources{ typically displays connected over DVI, HDMI, etc, and keyboards, mice, etc. wlroots (stylized in lowercase, or as "wlr") is a subproject of the Sway com- positor. Originally, Sway was written on top of a similar library called wlc. This library offered abstractions on top of DRM, GBM, GLES, libinput, and so on{ allowing Sway to focus on building the software specific to the compositor. However, with time it became clear that wlc's design is too limiting, and many of Sway's long-term goals were difficult to achieve with it. As a result, we built wlroots. We believe it offers a substantially better basis for development of Wayland compositors than any competing approach. We offer a powerful library that removes most of the heavy lifting from building a Wayland compositor while providing compositor authors as much flexibility in their design as they might gain by doing it all themselves{ I've jokingly referred to wlroots as "about 30,000 lines of code you were going to write anyway." We hope that compositors based on wlroots will be written faster, work better, and will be better citizens of the broader Wayland ecosystem.
    [Show full text]
  • Graphics-Slides.Pdf
    Understanding the Linux Graphics Stack Understanding the Linux Graphics Stack © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 5, 2021. Document updates and sources: https://bootlin.com/doc/training/graphics Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/206 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/206 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/206 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]