From: Alin Soare <as1789@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Emacs Dev <emacs-devel@gnu.org>
Subject: Re: Add morph library to emacs
Date: Tue, 6 Mar 2012 03:09:09 +0200 [thread overview]
Message-ID: <CA+Xtq3XJeu3wtRCGBv7g12zrUmbjT6b8FLc8crDkaoAv4w515Q@mail.gmail.com> (raw)
In-Reply-To: <87ty23cy0l.fsf@uwakimon.sk.tsukuba.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 2508 bytes --]
>
>
> > It is evident that the problem of tabs passes beyound the limits of
> > graphical capabilities of emacs.
>
> Not at all. Lack of graphic capability has nothing to do with it;
> graphically adding tab control widgets is no problem (I'm looking at
> them in my XEmacs right now), and displaying different content in the
> same window is Emacs's bread and butter for user multitasking.
>
>
The effort you depose to write tabs for emacs can be compared with the
effort to add to emacs a real graphical interface -- this require maximum 5
000 lines of C code.
And if this is done, we will have a graphical interface of the same power
of that one of smalltalk.
Or otherwise -- a smalltalk with an editor with editing capabilities of
emacs.
The problem that you face is that nobody else understands why you
> think it necessary to add a whole new event processing system to Emacs
> to support your tabs, or why you think tabs are an appropriate
> graphical metaphor for subprocess control (beyond what can already be
> accomplished by attaching the process's stdio channels to a buffer,
> and switching to that buffer via tabs).
>
> > To add morphic objects to the actual structure of emacs it is also
> beyound
> > the limits of the system.
>
> Again, XEmacs did so a decade ago, by the name of "native widgets".
> They are not used much (partly because Emacs doesn't have them, so
> third parties avoid using them, and partly because the developers who
> introduced them only debugged their itchy applications, so they tend
> to still have bugs that need serious scratching when you try to use
> them for other applications), but they are surely proof of concept.
>
>
This is a play. This graphical interface is limited to the capabilities of
emacs's matrix of glyphs.
> > Having such a structure, emacs will have a main working desktop -- main
> > morph, in which we can drop other kind of morphs -- like buffers, tabs,
> > etc. (the frames will not be useful any more).
>
> I think you need to rethink your basic concept of "morph". Buffers
> are *not* GUI objects, and should not be. It is important that a
buffer be displayable in more than one place, or completely detachable
> from the UI. It's arguable that a tab control is a generalization of
>
A buffer could be displayed in 2 morphs , if you want.
Just start reading about the basics of oop and the link with graphical
interfaces.
Seems that you never heard about morphs:
http://en.wikipedia.org/wiki/Morphic_(software)
[-- Attachment #2: Type: text/html, Size: 3659 bytes --]
next prev parent reply other threads:[~2012-03-06 1:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 3:16 Add morph library to emacs Alin Soare
2012-03-05 7:22 ` Stephen J. Turnbull
2012-03-06 1:09 ` Alin Soare [this message]
2012-03-06 1:53 ` Óscar Fuentes
2012-03-06 2:31 ` Stephen J. Turnbull
2012-03-06 2:56 ` Alin Soare
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+Xtq3XJeu3wtRCGBv7g12zrUmbjT6b8FLc8crDkaoAv4w515Q@mail.gmail.com \
--to=as1789@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).