>> There are literally hundreds, if not thousands, of tiny little features that
>> would are relatively simple to implement.
> Actually, in this case, what Mike describes isn't really the problem. It is
> actually pretty hard to implement in dynamic database view like we have.
> It's not too hard in the case where you thread the messages once, but to
> keep the threading correct as messages are added/removed/modified is hard.
> It's on our list of things to do but hasn't made it to the top yet because
> we've always found more compelling things to do with that time.
Um, okay, allow me to extend and revise my comments.
In addition to the literally hundreds, if not thousands, of tiny little
features that are relatively simple to implement, there are those that are
relatively difficult to implement.
;-)
> If you find news reading totally unusable without date-sorted threads, all I
> can do is recommend other news readers at this point.
I want threading allow the mid 1980's 'trn'.
And I still want a graphical representation of threads ala the late 1980's
'nn'.
And I want scoring ala the never finished 'srn'.
And I want virtual newsgroups ala the mythical 'stvrn' (which added scoring
and virtual newsgroups to trn but was rarely seen outside the author's
machines).
Of course, I achieve a lot of that by gatewaying newsgroups of interest to
email and processing the incoming messages with procmail. But that's not
recommended for mere mortals.
mikel
PS: Have you ever noticed that users never go for the "But that's hard"
response? ;-)
PPS: Have you ever wondered just how many alt.binaries.* groups someone has
to be reading to get a 1.5 gigabyte message database? ;-)
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
