Qt.git - Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update licenseheader text in source files for qt4.8	Jyri Tahtela	2011-05-13	1	-17/+17
\| \| \| \| \| \| \|	Updated version of LGPL and FDL licenseheaders. Apply release phase licenseheaders for all source files. Reviewed-by: Trust Me
*	Use maximum ascent/descent/leading from fallback fonts in shaping	Jiang Jiang	2011-04-27	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	When shaping a QScriptItem with a multi font engine, currently we only take the ascent/descent/leading from the primary (first) font engine in that multi font engine, however, subsequent engines used during shaping may have larger ascent/descent/leading, disregarding them may cause clipping issues in some cases. It's fixed by checking each font engine used in the shaping process and take the maximum value instead of the first one. On ATSUI we merely make it compile. Task-number: QTBUG-16719 Reviewed-by: Eskil
*	Long live QRawFont!	Eskil Abrahamsen Blomfeldt	2011-04-15	1	-2/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	Update copyright year to 2011.	Rohan McGovern	2011-03-10	1	-1/+1
\| \| \| \| \|	Reviewed-by: Trust Me (cherry picked from commit 774a3536b00c4d6e4c4c10b708e31b4373a338e3)
*	Moving QCoreTextFontEngine with related classes into own file	Jørgen Lind	2010-10-28	1	-0/+167
	The declaration of QCoreTextFontEngine was ifdefed in qfontengine_p.h. So was QMacFontEngine. I have moved them into their own files (qfontengine_coretext_p.h and qfontengine_mac_p.h).