Robert Roessler wrote:
In particular, aren't the specific implementations of the GTK/Pango libraries free to use whatever they want to actually stuff the bits into a bitmap? All these functions do is [presumably] reap whatever optimizations are possible in being specialized for specific font representations... right? Or is this where my model needs work? :)
The backends are mostly responsible for enumerating available fonts, reporting the space used be specific glyphs for a specific font size & other attributes and drawing the glyphs at specific positions. That's glossing over a fair bit, but that's about it. I think that functionality is available without writing backend dependent code though.
As an aside, in these contexts, "win32" means TrueType fonts, while "ft2" means FreeType fonts, right? Are either of these expected to be replaced anytime soon?
I don't know exactly where you are looking, but I think the cairo backend is used in the gtk 2.8 stack and that the win32 bits have been rolled into this backend.
Without BUILDING [all of] the GTK components and Pango with my vc7.1 tools, it is not clear how to do detailed profiling. Now, if you can point me at a real Makefile (NOT some ./configure script), or even a VS workspace and collection of dsp files (I prefer the older environment, even though I use the newer compiler) for building all of this, *then* we could talk profiling... :)
Some VS 8 project files were checked into CVS, but I haven't tried them. There's also the nmake .mak files that work with some fiddling. I'm currently using wrapper scripts that fool configure into working with VC++, but they require all the stuff to let configure run.
John _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
