2009/8/6 Corey O'Connor <coreyocon...@gmail.com>: > I've been working on overhauling VTY for: > * variable column unicode text rendering > * improved performance > * improved terminal support > * More flexible image combinators. > > While there are a number of tasks still remaining before a release, the > infrastructure is all in place. I've also completed an initial version of an > interactive test that can be used by a user to create a report about how > well VTY supports their terminal. I would like anybody willing with about 10 > minutes to spare to run this test and email me the results. > > To run the interactive test it's necessary to: > 0. Pull the latest VTY from http://code.haskell.org/vty/ > 1. Open their terminal of choice to the "test" directory in the vty > sources. > 2. execute "make interactive_terminal_test" > 3. Assuming the source builds OK (It does not use Cabal so building the > test can be unreliable) the test should walk you through the verification > process. > > I'm pretty sure I know what the results are going to be for the various > terminals. ;-) However I would still like people to run the test to work out > any kinks in the test process and establish a nice baseline data set. > > For those that are curious what modules are used for terminal support: > Graphics.Vty.Terminal: This instantiates an instance of an interface to the > terminal. Currently this always instantiates the XTermColor terminal > interface. This should instantiate a terminal interface based on the TERM > environment variable. > Graphics.Vty.Terminal.Generic: Defines the generic interface all terminals > need to implement. > Graphics.Vty.Terminal.XTermColor: This module contains an interface > suitable for xterm only due to the many hard coded control codes. This does > use terminfo for some control codes. This would be a useful reference for > building new terminal support modules. > > The work remaining: > 0. Add more terminal support instances (In particular a generic one that > just relies on termcap) > 1. The interface exported by the package still uses the old implementation. > 2. Resolve performance regressions. > > Thanks in advance, > Corey O'Connor
I was running this test and it seemed pretty straight-forward, but on test #4 (using "image ops"), everything is "striked through" on the screen. When I hit RET and come back to the instruction screen, it's back to normal. However, all the subsequent tests have striked through text as well. The instruction screen is always normal. For this reason, I did not finish the test. I'm using sakura (GTK/VTE) 2.3.4 on Arch Linux. -- Deniz Dogan --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
