in reply to console editor

I'm interested in hearing more about those Curses::UI bugs you found... I have lately also been looking for a good console UI library, and it was the best I came upon (at least at a higher level than plain old Curses or Term::Cap). Curses::UI is also pretty similar to Tk in its usage, which is a plus for me.

For the console text editor you seek, I was going to suggest vim (but others have already), so instead I'll suggest another good editor that isn't at all like vim, but has many wonderful features: http://www.triptico.com/software/mp.html

Replies are listed 'Best First'.
Re^2: console editor
by misc (Friar) on Sep 04, 2007 at 14:21 UTC
    I didn't know this text editor..
    Thanks for your hint, I'll have to try it, although I'm used to vim.

    About my problems with Curses::UI
    I wasn't able to clear keybindings like documented in Curses::UI::Widget.
    Instead of e.g., as documented, 
    $w->set_binding( \&myfunc, "\cF" );
$w->clear_binding( \&myfunc );

    [download]
    you'll have to call  $w->clear_binding( '__routine_'.\&myfunc ); In order to clear the binding to myfunc.

    I had to look into the sources to figure this out, and I'd consider this a bug.. It should be at least documented in the pod.

    I've mailed the maintainer, but didn't get an answer yet.

    Next problem I had: the texteditor isn't searchable.
    I tried to set some bindings to the according search functions,
    but ended in a mess.
    This time I wasn't able to figure out howto make the texteditor searchable within some hours, I gave up.

    I'd like to say that Curses::UI are great modules as long as you don't want something too complex.

    I personally also hate to do workarounds (which drives me crazy if I've to code some javascript..),
    so I concluded that I'd be better with writing my own ui than using Curses::UI.

    It's not the way I have fun, and I'd also like to say you'll end up in a mess.
    Furthermore I believe such workarounds would become too dependent on the internals of Curses::UI. If anything changes in these modules, the workarounds could easily break.

    Update: My feelings about getting into trouble with Curses::UI have been confirmed.
    I just found this node: Re: text mode screen-oriented application development]
    To quote Withigo: Debugging little quirks in Curses::UI which required custom overrides with Curses code was an especially painful.
[reply]
[d/l]
[select]
Re^2: console editor
by Anonymous Monk on Dec 29, 2007 at 13:37 UTC
    more bugs in Curses, lots not portable
[reply]

In Section Seekers of Perl Wisdom