GUI toolkit(s) status

[wxjmfauth at gmail.com]

Le vendredi 21 novembre 2014 05:35:22 UTC+1, Terry Reedy a écrit :
> 
> UTF-16+: I posted on the tracker a prototype of how to make indexing 
> correct by adding an auxiliary index of non-BMP chars.  It makes 
> indexing O(k), where k is the number of astral chars.
> 

It will not work (mathematics).
Start by understanding Unicode (mathematically).

jmf







> UFT-8: Makes indexing O(n).
> 
> Python FSR (3.3+ Unicode): Handling variable byte width adds complexity, 
> but Python has already implemented this pretty efficiently.  Python is 
> open source with a liberal licenc
> 
> To me, an important consideration for choosing is what the OSes require 
> to put characters on the screen.  Are they all the same?
> 
> > Apple is a
> > moving target, they pulled the rug from under Tk's feet twice over the
> > past 10 years. Nobody knows if Tk will continue to exist on the mac if
> > Cocoa is withdrawn some day and replaced by a new and completely
> > different windowing framework.
> 
> > Python has largely replaced Tcl as the
> > first-choice scripting language, and that also does not help to attract
> > people working on Tcl/Tk.
> 
> A possible solution for Tk is to replace the non-C Tcl parts of TK with 
> Python (or the CPython API functions as needed for speed).  I have no 
> idea how horrendous a project creating Py/Tk would be.
> 
> -- 
> Terry Jan Reedy