I just saw <http://www.mozilla.org/mailnews/performance/speed.html> (Thanks to stephend for the link). > Many things in the MailFE will have to be re-written to work using the > outliner widget. This should be reason for some serious reflection. * Does XUL / XPToolkit encourage messing FE with logic? * Is the Mailnews app properly designed? > * Do we have just one outliner view implemenation class or do we > need one per each type of folder (imap, news, local)? > What would be the differences? > * In 4.x we had > ...what? > The hierarchy was msgdbvw (which handled flat views), thrdbvw for > threaded view, and thrnewvw for threads with new. How did the hierarchy look (i.e. what was a child of what)? > xp toolkit dependencies Please assume that there will be alternate FEs for Mailnews, e.g. (1) one with MFC / the MS tree widget or one with WxWindows and (2) one with a completely different UI, like WAP (wireless Internet standard) or commandline or 3D whatever. I.e. (1) if there have to be XP toolkit dependencies, capsulate them appropriately. (2) Also make sure not to code too much into the View classes, i.e. no "logic" in there. > We'll also need some XP-toolkit help to implement the abiliity to show > a "connected-ness" between messages in the same thread. In 4.x, this > meant those little dotted lines that went from the parent message to > the next message in the thread, to the next message, etc. Cool, this is missing currently (see recent posts in other thread). > * What about the folder pane data source? Do we get rid of it too? > > * could improve performance > WFM. > * allow us to re-order accounts (currently RDF forces > alphabetical order) > WFM, too. (Listed in order of creation.) > * could simplify much of our folder command logic and > selection management > Can't comment. -- This message is protected by ROT0 encryption and the DMCA. Reading is disallowed and will be prosecuted.
