9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Bence Fábián" <begnoc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSoC proposal: Alternative window system
Date: Wed, 19 Mar 2014 09:56:08 +0100	[thread overview]
Message-ID: <CAOCRf5VZUFj7RxAo8QeP+TwPxW8zyygEx1D8Wi42iUnPtUxWrQ@mail.gmail.com> (raw)
In-Reply-To: <53295712.1050505@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]

We already have a lot of hacks to make rio tiling.
In my opinion the most interesting/worthwhile
projects mentioned on that wiki is to make things
touchscreen friendly.


2014-03-19 9:36 GMT+01:00 Caleb Malchik <cmalchik@gmail.com>:

> Greetings,
>
> I am a student interested in participating in GSoC under Plan 9. My
> project would involve writing a new window manager as an alternative to rio:
>
> http://www.plan9.bell-labs.com/wiki/plan9/alternative_
> window_system/index.html
>
> I thought I'd say a few words informally as my proposal is not yet ready
> for upload, and it would be good to get some feedback in the remaining days
> before the deadline.
>
> I have experience with C and Linux, but plan9port is the extent of my
> first-hand experience with Plan 9. I've read some of the papers and other
> resources and I am intrigued by the ideas behind Plan 9 and the clean
> implementation of those ideas. I intend to start using Plan 9 natively or
> in a VM soon, and I am confident I could get comfortable with the
> environment before the start of the summer.
>
> For my project, I would build a tiling window manager similar to dwm (what
> I use on Linux). I think a dwm-style interface that could be controlled
> from the keyboard would provide a nice contrast to what we already have
> with rio, and as we see from dwm the implementation of such an interface
> needn't be complex. Development would involve modifying the rio source code
> to implement the basic functions of a tiling/keyboard-controlled window
> manager one by one.
>
> Let me know if this sounds like a good summer-sized project for someone
> who is not yet well acquainted with Plan 9.
>
> Regards,
> Caleb Malchik
>
>

[-- Attachment #2: Type: text/html, Size: 2181 bytes --]

  reply	other threads:[~2014-03-19  8:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19  8:36 Caleb Malchik
2014-03-19  8:56 ` Bence Fábián [this message]
2014-03-19  9:01   ` Shane Morris
2014-03-19 13:46     ` Peter A. Cejchan
2014-03-19 14:13       ` Aram Hăvărneanu
2014-03-19 14:17         ` erik quanstrom
2014-03-19 15:00           ` Bence Fábián
2014-03-19 15:26             ` erik quanstrom
2014-03-19 15:35               ` Anthony Sorace
2014-03-19 15:38                 ` erik quanstrom
2014-03-19 15:49                   ` Anthony Sorace
2014-03-19 16:16                     ` Jeff Sickel
2014-03-19 15:31             ` Anthony Sorace
2014-03-19 15:35               ` erik quanstrom
2014-03-19 16:16           ` Aram Hăvărneanu
2014-03-19 19:02 ` Bakul Shah
2014-03-20  0:05   ` Paul Lalonde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOCRf5VZUFj7RxAo8QeP+TwPxW8zyygEx1D8Wi42iUnPtUxWrQ@mail.gmail.com \
    --to=begnoc@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).