From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 9622 invoked from network); 28 Jan 2022 02:03:30 -0000 Received: from tb-ob0.topicbox.com (64.147.108.117) by inbox.vuxu.org with ESMTPUTF8; 28 Jan 2022 02:03:30 -0000 Received: from tb-mx0.topicbox.com (tb-mx0.nyi.icgroup.com [10.90.30.73]) by tb-ob0.topicbox.com (Postfix) with ESMTP id C0F9E2FB76 for ; Thu, 27 Jan 2022 21:03:28 -0500 (EST) (envelope-from bounce.mMb4eb2005f779e611cdef4de4.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx0.topicbox.com (Postfix, from userid 1132) id BD7A513BEC62; Thu, 27 Jan 2022 21:03:28 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=9fans.net; h=to :message-id:date:mime-version:content-type :content-transfer-encoding:from:list-help:list-id:list-post :list-subscribe:reply-to:subject:list-unsubscribe; s=dkim-1; bh= y9xAI5fp4FWSSBJIlN3fqDd3MZXts6LuzS2/n+ZL1SE=; b=bAnpw3ja5HOiN+xo FVoYtTwntyKQGPg6XLbUIYasEf8kZH7KktegJngmMCQWg6SwbHs/jAKhQtG1+qPP H+r+2VI8rGEQQL/MVBnHt42GOc1Zea+irqkamLXxX77yRF9+zirBDBRkYI8jVcKC aRA0JVnwPzjqnozbX5XqEvedv2o= To: 9fans <9fans@9fans.net> Message-Id: <16433354030.97ACA3.134633@composer.9fans.topicbox.com> Date: Thu, 27 Jan 2022 21:03:23 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=16433354031.2D5aB6FA.134633 Content-Transfer-Encoding: 7bit Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: 792b7558-7fde-11ec-b484-7999242d11b0 Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UMjUxOGY5ZTRmYzEwZWQwMy1NYjRlYjIwMDVmNzc5ZTYxMWNkZWY0?= =?UTF-8?B?ZGU0Pg==?= From: "ibrahim via 9fans" <9fans@9fans.net> List-Help: List-Id: "9fans" <9fans.9fans.net> List-Post: List-Software: Topicbox v0 List-Subscribe: Precedence: list Reply-To: 9fans <9fans@9fans.net> Subject: [9fans] suggestion : new service targets for plan9 List-Unsubscribe: , Topicbox-Delivery-ID: 2:9fans:437d30aa-c441-11e9-8a57-d036212d11b0:522be890-2105-11eb-b15e-8d699134e1fa:Mb4eb2005f779e611cdef4de4:1:IUKIBu7vwwe75kKzIxEp8-NCFw9iucBb2U18Sf3zCDU --16433354031.2D5aB6FA.134633 Date: Thu, 27 Jan 2022 21:03:23 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I developed a kiosk version of plan9 (based on 9front and legacy9) and am a= bout to develop a single user desktop system. Those can coexist with the ex= isting plan9 system. I named the new service targets kiosk and desktop. Both work without rio. Currently I used initdraw, initmouse, initkeyboard, loadimage, flushimage f= rom devdraw to avoid breaking of compatibility with the existing plan9 syst= ems while the whole rendering of the windows is framebuffer based. Instead = of the usual plan9 fonts I used regular truetypefonts.=20 So my suggestions would be : 1) Define new service targets kiosk and desktop (Currently I do this in ini= t or /user/.../lib/profile. This makes it possible for a user to start an a= lternative window manager or even a single applicaton (kiosk service) with = a modern look and feel. 2) Define a layer between vga and devdraw perhaps vgafb which improves the = performance for frame buffer rendered window managers.=20 3) Define events for mouse, keyboard, touchpad, windows which is based on n= otes managed by light threads inside the client app.=20 Those three steps would protect the existing plan9 from changes and make it= possible to only use the kernel, libraries, tools from alternative user in= terfaces. Plan9 is one of the smallest operating systems accompanied with a= compiler and an abstraction which would attract much more developers and u= sers if it had a modern user interface. We don't have to throw away anythin= g and rio would even be able to run inside a window of a modern desktop.=20 Plan9 has everything necessary to make it an attractive system not only for= a handful of developers. The compilers, the portability, 9p, unicode, dire= ct support for video hardware and its small size are fascinating.=20 The only reason why it isn't recognized by more people is its GUI. I don't = get the reason why we wouldn't extent it so we can use other GUI's while ke= eping the existing in respect of the developers who created this system.=20 I will integrate this changes but I would prefer staying fully compatible t= o the existing projects legacy9 and 9front even more I would prefer not for= king any of them but sharing my parts as contributions. What I need and what those changes need is a separation level between devdr= aw and the graphics hardware and a new event mechanism which can be based o= n notes or equals. I'm not a native English speaker so excuse the many mistakes. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T2518f9e4fc10ed03-Mb4eb2= 005f779e611cdef4de4 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription --16433354031.2D5aB6FA.134633 Date: Thu, 27 Jan 2022 21:03:23 -0500 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I developed a kiosk version of plan9 (based on= 9front and legacy9) and am about to develop a single user desktop system. = Those can coexist with the existing plan9 system.

I named the new service targets kiosk and desktop. Both work withou= t rio.

Currently I used initdraw, initmous= e, initkeyboard, loadimage, flushimage from devdraw to avoid breaking of co= mpatibility with the existing plan9 systems while the whole rendering of th= e windows is framebuffer based. Instead of the usual plan9 fonts I used reg= ular truetypefonts.

So my suggestions wou= ld be :

1) Define new service targets kios= k and desktop (Currently I do this in init or /user/.../lib/profile. This m= akes it possible for a user to start an alternative window manager or even = a single applicaton (kiosk service) with a modern look and feel.

2) Define a layer between vga and devdraw perhaps vg= afb which improves the performance for frame buffer rendered window manager= s.

3) Define events for mouse, keyboard, = touchpad, windows which is based on notes managed by light threads inside t= he client app.

Those three steps would pr= otect the existing plan9 from changes and make it possible to only use the = kernel, libraries, tools from alternative user interfaces. Plan9 is one of = the smallest operating systems accompanied with a compiler and an abstracti= on which would attract much more developers and users if it had a modern us= er interface. We don't have to throw away anything and rio would even b= e able to run inside a window of a modern desktop.

<= /div>
Plan9 has everything necessary to make it an attractive system no= t only for a handful of developers. The compilers, the portability, 9p, uni= code, direct support for video hardware and its small size are fascinating.=

The only reason why it isn't recogni= zed by more people is its GUI. I don't get the reason why we wouldn'= ;t extent it so we can use other GUI's while keeping the existing in re= spect of the developers who created this system.

I will integrate this changes but I would prefer staying fully comp= atible to the existing projects legacy9 and 9front even more I would prefer= not forking any of them but sharing my parts as contributions.
=

What I need and what those changes need is a separati= on level between devdraw and the graphics hardware and a new event mechanis= m which can be based on notes or equals.

I= 'm not a native English speaker so excuse the many mistakes.

= --16433354031.2D5aB6FA.134633--