Boy, is this a classic example of why I dislike "low-bandwidth" communications - I did not manage to convey what I was talking about with either of these! :(

Neil Hodgson wrote:
Robert Roessler:

The first thing is that [I think] Scintilla is using a fairly "heavy
weight" Pango interface for relatively "light weight" needs... IIRC,
Neil mentioned this himself quite a while ago - but I could be wrong
about this.  In any case, the PangoLayout machinery being used is able
to do entire [possibly bi-directional] paragraphs, while Scintilla
only uses it for [at the most] single lines - and usually far less.
Again, I *think* Neil said that using this high-level interface was a
convenience issue [for him].  Comments or corrections?

   Scintilla breaks text drawing up into individual runs with one
style. You could attempt to replace this with a model where you build
a paragraph up in Pango setting styles for regions in that paragraph
before drawing the whole paragraph. Its worth trying (but not by me)
although it may be difficult to provide all of the features. I think
Pango only has a couple of underline/strikethrough attributes which
may not match Scintilla indicators and the control character symbols
may be displayed differently.

   It will also be difficult to match this API with other platforms.On
Windows you may be able to use the Rich Edit Control or on of the HTML
controls. All platforms will provide a low level string drawing
function.

This question was just about how asking Pango to use its *paragraph* layout machinery when Scintilla doesn't really need that level of functionality seems to be [possibly expensive] overkill... I thought when I read over the available Pango calls that there was a lower level set of calls that would satisfy Scintilla's needs. And further, that you had actually brought this up (at least tangentially) almost a year ago (maybe).

Secondly, while one *could* salivate over the *possible* cleanliness of a fully Pango-ized font/rendering model within Scintilla, that doesn't address [possible] performance issues... and that just isn't the way it is in Scintilla today. ;)

Finally, I am having a conceptual/code-sleuthing problem with
Scintilla, Pango, and fonts - all I see is the very high-level
abstract font description stuff... I do not see where this is made
concrete.  Put a different way, Pango has the abilities to directly
understand and use both Win32 [I assume this means TrueType] and
FreeType fonts (and something called OpenType also)... but I do not
see any of these [lower-level or more specific] calls being made.
What's the deal here? :)

   IIRC there are some subdirectories with font system drivers.

This was driven off of the fact that while Pango supports a mess of calls of the form pango_{ft2,win32}_{font,render}..., I do not *see* any of these in Scintilla. And for that matter, it is unclear to me precisely how Pango makes the actual connection between fonts (with all of their real real info on how to draw glyphs, metrics, etc) and the abstract font descriptions - which are all I see being supplied.

Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest

Reply via email to