Experience from actually trying to write a plugin that embedded a font: You can't in any useful way for the editor. You can programmatically install a font on Java for use by the JVM, but the resulting Font object then has to be passed around by reference. Editor colorings look up fonts by name from xml files in the system filesystem.
You can have a plugin that has a prioritized list of fonts for UI elements and uses the first one that exists, setting the right UIManager key value pairs. But not for the editor. Conceivably, you could have a dynamic filesystem layer that found the font and generated a fake xml file with the right data, but it would either be non editable, or as soon as the user edits it, their edits will be saved in a layer above it and it will never be read in startup again. The best bet for something vaguely like this would be modifying the editor infrastructure to allow for a prioritized list of fonts, ala CSS, and to preserve the alternates on editing. -Tim On Thu, Feb 7, 2019 at 1:31 AM Laszlo Kishalmi <laszlo.kisha...@gmail.com> wrote: > Just asking, > > What do you think about using a standard font like Source Code Pro as > the default font for Editor? > > > Laszlo Kishalmi > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > -- http://timboudreau.com