9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] Anyone to try to convert Acme to full UI (w/graphics)
Date: Wed, 25 Oct 2006 06:29:25 +0200	[thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17D740262@XMAIL.asuch.cas.cz> (raw)
In-Reply-To: <op.thxmg4y0hipq0d@santucco.avp.ru>

thanks for your explanation of your point. however, don't you feel that a single big command window with probably some king of addressing the commands where to go would be more elegant that the taglines? maybe one could open her/his guidefile in the cmd-window using them from there, not via snarf-paste into the proper tagline... maybe i'm a bit biased by using long pipelines of commands that sometime don't fit within the tagline, scrolling there is somewhat problematic. also, having opened 20+files, taglines are almost equivalent to a (non-scrollable) list of open windows.
Not to make you confused: I like acme very much, just trying to share some ideas that may finally render as idiotic/unnecessarry/inconsistent/whatever...

thanks, regards,
++pac.


-----Original Message-----
From: 9fans-bounces+cej=gli.cas.cz@cse.psu.edu [mailto:9fans-bounces+cej=gli.cas.cz@cse.psu.edu] On Behalf Of Alexander Sychev
Sent: Tuesday, October 24, 2006 5:26 PM
To: Fans of the OS Plan 9 from Bell Labs
Subject: Re: [9fans] Anyone to try to convert Acme to full UI (w/graphics)

Hi!

On Tue, 24 Oct 2006 09:55:46 +0400, <cej@gli.cas.cz> wrote:

>
>
>> What exactly do you mean?
>
> getting rid of menus, and of rio, if possible. wopukld also *love* to  
> see a single command window instead of taglines (maybe my fault, but I  
> can only move to thhe beginning or end, but not really scroll through  
> the tagline)
>
> i had on my mind something like Native Oberon (*NOT* bluebottle ) UI...  
> then, acme window could také the whole screen and windows would become  
> panes uinder acme. onme would get an Ui coupled w/text-editor  
> immediatelly.
>
> now, the ui philosophy semms to me to be a bit split... between rio and  
> acme,
> e.g, we must redefine 'cd' to use it under acme ...

For what? If you would like to use a terminal, you should use 'win'.
I'm afraid I will fail your wishes.
I think Acme has a quite consistent UI with lot of wonderful ideas, I'm  
just going to add a graphics support and make some usability improvements  
I suppose are helpful (like a fullscreen mode, rows, maybe multiline tags,  
etc. ).
The backward compatibility with Acme is going to be stored as far as  
possible.

> (my inspiration was: i would like to write a simple program to do  
> measurements within an image, and send the values (in pixels) to an acme  
> 'pane' (window, if you like). would really like to do that with acme,  
> with commands instead of menus)

I think a such kind of things will be implemented.
>
> thanks,
> ++pac.
>



-- 
Best regards,
   santucco


  reply	other threads:[~2006-10-25  4:29 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23  7:30 cej
2006-10-23 10:34 ` Alexander Sychev
2006-10-23 11:56   ` Eric Van Hensbergen
2006-10-23 12:21     ` Alexander Sychev
2006-10-24  5:55     ` cej
2006-10-24  5:55   ` cej
2006-10-24 15:08     ` Ronald G Minnich
2006-10-25  4:31       ` cej
2006-10-25 16:33         ` Joel Salomon
2006-10-25 16:54           ` Russ Cox
2006-10-25 17:21             ` Russ Cox
2006-10-25 17:27               ` erik quanstrom
2006-10-25 17:42               ` Tad Hunt
2006-10-25 18:07                 ` Skip Tavakkolian
2006-10-25 18:19                   ` Paul Lalonde
2006-10-25 18:24                     ` erik quanstrom
2006-10-25 17:55               ` rog
2006-10-25 18:17                 ` Skip Tavakkolian
2006-10-26 18:13             ` David Leimbach
2006-10-26 18:22               ` Sascha Retzki
2006-10-26 18:30                 ` David Leimbach
2006-10-26 18:35                 ` rog
2006-10-30 19:05                   ` Joel Salomon
2006-10-30 19:34                     ` Paul Hebble
2006-10-26 18:24               ` Ronald G Minnich
2006-10-26 21:39                 ` David Leimbach
2006-10-27  7:00             ` cej
2006-10-27  8:37               ` Bruce Ellis
2006-10-27 11:24               ` erik quanstrom
2006-10-27 14:04               ` Russ Cox
2006-10-28 19:27               ` Paweł Lasek
2006-10-24 15:25     ` Alexander Sychev
2006-10-25  4:29       ` cej [this message]
2006-10-25  4:57         ` Lyndon Nerenberg
2006-10-25 16:18         ` Joel Salomon
2006-10-30  6:23           ` cej
2006-10-30  6:33             ` Paul Lalonde
2006-10-30 12:56               ` erik quanstrom
2006-10-30 15:16               ` Russ Cox
2006-10-30 15:25                 ` Gabriel Diaz
2006-10-30 15:30                 ` Paul Lalonde
2006-10-30 16:17             ` Ronald G Minnich
2006-10-31  5:33               ` cej
2006-10-31 18:33                 ` Ronald G Minnich
2006-11-01  6:21                   ` cej
2006-10-23 11:10 ` Tony Lainson
2006-10-23 17:31 ` lucio
2006-10-25 18:04 ` Sascha Retzki
2006-10-25 18:12   ` Sascha Retzki
2006-10-25 18:18   ` Paul Lalonde
2006-10-25 18:23     ` erik quanstrom
2006-10-25 20:15       ` Paul Lalonde
2006-10-25 20:38         ` erik quanstrom
2006-10-25 20:57           ` Tim Wiess
2006-10-25 21:14             ` Paul Lalonde
2006-10-25 18:25     ` Sascha Retzki
2006-10-25 20:16       ` 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=ACCF003CBA3D09458207DB0CB86AD17D740262@XMAIL.asuch.cas.cz \
    --to=cej@gli.cas.cz \
    --cc=9fans@cse.psu.edu \
    /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).