9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sascha Retzki" <sretzki@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Anyone to try to convert Acme to full UI (w/graphics)
Date: Wed, 25 Oct 2006 20:04:47 +0200	[thread overview]
Message-ID: <840ca974ce34a6d6bb253b5f997cddf5@mail.gmx.net> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D481ADE@XMAIL.asuch.cas.cz>

I always wanted to do that, because I like the tagline-concept. I think it would be interesting if the tag would accept \n, spawn a newline, get a scroll-bar, and accept maximal three lines, but maybe that's just me.

My idea was to make something along the lines of 'win', like 'guiwin'. It would be in normal textmode till somebody opens /dev/draw, then switch to 'graphical mode', in which it just relays the picture to its own (acmes) /dev/draw - I have no idea how much things I must rewrite in acme for that, tho :-)

It sounds simple, tho - its just acme needs a few calls so that the application it runs can tell acme it is 'graphical', and arrange some things so that it can read a picture and display it. Acme tells the window its that x this pixels huge, and there we go.



  parent reply	other threads:[~2006-10-25 18:04 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
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 [this message]
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=840ca974ce34a6d6bb253b5f997cddf5@mail.gmx.net \
    --to=sretzki@gmx.de \
    --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).