fix for #95358, folder pane sorting should be case insensitive
fix for #18343, newsgroups in the folder pane should be in newsrc order, not alphabetical order.
plus, some clean up.
r=racham, sr=bienvenu, a=asa
Includes front end re-write to use the outliner widget for the thread pane.
Improvements in scrolling, folder loading, message display, replyto time, sorting, selecting, deleting, the list goes
on and on.
enjoy =).
Revising nsIChannel to allow for overlapped i/o. This consists of three parts:
1. Factoring nsIChannel into a protocol specific part, the nsIChannel, and a socket specific, the nsITransport.
2. Derive the nsIChannel from a nsIRequest.
2. Changes the notification system from necko and the URILoader to pass the nsIRequest interface instead of nsIChannel interface.
This goal stems from wanting to be able to have active AsyncRead and AsyncWrite operations on nsSocketTransport.
This is desired because it would greatly simplify the task of maintaining persistent/reusable socket connections
for FTP, HTTP, and Imap (and potentially other protocols). The problem with the existing nsIChannel interface is
that it does not allow one to selectively suspend just one of the read or write operations while keeping the other active.
r=darin@netscape.comsr=rpotts@netscape.com
you right click on a folder. thanks to sspitzer and bienvenu for good review. Thanks to
david for providing nsMsgFolder::ListDescendents function and all the help.
1. Factoring nsIChannel into a protocol specific part, the nsIChannel, and a socket specific, the nsITransport.
2. Derive the nsIChannel from a nsIRequest.
2. Changes the notification system from necko and the URILoader to pass the nsIRequest interface instead of nsIChannel interface.
This goal stems from wanting to be able to have active AsyncRead and AsyncWrite operations on nsSocketTransport.
This is desired because it would greatly simplify the task of maintaining persistent/reusable socket connections
for FTP, HTTP, and Imap (and potentially other protocols). The problem with the existing nsIChannel interface is
that it does not allow one to selectively suspend just one of the read or write operations while keeping the other active.
The full details of the change on written up in the netlib newsgroup.
r=darin@netscape.comsr=rpotts@netscape.com
make it so you can view "threads with unread". (#52927)
threaded and unread are no longer mutually exclusive.
later, I'll add "unread threaded" which is no the
same thing as "thread with unread".
fix the nsMsgMessageDataSource() to ask the view, thread or msg database for existance of messages, instead of getting an enumerator for all messages, and seeing if it is non empty. more performance work on the way.
move enums from MailNewsTypes.h to MailNewsTypes2.idl, so that I can use the same ones from JS and C++.
sr=bienvenu
- expose event notifications through nsIFolder so that non-folders can trigger notifications on individual folders
- add generic OnItemEvent to nsIFolderListener, and implement in base classes
to it so that you don't lose your place in the thread pane. More work on 26456. r=alecf.
Some performance improvements for loading folders by speeding up building up a uri.
naving%netscape.com
sspitzer%netscape.com
dbaron%fas.harvard.edu
bienvenu%netscape.com
cls%seawood.org
dianesun%netscape.com
gayatrib%netscape.com
mscott%netscape.com
dougt%netscape.com
disttsc%bart.nl
nhotta%netscape.com
putterman%netscape.com
jefft%netscape.com
alecf%netscape.com