Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

TextGeometry; creation and implementation #151

Closed
8 tasks done
ruby0x1 opened this issue Nov 5, 2014 · 1 comment
Closed
8 tasks done

TextGeometry; creation and implementation #151

ruby0x1 opened this issue Nov 5, 2014 · 1 comment

Comments

@ruby0x1
Copy link
Member

ruby0x1 commented Nov 5, 2014

Current text rendering is efficient in that it creates as few geometry as needed (by texture page break for batching) but it's inefficient in that it creates a new geometry each time the text is re-drawn. This was older placeholder implementation so a text specific Geometry class is needed.

Needs:

  • aware of per-geometry vert count limits
  • avoid if possible creating trees of transforms and use the parent transform
  • dynamic text updates reusing pool of vertices for letters
  • flush excess letters from pool for when you know you wont need the excess
  • ensure geometry transform / origin is not limited by position/align/bounding
  • be future proof for per letter/word etc styling
  • be future proof for rendering easily to a image buffer for effects etc
  • be future proof for SDF shaders and other flexibility
@ruby0x1
Copy link
Member Author

ruby0x1 commented Dec 2, 2014

This is completed in a local branch, once I have tested more thoroughly against larger projects (so far 2 large projects have had no major side effects of all the changes) it will migrate to master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant