On Tue, Sep 8, 2009 at 8:03 PM, Corey O'Connor<[email protected]> wrote: > > On Tue, Sep 8, 2009 at 10:32 AM, Jean-Philippe > Bernardy<[email protected]> wrote: >> >> On Tue, Sep 8, 2009 at 6:09 PM, Jeff Wheeler<[email protected]> wrote: >>>> Did anybody try vty under windows? >>> >>> It depends on unix, unfortunately. I looked briefly to see if I could >>> replace it with unix-compat, but then I ran into weird ncurses >>> dependencies that I didn't know how to handle (as far as I know, >>> ncurses isn't supposed to work on Windows). > > I bet it was terminfo. > >> Anyhow, last time I checked this >> http://hackage.haskell.org/packages/archive/ansi-terminal/0.5.0/doc/html/System-Console-ANSI.html >> was the most promising way to support windows. >> >> It supports lots of the display capabilities, but not input. > > For the next major release of vty windows support is a reasonable > goal. The current plan is as follows: > - Use ansi-terminal package to add an instance of Terminal and > DisplayTerminal that does not depend on terminfo. > - Use unix-compat > - Use the backend of haskeline for input. Haskeline has already solved > a number of the input issues that are open on vty and has windows > support. However the currently exported modules for haskeline do not > expose the backend modules. Either that would need to be exposed in > the current haskeline package or a new package that is a shared input > backend created. > > None of this should be too difficult. Though I am currently occupied > by other projects.
Great, I've put this info in the related ticket. -- JP. --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
