2011/9/21 Eric Y. Kow <eric.kow@...>:
> On Wed, Sep 21, 2011 at 16:36:55 +0200, David Virebayre wrote:
>> I have a probably stupid question, but I'll fire it anyways:
> Hmm, worth a thought.
>> Would it make sense to have future versions of wxHaskell support Text
>> instead of String ?
> Do GUIs typically manipulate large text fields for which this would make
> sense? Is String a source of overhead for any other reason (ie. lots of
> text fields)? Do we care if we just of lots of small ones? Is this a
> matter of convenience for people moving to using a lot more Text in
> modern Haskell?
I have no good answer to those questions. But, if I didn't read too
fast, I think wxwidgets uses UTF-16, which is also what is used in
I've made a little program and used Text to process Textual data which
I want to display in a GUI, so converting to String puts lots of
unwanted T.unpack here and there.
This is annoying enough that I wish I didn't use Text to begin with !
I think it's bad because
- Text is in the Haskell Platform, so it's the blessed way of dealing
with text data
- Takes less memory, faster, etc
- Not using it would slow its adoption
Since wxHaskell or wxWidgets probably has to convert that back to
UTF-16 at some point...
I'm probably thinking way ahead of time with this idea.
> Eric Kow <http://erickow.com>