@Mario,
The easiest/quickest way to get the T6963 integrated into the glcd
library would be ignore the text capabilities for now.
The glcd library doesn't have any code to take advantage of this
capability as it assumes the display is a simple bitmapped memory
display and handles all the character rendering internally.
Michael and I have both taken a look at a few displays that
have hardware text support, and while it would be possible
to add support for it,
adding in support for hardware text capability won't be a simple drop in.
This is because the gText class currently assumes fonts are rendered
from local font data and that it has total control over any
pixel in the bitmapped display. This control allows gText to do some things that are likely to not be possible with hardware text.
For example the ability to render characters on any pixel boundary.
The displays that Michael and I have looked at so far tend to force the character glyph to land on certain boundaries.
Also, gText allows configuring multiple text areas each with
each allowed to select its own font and
supports line wrapping and scrolling within those user defined
text areas.
Overall, the issue really isn't so much putting in code to support
hardware text capabilities but how to update the API to support it
as some of the text capabilities will be different when using hardware
text support.
--- bill