On Fri, Oct 31, 2008 at 11:45 AM, Ville M. Vainio <[EMAIL PROTECTED]> wrote:
> - It needs to be fast, fast, fast. End users reject an editor > immediately if it feels clunky. The recent Aha about the file cache may help a lot. It's not clear how much faster other parts of Leo could be. Leo does a lot that traditional editors do not. The shared subtrees representation of Leo's node structure was a giant improvement over the naive duplication of nodes used in MORE and early versions of Leo. In certain contexts, the speedup can be the difference between O(n) and O(log(n)) performance, where n is the number of tree nodes. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
