Yes, exactly. There's no need to ship a font with NetBeans just to render the splash screen. I'd recommend keeping the auto-generated version number separate from the logo lockup, i.e. don't try to make the splash screen say "[icon] Apache NetBeans 11.0", instead, just say "[icon] Apache NetBeans" in the format David designed, and display the auto-generated version and/or build number elsewhere in the splash screen. This way the logo lockup always look exactly the same, regardless of version number or platform font rendering.
Is someone rewriting the splash screen display logic? The current splash screen code requires the splash screen to be stored as a bitmap (e.g. png)--SVG is not an option. Even if we eventually support SVG file loading, it might be best to keep the splash screen images as PNG, to avoid the need to load a lot of dependencies (e.g. the Batik library) at such an early stage of the NetBeans boot process, and to load/render the splash screen as fast as possible. Multiple resolutions can be provided to support HiDPI screens. For future SVG image loading support, e.g. for HiDPI icon loading, I already did some work that I can polish up and contribute. -- Eirik From: James Gosling <[email protected]> Sent: Wednesday, May 8, 2019 11:31 PM To: dev <[email protected]> Cc: [email protected] Subject: Re: [NETBEANS-2455] Splash Screens! Another approach is to just flatten the text to vectors, and remove all font references: This version is only 6K, with no fonts. > On May 8, 2019, at 1:06 PM, Jan Tosovsky <[email protected]> wrote: > > > On 2019-05-08 Christian Lenz wrote: >> A colleague said smth about loading fonts via SVG or render them to get the >> path. Smth with Apache Batik? So adding the font with the IDE, load it and >> adding that to SVG. I don’t know it exactly, but the Keywords were fonts in >> SVG as paths created via Apache Batik. > > The font can also be embedded as Base64 stream: > > @font-face { > font-family: "droid-sans"; src: > url(data:font/ttf;base64,AAEAAAARAQAABAAQ ... ); > } > > As it is embebded, there is no need for installing the font on user's > computer or outlining glyph shapes. > > That font should be ideally a subset containing just required glyphs (to > ensure the minimum size, can be done in e.g. FontForge), but this could > violate the font license (IANAL). > > Btw, Batik parses/translates SVG syntax into Java Graphics2D directives. > These can then be rendered on screen or transformed into other outputs (PNG > or PDF). I am not aware it can outline font shapes directly. > > Jan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
