From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0e42da614dd312bf3a7d0f11ed2ab276@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Evolving rio / GUI development
Date: Fri,  4 Mar 2005 16:19:58 +0000
From: rog@vitanuova.com
In-Reply-To: <ee9e417a0503031027162734a8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 1f6abde4-ead0-11e9-9d60-3106f5b1d025

> just an idea.  what i'd really like is to be able to move
> windows between rio and acme, not just make them look
> similar.

i agree.

i thought about this before and looked into the acme data structures a
bit.  at the moment, you've got multiple Columns, but only one Row. i
didn't go any further into it, but i reckoned it might not be too hard
to make acme multi-window capable, and have one Row for each separate
window that it creates.

then maybe you could drag an acme window onto the rio background and
have it create a new rio window; you could move other windows there
too.

if you enabled graphics-style windows in acme (which i haven't looked
into but rob says isn't hard), then you lose a lot of the need for rio.
in fact you could run acme as your window manager and nest rio
inside a window inside it, and further acme windows inside that.
maybe that's going a bit far :-)

one difficulty i have is when editing code in a deeply nested
directory.  i wonder whether in the above scenario, one might allow a
Row window to have a filename tag; any windows in it would display
relative pathnames if under that directory.