Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Wizards and W3 integration (was: Re: A road map for Oort Gnus)
Date: 17 Apr 2001 12:57:02 +0200	[thread overview]
Message-ID: <rj4rvnvloh.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <7458-Mon16Apr2001220522+0300-eliz@is.elta.co.il> ("Eli Zaretskii"'s message of "Mon, 16 Apr 2001 22:05:22 +0300")

[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]

"Eli Zaretskii" <eliz@is.elta.co.il> writes:

> Given this description, I don't understand how did you get to
> discussing HTML and W3.  This sounds like a possible extension of
> Customize, plus some glue to go through several options in a
> predefined order.  Am I missing something?

Basically, there are four proposals.

#1. To use HTML with embedded customize widgets and Emacs Lisp as the
basis for the saints.  Basically, an interactive tutorial where you
can set the options directly from the tutorial using embedded
customize widget, with the smartness (if any) programmed with embedded
Emacs Lisp.

This is already implemented in Bill Perrys W3.  Demonstration at

        <URL: http://www.dina.kvl.dk/~abraham/custom/gnus.html >

(one embedded customize widget, no smartness).  The page only make
sense with Emacs W3.

In your words, we would use HTML as the glue between the options.

#2. Some kind of rule based knowledge base, proposed by Lars.  I have
no idea what this would 

#3. Use the saint foundation developed for JDE.  Apparently, this is
an Emacs Lisp only solution using a library build on top of customize
and eieio. 

#4. A pure customize solution.  The customize framework already allows
special purpose groups with existing options listed in a specific
order.  I wrote one for Gnus as a demonstration, which I have attached
to this message.  Load the file, and type 'M-x gnus-virgin <ret>'.

...

My preference is #1, but even though it is already implemented, it is
mostly useless as long as w3 is not integrated in Emacs.  


[-- Attachment #2: Gnus Saint --]
[-- Type: application/emacs-lisp, Size: 4262 bytes --]

  reply	other threads:[~2001-04-17 10:57 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-14 10:31 A road map for Oort Gnus Lars Magne Ingebrigtsen
2001-04-14 10:53 ` Alexandre Oliva
2001-04-14 12:35   ` Per Abrahamsen
2001-04-14 13:12     ` Lars Magne Ingebrigtsen
2001-04-14 14:42       ` Wizards and W3 integration (was: Re: A road map for Oort Gnus) Per Abrahamsen
2001-04-14 15:22         ` Wizards and W3 integration Raymond Scholz
2001-04-14 15:45         ` Re[1]: Wizards and W3 integration (was: A road map for Oort Gnus) Eric M. Ludlam
2001-04-14 16:38         ` Wizards and W3 integration (was: " Eli Zaretskii
2001-04-16 16:49           ` Lars Magne Ingebrigtsen
2001-04-16 19:05             ` Eli Zaretskii
2001-04-17 10:57               ` Per Abrahamsen [this message]
2001-04-17 13:25                 ` Eli Zaretskii
2001-04-17 13:43                   ` Per Abrahamsen
2001-04-17 15:13                     ` Eli Zaretskii
2001-04-17 15:34                       ` Per Abrahamsen
2001-04-17 15:44                         ` Kai Großjohann
2001-04-17 15:45                         ` Laura Conrad
2001-04-17 13:57                   ` William M. Perry
2001-04-17 15:04                     ` Eli Zaretskii
2001-04-16 20:28             ` Kai Großjohann
2001-04-16 20:57             ` Wizards and W3 integration Robin S. Socha
2001-04-17  7:05               ` Eli Zaretskii
2001-04-17  6:12                 ` Norbert Koch
2001-04-17 14:02                 ` Robin S. Socha
2001-04-17 14:14                   ` Michael Livshin
2001-04-17 14:29                     ` Robin S. Socha
2001-04-17 14:35                       ` [noise] " Michael Livshin
2001-04-14 10:57 ` A road map for Oort Gnus Robin S. Socha
2001-04-14 13:15   ` Harry Putnam
2001-04-14 13:19   ` Lars Magne Ingebrigtsen
2001-04-16  0:06     ` Albert Krusbersky
2001-04-14 16:04   ` Per Abrahamsen
2001-04-15 13:20     ` Robin S. Socha
2001-04-15 22:58       ` Kai Großjohann
2001-04-15 23:30         ` Samuel Padgett
2001-04-16  7:50           ` gnus-virgin.el (was: Re: A road map for Oort Gnus) Per Abrahamsen
2001-04-16 13:23             ` gnus-virgin.el Robin S. Socha
2001-04-17 10:52             ` gnus-virgin.el (was: Re: A road map for Oort Gnus) Didier Verna
2001-04-17 11:02               ` Per Abrahamsen
2001-04-17 12:00               ` Kai Großjohann
2001-04-17 12:30                 ` Didier Verna
2001-04-17 17:12                 ` Colin Marquardt
2001-04-17 21:04                 ` Stainless Steel Rat
2001-04-17  8:49   ` A road map for Oort Gnus Christoph Rohland
2001-04-17 15:09     ` Amos Gouaux
2001-04-17 15:31       ` Simon Josefsson
2001-04-18 13:17         ` Christoph Rohland
2001-04-17 15:39       ` Kai Großjohann
2001-04-14 10:58 ` Kai Großjohann
2001-04-14 13:22   ` Lars Magne Ingebrigtsen
2001-04-14 13:42     ` Michael Livshin
2001-04-15 23:01       ` Kai Großjohann
2001-04-17 18:08     ` Didier Verna
2001-04-17 18:05       ` Kai Großjohann
2001-04-17 18:21         ` Didier Verna
2001-04-17 17:47   ` Didier Verna
2001-04-17 18:04     ` Kai Großjohann
2001-04-14 13:58 ` NAGY Andras
2001-04-14 21:51   ` Steinar Bang
2001-04-15 23:02   ` Kai Großjohann
2001-04-16  6:01     ` Amos Gouaux
2001-04-16 18:06       ` Doug Alcorn
2001-04-16 21:10   ` Paul Jarc

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=rj4rvnvloh.fsf@ssv2.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).