Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Feature Request: Collecting Lines in Index Mode
Date: Wed, 30 Sep 2009 11:17:55 -0700	[thread overview]
Message-ID: <1254334371-sup-5145@masanjin.net> (raw)
In-Reply-To: <1254247706-sup-2745@peer.zerties.org>

Reformatted excerpts from Christian Dietrich's message of 2009-09-29:
> i am using sup now for just a few weeks and it is just amazing how
> good it works (the lack of folders iritated me a little bit at
> first).

Welcome!

> But now to my Request, i would like to have something like datelines
> in index mode, like:

Cool idea. I'd like to see how this looks.

> I tried to implement the feature by my self, but the mapping beetween
> `curpos' and `@threads' in modes/thread-index-mode.rb made this a
> little bit hard, and i didn't know how to solve this problem without
> breaking sup. Perhaps you can give me a hint, how this problem with
> the direct mapping can be solved.

If you look at #regen_text, @text and @lines are the two variables that
control the display. @text is an array of the GUI elements for each line
of the display. Right now it's just set to one line for each thread. You
want to add one additional element at the appropriate position. for each
date line. GUI elements are represented as arrays of [color, text]
pairs; you can look at #text_for_thread_at for an example.

Then, you want to make sure that @lines is set correctly. @lines is a
map (hash) from line number to thread (so that when the user presses a
key, we know which thread the cursor is resting on).

Hope that helps.
-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2009-09-30 18:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 18:14 Christian Dietrich
2009-09-30 18:17 ` William Morgan [this message]
2009-10-02 20:48   ` Christian Dietrich
2009-10-08  7:05     ` Christian Dietrich
2009-10-08 12:31       ` Christopher Bertels
2009-10-08 12:44         ` Christopher Bertels
2009-10-08 18:28           ` Christian Dietrich
2009-10-08 19:33             ` Christopher Bertels
2009-10-08 19:44               ` Gaute Hope
2009-10-08 20:12                 ` Gaute Hope
2009-10-08 20:26                   ` Benoît PIERRE
2009-10-09  7:19                     ` Christian Dietrich
2009-10-08 20:50                   ` Christian Dietrich
2009-10-09  7:31                     ` Gaute Hope
2009-10-09  7:44                       ` Christian Dietrich
2009-10-09  9:45                         ` Gaute Hope
2009-10-09 10:12                           ` Gaute Hope
2009-10-09 10:39                             ` Christian Dietrich
2009-10-09 11:00                               ` Gaute Hope
2009-10-12  7:11                                 ` Christian Dietrich
2009-10-12 19:23                                   ` Christian Dietrich
2009-10-08 20:04             ` Benoît PIERRE

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=1254334371-sup-5145@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    /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