<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div apple-content-edited="true">As for GUI, I have pretty extensive binding for Gtk+, and I am also done some work with gobject-introspection with plans to provide complete binding of everything glib. My plan is to publish it (an older version, for Gtk1, already circulated here). Gtk+ works on almost everything.
</div><div apple-content-edited="true"><br></div><div apple-content-edited="true">As for TEXT system… Old TEXT system base type was semiopaque REF ARRAY OF CHAR. Compiler was hooking & to Text.Cat which was "allocate enough space, copy both arguments, keep everything ASCIIZ". New type makes & as efficient as possible, but does not disallow us to reimplement RtHooks' Cat and MultiCat to behave just like 3.6/pm3 Text.Cat. </div><div apple-content-edited="true"><br></div><div apple-content-edited="true">I think cm3's reasoning was pretty natural once they decided (because of task at hand, JVM) to create WIDECHAR as standard type. Next was W"" literal, and one thing was following another. When this proved itself as efficient for their needs, it was cemented. </div><div apple-content-edited="true"><br></div><div apple-content-edited="true">I would like to know if anybody would object to reimplementation of TextCat module? I can make it, no problem, as people are not going to lynch me :).</div><div apple-content-edited="true"><br></div><div apple-content-edited="true">Dirk, are you covering Unicode Collate with your Unicode implementation? Except for Unicode tables (and your earlier implementation of this is very useful) and UTF handling/operations (I have this, very complete), Unicode Collate remain biggest remaining obstacle for full incorporation of Unicode/UTF8 into cm3.</div><div apple-content-edited="true"><br></div><div apple-content-edited="true">dd</div><div apple-content-edited="true"><br></div><div><div>On Apr 25, 2013, at 10:12 PM, Dirk Muysers wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Candara; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I would myself like M3 to step back to the good old<br>SRC-PM3 text system (but UTF-8 encoded)<br>preferably to the actual dual CHAR-WCHAR text<br>machinery).</span></blockquote></div><br></body></html>