--------------------------------------------------------------------------
For application writers
--------------------------------------------------------------------------
Problem:
	Your X server seems to freeze up for a long period when you
	XeText widget is taken into use.

Probable cause 1:
	Check that a proper XeText.fonts resource is in effect. The most
	simple one is (Demo.ad should contain better ones)

		*XeText.fonts:16 -
		*XeTextEd.fonts:16 -
	
Probable cause 2:
	Currently the Text widget is rather agressive in picking up the
	correct size of font, and asks for scaling of the fonts. This will
	be especially noticeable, if you ask many different sized fonts or
	if you are using multibyte fonts (japanese, chinese, korean etc).

	With many multibyte fonts, you also may quickly run out of
	memory, as your X server grows large.
--------------------------------------------------------------------------
For widget writers
--------------------------------------------------------------------------
Caution for subclassers:
	If you intend to subclass some of the Xew widgets, be careful about
	the contraints records. The core -> constraint change is recent and
	the code is not yet fully streamlined. The constraint record starts
	with FrameConstraints fields (frame), but these should really  be
	renamed to the 'basic' (and will be at some point). FrameSupport.c
	belongs logically to XeBasic, but is now used explicitly from XeText
	and XeFrame.

	XeRaster, XeAudio and XeVideo do not yet utilize the composite and
	constraint features.
--------------------------------------------------------------------------

