Ports Search

POE::Loop::Tk implements the interface documented in POE::Loop. Therefore it has no documentation of its own. Please see POE::Loop for more details. POE::Loop::Tk is one of two versions of the Tk event loop bridge. The other, POE::Loop::TkActiveState accommodates behavior differences in ActiveState's build of Tk. Both versions share common code in POE::Loop::TkCommon. POE::Loop::Tk dynamically selects the appropriate bridge code based on the runtime enviroment.

POW::Component::RSSAggregator is a non-blocking way to watch multiple RSS sources with one process. See also p5-XML-RSS-Feed.

This component extends POE::Component::Schedule by adding an easy way t specify event schedules using a simple cron spec.

POE::API::Peek extends the POE::Kernel interface to provide clean access to Kernel internals in a cross-version compatible manner. Other calculated data is also available.

POE::Component::TSTP -------------------- A POE component to correctly handle Ctrl-Z in your program.

This module profiles POE programs, in the same way the Devel::DProf family of modules do.

POE::Loop::AnyEvent replaces POE's default select() event loop with AnyEvent. This allows POE programs to transparently use most of the event loops AnyEvent can provide. POE::Loop::AnyEvent changes POE's internal implementation without altering its APIs. By design, nearly all software that are already uses POE should continue to work normally without any changes.

Parse::Win32Registry is a module for parsing Windows Registry files, allowing you to read the keys and values of a registry file without going through the Windows API.

POE::Session::MultiDispatch is a drop in replacement for POE::Session that adds callback dispatch functionality to POE sessions. Each event may have multiple handlers associated with it. Fine control over the order of execution is available using helper methods that extend the interface of a POE::Session. POE::Session::MultiDispatch uses POE::Session as a base class. When multiple callbacks are registered for an event, only the last callback survives, all the others are clobbered. POE::Session::MultiDispatch is much nicer to your registered callbacks, it keeps them all in the order they were defined. When an event is triggered, all the callbacks are then executed in that same order (unless you muck around with said order).

POE::Test::Loops contains one function, generate(), which will generate all the loop tests for one or more POE::Loop subclasses.