Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Make QtQuick2 compile on QPA | Eskil Abrahamsen Blomfeldt | 2011-04-27 | 1 | -51/+0 |
| | | | | | | | | | | | Moved the logic to set pixel size into the font engines to avoid making the platform plugin interface too complex, and added a function in QPA to make an isolated font engine based on font data. Currently none of the QPA back-ends supports it, but it compiles and spits out a warning if you try to create a QRawFont from data there. This isn't used in QtQuick2 anyway. Reviewed-by: Jiang Jiang | ||||
* | Long live QRawFont! | Eskil Abrahamsen Blomfeldt | 2011-04-15 | 1 | -0/+189 |
The QGlyphs API was initially attempted with a bastardization of QFont which was meant to encapsulate a single, physical font instance (a QFontEngine) where a set of glyph indexes would make sense. This is not how QFont was intended to be used, and it caused several issues. At the same time, the requirement for loading a font from ttf/otf data and be able to access it and use it without polluting the rest of the process with the font arose. To support these two APIs we introduce QRawFont, which is an abstraction on top of a single physical font. Done-with: Jiang Jiang |