Re: com.jogamp.graph.curve.opengl.TextRenderer without shader?
Posted by Sven Gothel on Aug 05, 2014; 3:50pm
URL: https://forum.jogamp.org/com-jogamp-graph-curve-opengl-TextRenderer-without-shader-tp4032687p4032715.html
On 08/05/2014 04:48 PM, aqd [via jogamp] wrote:
> Sorry I was wrong. It failed Chinese fonts no matter the size, or the font.
>
> I have tested:
>
> Adobe Fan Heiti Std B
> Arial Unicode MS
> Droid Sans Fallback (Android's font)
> Microsoft JHengHei
> Microsoft YaHei
> MingLiU
>
>
>
> Droid Sans looks nearly perfect and its holes seem only filled because the
> stroke is far too wide. I set the weight property but nothing changes.Thx for the details.
>
>
>
> I still had to get AWT TextRenderer back for now.
> Somehow it gets very slow
> even with the latest CPU (i7-4700MQ) and GPU (GTX 860m) of mine. Rendering
> hundreds of chinese names is enough to completely freeze my World Wind for
> more than a second.
With our 'AWT text renderer' or w/ our 'Graph text renderer' ?
In graph, we cache the glyph data incl. tesselation and shader attributes.
Hence rendering shall be only limited to the GPU/GLSL performance
after this 'graph data initialization'.
> However, I workaround the problem by pre-rendering text in
> another thread (to AWT backing store, Java2D is the only thing that's slow).
>
> I assume you people won't further improve the AWT renderer, right? So I don't
> need to bother with source compatibility?
If you like to jump in and maintain the AWT text renderer,
you would be welcome of course.
API incompatibility changes will be allowed in each minor version update,
see wiki version-semantics.
Of course, they should be reasonable, however,
removing deprecated stuff and avoiding duplicate code is always reasonable.
There is also one branch 'floating around' using GL3 w/ AWT renderer,
which has not been merged for around 2 years now since the author
didn't maintain it anymore.
<https://github.com/adbrown85/jogl>
+++
As mentioned earlier,
helping in improving graph text rendering is always welcome as well,
if not even favored :)
~Sven
URL: https://forum.jogamp.org/com-jogamp-graph-curve-opengl-TextRenderer-without-shader-tp4032687p4032715.html
On 08/05/2014 04:48 PM, aqd [via jogamp] wrote:
> Sorry I was wrong. It failed Chinese fonts no matter the size, or the font.
>
> I have tested:
>
> Adobe Fan Heiti Std B
> Arial Unicode MS
> Droid Sans Fallback (Android's font)
> Microsoft JHengHei
> Microsoft YaHei
> MingLiU
>
>
>
> Droid Sans looks nearly perfect and its holes seem only filled because the
> stroke is far too wide. I set the weight property but nothing changes.
>
>
>
> I still had to get AWT TextRenderer back for now.
> Somehow it gets very slow
> even with the latest CPU (i7-4700MQ) and GPU (GTX 860m) of mine. Rendering
> hundreds of chinese names is enough to completely freeze my World Wind for
> more than a second.
With our 'AWT text renderer' or w/ our 'Graph text renderer' ?
In graph, we cache the glyph data incl. tesselation and shader attributes.
Hence rendering shall be only limited to the GPU/GLSL performance
after this 'graph data initialization'.
> However, I workaround the problem by pre-rendering text in
> another thread (to AWT backing store, Java2D is the only thing that's slow).
>
> I assume you people won't further improve the AWT renderer, right? So I don't
> need to bother with source compatibility?
If you like to jump in and maintain the AWT text renderer,
you would be welcome of course.
API incompatibility changes will be allowed in each minor version update,
see wiki version-semantics.
Of course, they should be reasonable, however,
removing deprecated stuff and avoiding duplicate code is always reasonable.
There is also one branch 'floating around' using GL3 w/ AWT renderer,
which has not been merged for around 2 years now since the author
didn't maintain it anymore.
<https://github.com/adbrown85/jogl>
+++
As mentioned earlier,
helping in improving graph text rendering is always welcome as well,
if not even favored :)
~Sven
signature.asc (894 bytes) | Free forum by Nabble | Edit this page |