Gecko2:NewTextAPI: Difference between revisions

Gecko2:NewTextAPI (view source)

73 bytes added , 18 May 2005

1,295

edits

Revision as of 05:43, 18 May 2005 (view source) Roc (talk \| contribs) No edit summary		Revision as of 05:44, 18 May 2005 (view source) Roc (talk \| contribs) (→‎Performance) Newer edit →
Line 49:		Line 49:
	We'll be more tied to platform text performance.		We'll be more tied to platform text performance.

	We should explore some mechanism for caching the Thebes text layout object in nsTextFrame (which would allow caching of underlying Pango/Uniscribe/ATSUI/font resources). A simple mechanism would be to put the cache in Thebes itself, and use nsTextFrame pointers as abstract keys. When an nsTextFrame was modified, changed style, or destroyed, it would notify Thebes to invalidate any cache entry with that key. We almost certainly don't want to keep a text layout object in every text frame.		We should explore some mechanism for caching the Thebes text layout object in nsTextFrame (which would allow caching of underlying Pango/Uniscribe/ATSUI/font resources). A simple mechanism would be to put the cache in Thebes itself, and use nsTextFrame pointers as abstract keys. When an nsTextFrame was modified, changed style, or destroyed, it would notify Thebes to invalidate any cache entry with that key. We almost certainly don't want to keep a text layout object in every text frame, and the best cache management policy is probably very platform-specific.