unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mario Lang <mlang@delysid.org>
Subject: Re: tree widget
Date: Tue, 13 Apr 2004 12:56:03 +0200	[thread overview]
Message-ID: <87brlwcfjw.fsf@lexx.delysid.org> (raw)
In-Reply-To: <m3d66cn9qq.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "12 Apr 2004 23:53:49 +0200")

storm@cua.dk (Kim F. Storm) writes:

> Masatake YAMATO <jet@gyve.org> writes:
>
>> >     How do you think including tree-widget developed by David PONCE 
>> >     in emacs official distribution?
>> > 
>> > Could you explain to me what that does?
>> 
>> As the name explains, the code provides widget
>> representing a tree hierarchy like:
>> 
>> You can click [+] and [-] to show and hide the sub tree like
>> outline mode.
>
> Doesn't speedbar already have code to do that?  But maybe not in a
> generally useful way...?

That is the point.  Speedbar can not really be reused
outside of the speedbar itself.  tree-widget can be used
in every buffer that has received proper `widget-setup'.
Appart from that, tree-widget has a really nice dynamical children
generation feature which you can use to draw a tree
collapsed, without having all the data for the whole tree ready.
Whenever the user expands a node, the children of that node
are retrieved by calling a function.  This is very very
handy for deeply branched trees.

Apart from that, since tree-widget is completely Widget based,
you can easily create things like a node with a text entry
field, without any major hassle.  I don't think that
speedbar makes this easy in any way.

-- 
CYa,
  Mario | Debian Developer <URL:http://debian.org/>
        | Get my public key via finger mlang@db.debian.org
        | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44

  reply	other threads:[~2004-04-13 10:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 12:07 tree widget Masatake YAMATO
2004-04-08 12:40 ` Dhruva Krishnamurthy
2004-04-08 22:32 ` Mario Lang
2004-04-12  3:39 ` ~/{arch} causes an error in find-file Masatake YAMATO
2004-04-12  4:23   ` Stefan Monnier
2004-04-12  4:56     ` Masatake YAMATO
2004-04-12  5:06       ` Miles Bader
2004-04-12 15:50         ` Stefan Monnier
     [not found] ` <E1BC4jy-0005JP-5d@fencepost.gnu.org>
2004-04-12  3:59   ` tree widget Masatake YAMATO
2004-04-12 21:53     ` Kim F. Storm
2004-04-13 10:56       ` Mario Lang [this message]
2004-04-16 13:02         ` Per Abrahamsen
2004-04-13 17:44     ` Richard Stallman
2004-04-14  3:24       ` Masatake YAMATO
  -- strict thread matches above, loose matches on Subject: below --
2004-04-14  6:41 David PONCE
2004-04-29 16:06 David PONCE
2004-04-29 23:48 ` Kim F. Storm
2004-05-01  9:44   ` Richard Stallman
2004-05-01 11:56     ` David Ponce
2004-05-01 20:29       ` Stefan Monnier
2004-05-01 20:45         ` David Ponce
2004-05-01 20:09     ` Kim F. Storm
2004-05-02 19:52       ` Richard Stallman
2004-04-30  6:42 David PONCE

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=87brlwcfjw.fsf@lexx.delysid.org \
    --to=mlang@delysid.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).