| Newsgroups |
gmane.network.tin.user |
| Message-ID |
<[email protected]> |
> [email protected] schrieb:
> [fixed article screen header]
> > I do see some of the potential advantages, but I still think it's
> > a net loss
>
> The main problem with your suggestion is that if you use line
> scrolling, the article would jump up and down if you scroll down or
> up only one line immediately after (or before) the first screen. You
> will lose the line you were reading just before. The other problem
> is that it is a major pain to implement;
Yeah, both these thoughts occured to me, which is why I'd now
advocate just a stronger visual split between the header and
the body.
> In addition, we don't have to redraw the full screen but only the
> article "pane". That's also a UI issue because the screen flickers
> on a full redraw.
Well, a pagedown is still a full page redraw, save for maybe the
header itself, right?
> If there will be any changes to the article screen header it will be
> likely a configurable format variable. But still, it is very likely
> that there will be no distinction between being on the first or any
> other line. It will just be fixed as it is now (but configurable in
> what it will display in how many lines.) When this is done, you may
> configure this screen header to only display one and your
> hyphenation line and use the news_headers_to_(not_)display tinrc
> setting for the first screen.
I guess I'd suggest two, probably fairly easily implemented options:
1. replace row of spaces with row of hyphens
2. make entire header inverse (though of course, that looks a little
ugly if they've set it to trim spaces.
--
[email protected] http://kisrael.com
[Stegosaurus] Two words: spiked tail. "Oh, so you're sneaking up
behind me to eat my delicious body? WHAM! Spikes! For you! In your head!"
--Brunching Shuttlecocks, http://www.brunching.com