Colin is Building a CEP App

3 More Discussions You Might Find Interesting

1. Programming

Wuhan Coronavirus Status App for China - Rapid Prototype using MQTT and the IoT OnOff IOS App

With a little bit of work, was able to build a nice "Wuhan Coronavirus Status" app using MQTT and the IoT-OnOff app. More on this technique here: ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages The result turned out nice, I think. I like the look and...

2. Programming

Building app. to send data to website

Hi. I plan to build an application which takes text data from a user. It then sends this to a website, login required. The business case being this site contains many text fields, mostly redundant to user. My application would only prompt user for necessary text. What language, methods...

3. Solaris

Problem building app

trying to run IPERF and i've downloaded and installed and screwed around with my path to get compilers and such available... log in as myself, go to /iperf-2.0.4 switch to su run ./configure seems to go fine, couple of no's but based on previous runs it seems to be ok... do make it goes...

LEARN ABOUT DEBIAN

app::info::handler::prompt

App::Info::Handler::Prompt(3pm) 			User Contributed Perl Documentation			   App::Info::Handler::Prompt(3pm)

NAME

       App::Info::Handler::Prompt - Prompting App::Info event handler

SYNOPSIS

	 use App::Info::Category::FooApp;
	 use App::Info::Handler::Print;

	 my $prompter = App::Info::Handler::Print->new;
	 my $app = App::Info::Category::FooApp->new( on_unknown => $prompter );

	 # Or...
	 my $app = App::Info::Category::FooApp->new( on_confirm => 'prompt' );

DESCRIPTION

       App::Info::Handler::Prompt objects handle App::Info events by printing their messages to "STDOUT" and then accepting a new value from
       "STDIN". The new value is validated by any callback supplied by the App::Info concrete subclass that triggered the event. If the value is
       valid, App::Info::Handler::Prompt assigns the new value to the event request. If it isn't it prints the error message associated with the
       event request, and then prompts for the data again.

       Although designed with unknown and confirm events in mind, App::Info::Handler::Prompt handles info and error events as well. It will simply
       print info event messages to "STDOUT" and print error event messages to "STDERR". For more interesting info and error event handling, see
       App::Info::Handler::Print and App::Info::Handler::Carp.

       Upon loading, App::Info::Handler::Print registers itself with App::Info::Handler, setting up a single string, "prompt", that can be passed
       to an App::Info concrete subclass constructor. This string is a shortcut that tells App::Info how to create an App::Info::Handler::Print
       object for handling events.

INTERFACE

   Constructor
       new

	 my $prompter = App::Info::Handler::Prompt->new;

       Constructs a new App::Info::Handler::Prompt object and returns it. No special arguments are required.

BUGS

       Please send bug reports to <bug-app-info@rt.cpan.org> or file them at <http://rt.cpan.org/NoAuth/Bugs.html?Dist=App-Info>.

AUTHOR

       David Wheeler <david@justatheory.com>

SEE ALSO

       App::Info documents the event handling interface.

       App::Info::Handler::Carp handles events by passing their messages Carp module functions.

       App::Info::Handler::Print handles events by printing their messages to a file handle.

       App::Info::Handler describes how to implement custom App::Info event handlers.

COPYRIGHT AND LICENSE

       Copyright (c) 2002-2008, David Wheeler. Some Rights Reserved.

       This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.10.1							    2011-03-15					   App::Info::Handler::Prompt(3pm)

Complex Event Processing RSS News