On Wed, Jun 05, 2019 at 03:12:11PM +0200, Antenore Gatta wrote:
> - [0] https://github.com/vurtun/nuklear
Looks great... till you don't go support of global unicode scripts and
non pre-combined glyphs (pre-combined glyphs are deprecated in unicode)
How do you want to create a reasonable suckless
On Wed, 22 May 2019 15:19:40 -0400
LM wrote:
> By the way, nice job on the charfbuzz port. It would be great if it
> wasn't completely necessary and more systems went with FreeType
> without the circular dependency or started using stb_truetype.h.
> There are a few GUI toolkits (like Nuklear) us
On Wed, May 22, 2019 at 03:19:40PM -0400, LM wrote:
> ...
If you code your own toolkit, you can decide to handle only a few "unicode
scripts". You may add a few limitations on top, and it can become way simpler
to code. This is what I did with the drop-in replacement of harfbuzz: only
basic left-t
Sylvain .Bertrand wrote:
> The only really tough thing with a GUI toolkit (C or anything else) is what
> you
>wrote above: "correct" layout/navigation and rendering of unicode text at near
>global scale.
I've been investigating that. Was reading the Unicode information on
the BIDI algorithm amon
On Mon, May 20, 2019 at 02:55:17PM -0400, LM wrote:
> Another thing I'd want is at least minimal internationalization support
> (enough to be able to handle display and input of characters in the UTF-8
> character set).
Hi,
The only really tough thing with a GUI toolkit (C or anything else) is w
I was reading through the dev mailing list archives and noticed the
posts in March asking which GUIs might be considered better than GTK+
and Qt. I'm very interested in the subject and have been searching
for a decent GUI library for a very long time. My latest list of
possible C based GUI altern
