The Venerable Jeffrey L. Taylor scribed > SM is the best Webmail package I have found. I am working on a features > that would make me like it more. I have most of these working, mostly. > Instead of keeping these are private patches that I move as I update, I am > thinking of making them plug-ins, public patches, or folding them into the > main body of code. Which route(s) I follow obviously depends on how much > support there is. > > The features: > > 1) Flip order of the threaded view so message 1 is the oldest and the last > message is the newest (ignoring messages within threads). This almost > requires feature 2. > > 2) On opening an mailbox by clicking in the left frame, position to the > oldest, unread message. > > 3) Add a link to delete an entire thread for the selected message(s) and a > link to delete the selected message(s) and all children (replies). > Optionally, these links would be available while reading a message as well > as when looking at contents of a folder.
I'd love to see threads Collapsible like the folder trees is in the left pain are. > > 4) Add link for next new/unread. > > > Discussion: > > 1) This helps alleviate the confusion with next/previous. In thread view, > next would always be a reply to this message or a newer message. > Currently the ordering of message depends on context: in a thread, or not in > a thread. This could replace the existing Thread View, or be another kind > of Thread view. Either an option set somewhere or change the > Thread/Unthread toggle to a menu. > > 2) This could apply to just the Thread view or all views/sort orders. > > 3) I get a lot of e-mail from high volume lists (total: > 300-500msgs/weekday). Some subjects I know I don\'t care to read sight > unseen. Currently, getting rid of them is a hassle, especially when they > span several pages. > > 4) This also helps deal with high volume list in thread view. > > > Implementation: > > Feature 1 is pretty much done. I am doing some QA and eating my own > squirrel food. > > I am currently working with 1.2.11. Should I continue on the 1.2.x series > or move to the unstable/devel series (1.3? or 1.5?). Features 1 and 2 do > not work very well as plug-ins, too much core code has to modified. > Features 3 and 4 modify less code, but do not fit the plug-in API cleanly. > > > What do people think? Support, comments, and suggestions welcome. > > Jeffrey > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most > comprehensive and flexible code editor you can use. > Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. > www.slickedit.com/sourceforge > -- > squirrelmail-users mailing list > List Address: [EMAIL PROTECTED] > List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 > List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
