Java did it. Swing just asks the OS for a window and draws in it. Works fairly well...except that a Java (Swing) program never quite acts like a Windows, Mac, or Linux program.
And there was a practical use: you got much closer to "write once, run anywhere" whereas the earlier AWT resulted in "write once, test everywhere".
The same could be done in Haskell, but it would be a huge time commitment.
On Thu, Feb 7, 2013 at 12:08 PM, Emanuel Koczwara
<poczta@emanuelkoczwara.pl> wrote:
I'm looking for a library written from scratch in haskell, not high
level bindings.
Nobody's going to reimplement an entire graphics stack in Haskell (or any other language, except as a tour-de-force with no practical use); they're going to use existing bindings to a well-tested existing GUI. Rewriting Wx or Gtk+ in Haskell, seriously? Aside from the effort required at the outset, try keeping up with changes to the thing you're reimplementing. Not maintainable and not viable.
--
brandon s allbery kf8nh sine nomine associates