[Openmcl-devel] string handling question

[alex crain]

>
>
> Perhaps the heavy processing is done by the default layout manager. It
> could be shortcircuited by a simplified custom  layout manager, or
> perhaps only the type setter.  It must probably apply the same kerning
> algorithm on non-proportional fonts than on any other font. Even in
> Monaco (or was it in Apple's Courier), there was one character that
> was wider: Copyright.
>
>
I'm thinking that this is ultimately the answer and I may
be able to constrain the "active" portions of the buffer with multiple 
layout
managers and/or text containers. For now I'm avoiding the
question by trying to make certain parts smarter and faster. I'm 
editing 50Kb files
without too much pain but it's gets pretty annoying around 100Kb.

I'm going to be spending some time with shark next (props to Hamilton 
for
making that work) and I'll probably be learning all about OpenMCL byte
codes.

:alex