Hello kcott,

> I do like the feature-rich IO::Prompter module; the menus are perhaps my favourite bit.

well.. I dont know how to be kind about this, but I have a radical different opinion.

Given anyone is free to choose their tool I find very irritating to spot a nice perl module ( IO::Prompter ) with this statement in the docomentation: 

Several features of this module are known to have problems under Windo
+ws. If using that platform, you may have more success (and less distr
+ess) by trying IO::Prompt::Tiny, IO::Prompt::Simple, or IO::Prompt::H
+ooked first.

[download]

Well.. it is kind to inform me, but consider this situation:

Hey my friend! For sure I can lend you my wonderful supercar: it is very safe and fast but if you are not tall exactly 183 cm and 90 Kg the car probably will only go 40Km/h and the car can skid when cornering if your feet are not exactly 10 sized.

:( thanks, better I'll take the bus..

My busses are: 

use Term::Readline; 
$ENV{PERL_RL} = "Perl";

my $term = Term::ReadLine->new('sweet_ol_bus');

$term->Attribs->{completion_function} = sub {
                      my $txt = shift;
                      return  grep { /^$txt/i } sort keys %$my_list_of
+_autocompletion;
                  };

my $in;
while ( defined ( $in = $term->readline( 'my_prompt>' ) ) ) {
        chomp ($in);
        ...
}

[download]

More kind for IO::Prompter should be to have 00_OStest.t stating BAIL_OUT() if $^O eq "MSWin32" and instead I see all tests passing with only, ironically being an interactive module, t/styles.t ....................... skipped: Skipping interactive tests under Windows while all other interactive tests are ok: 

All tests successful.
Files=38, Tests=163, 53 wallclock secs ( 0.09 usr +  0.09 sys =  0.19 
+CPU)
Result: PASS

[download]

So please, consider it carefully before adopting a module if you plan to share your code widely. This is not criticism about you nor your code kcott, absolutely.

You will see me at the next Perl conference selling t-shirts with: Strawberry setups matter and Say NO to OSsism

</rant> :)

L*

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

In reply to Re^3: 'rgb_palette' - Term::ANSIColor Helper -- rant about IO::Prompter by Discipulus
in thread 'rgb_palette' - Term::ANSIColor Helper by kcott

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.