> -----Oorspronkelijk bericht----- > Van: Nico Klasens [mailto:[EMAIL PROTECTED] > Verzonden: vrijdag 12 maart 2004 20:02 > Aan: [EMAIL PROTECTED] > Onderwerp: RE: imagemagick and text > > > > > I don't know exactly, it would be a nice idea, however I > > don't know if > > > a webapp is allowed to set system properties. > > > > I can affirm that it is possible, becouse i just wrote a > > Class that dous it. > > The java.awt.headless is not a readonly property so an application is > allowed to set it with System.setProperty(). It is questionable if you > always want to set the property to true (See remark below). >
I think it would be a good idear to make it a parameter in the config file images.xml. that way users become at least aware of the property and it's implications. Allso it should be noted in the installation documentation. > > > Besides that there may > > > be sideeffects in code that uses awt. Also it is 1.4 only > but that > > > isn't really a problem. > > > > That could be so. I will try to find out why the atw package > > looks for a windowmanager, and what it wants from it. I can't > > think of much offhand, but i agree that it should be clear > > before making such a change. > > The java.awt package needs the windowmanager in the > getGraphics method. Java > 1.4 does not require a windowmanager, but the disadvantage is > that the jvm > can't use the font and other heavy-weight functionality of the > windowmanager. The headless version has to guess some things which can > result in some skewed and jagged images. > > Nico > Dous that mean that java can not find fonts on your system? I thought java was looking in default locations to find fonts. ernst
