Frecon: add text layout features provided by pango-view |
|||
Issue descriptionFeature description: https://bugs.chromium.org/p/chromium/issues/detail?id=457307 documents a desire to remove pango-view from builds. To do so, we'd need a replacement that does the following: * src/platform/bmpblk/strings/text_to_png_svg Called from a Makefile in a few places: http://cs/search/?q=(build_font%7Ctext_to_png_svg)+package:%5Echromeos_public$&m=25&type=cs . Uses minimal Pango-markup. * src/platform/initramfs/recovery/make_images Generates static images during ebuild stored in /etc/screens. (How did this not fail during build per Comment 18?) * src/platform/assets/text/display_boot_message Starts Frecon, dynamically generates images from text input, produces animations (!!!)/spinner. * src/platform/factory/sh/cutoff/display_wipe_message.sh Used in Factory process to display Pango-markup-formatted instructions. Uses Frecon. Dynamically generated. The list of features that are mandatory in a strict replacement: * Support for Unicode writing systems through Harfbuzz (shaping), libraqm (wrapping and bidirectional language support), and ICU (Unicode handling). * Some kind of canvas library * A PNG encoder (libpng) * An SVG encoder (and all of its dependencies) * Support for Pango Markup (a HTML-esq-but-not quite markup language). Eng owner: jclinton
,
Oct 20 2017
Hi Alec, you mentioned that you wanted to work on graphics. A lot of code would need to be written to attain this and almost none of that code would be blocked by platform changes. See the linked bug at the top of the bug description for the many folks and business objectives that went into considering how to do this. The requirements listed above touch lots of parts of Chrome OS.
,
Oct 20 2017
Thank you for the pointer! I'll take a look at it as soon as I finish off these last few CrosConfig bugs, only skimmed it for now. And I'll be in need of a new project soon. Ironically I was just about to start writing a text rendering pipeline for my little toy game-engine at home, but it sounds like this is much less hardware-acceleration based.
,
May 29 2018
It was decided that this would be very expensive (in time) to implement. |
|||
►
Sign in to add a comment |
|||
Comment 1 by sjg@google.com
, Jul 5 2017