On 6 Apr 2012, at 13:08, Jayaram <[email protected]> wrote: > Also I could not find any links for source code download of Kdrive or > tinyX.Can you kindly point me to a link?Also what I found out is that tinyX > is now no more developed and Kdrive as been integrated with X11. Moreover I > am not sure if they will be supporting ARM architecture.
Why would ARM not work? Most of the Xorg code is platform neutral... Seems to be lots of people using it successfully on ARM already. As ever, google is your friend...! Also, trawl about on the Xorg website, as most of this stuff is integrated into the default Xorg tree now, so you don't need anything "non-standard" at all anymore. > It looks like that FLTK has completely changed the text rendering > implementation in 1.3 from 1.1. The entire text rendering is now done through > xutf8 functions. The key difference in text rendering between fltk-1.1 & fltk-1.3 is support for Unicode, and support for UTF-8 as the preferred text encoding. If you need Unicode text handling, then you need to use a host system that can provide the xutf8 services that support it. If you do not need Unicode support, then fltk-1.1 is probably simpler to get working in a non-compliant setup. Note that the other text related change was in the choice of text renderer - fltk-1.1 defaults to Xlib with XFT as a configure option, whilst fltk-3 defaults to XFT but can be set to use Xlib as a configure option. I'm not sure, but I imagine the older Xlib API may be more compatible with nano-X. > Can I get a documentation anywhere which describes the change? The change to Unicode and UTF-8 is in the release notes. Indeed it is one of the key changes. -- Ian Sent, much to my surprise, from my iPhone _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
