#62455 make sure double clicking on a cell in a column that is a cycler doesn't open the message in a new window
#72665, #73888
treat the thread unread and thread total columns like all the other columns.
allow the user to persist their hidden attribuyte.
don't hide / show them when switching between threaded and nonthreaded views.
All that's left is to hide those columns by default.
#72252 fix sort indicator problems
#72250 sorts should default to ascending
sr=bienvenu
#72819 added ascend / descend to the "View | Sort By" menu. sr=bienvenu
#72248 properly update the checkboxes for the "View | Sort By" menu (when it is created). sr=bienvenu
#21094, #72823 some work for "select thread" / "select flagged". sr=bienvenu
change some printf("fix me") into assertions to catch problems.
remove some dead js.
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
ccarlen%netscape.com
sspitzer%netscape.com
bienvenu%netscape.com
gayatrib%netscape.com
jgmyers%netscape.com
mscott%netscape.com
racham%netscape.com
varada%netscape.com
timeless%mac.com
dougt%netscape.com
naving%netscape.com
disttsc%bart.nl
ducarroz%netscape.com
nhotta%netscape.com