On Sun, Oct 9, 2011 at 10:12 AM, Ville M. Vainio <[email protected]> wrote: > There is a reasonable way of making leo faster - switching to native > code for hot spots (e.g. through cython or sip). > > If we switched to pygments to do highlighting, we would probably be > disappointed on performance.
Yes. It took a lot of effort for Leo to drive QSyntaxHighlighter incrementally. I'll be studying the IPython code to see if they use any clever tricks. If not, we shall probably either have to stick with the present scheme, or adapt the tricks in the present scheme for use by pygments. What we could do instead is use this: > > http://srchiliteqt.sourceforge.net/source-highlight-qt.html Thanks for the link. In general, I'd like to remain pure-python only, especially for core features like syntax highlighting. But it's certainly worth a look. The first quest is, how adaptable are the highlighters for Leo's concepts? 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.
