Path: usenet.cise.ufl.edu!huron.eel.ufl.edu!usenet.eel.ufl.edu!uky.edu!stdio!news.iac.net!netnews.com!news-peer.sprintlink.net!news-peer-west.sprintlink.net!news.sprintlink.net!Sprint!newsfeed.wli.net!nntp.teleport.com!news.teleport.com!not-for-mail
From: Dominique Dumont <[email protected]>
Newsgroups: comp.lang.perl.announce,comp.lang.perl.tk
Subject: ANNOUNCE: Puppet::Log module
Followup-To: comp.lang.perl.tk
Date: 19 Mar 1998 19:31:35 GMT
Organization: Teleport - Portland's Public Access (503) 220-1016
Lines: 59
Sender: [email protected]
Approved: [email protected] (comp.lang.perl.announce)
Message-ID: <[email protected]>
NNTP-Posting-Host: gadget.cscaper.com
X-Disclaimer: The "Approved" header verifies header information for article transmission and does not imply approval of content.
Xref: usenet.cise.ufl.edu comp.lang.perl.announce:19 comp.lang.perl.tk:155


Hello

This message to announce the release of the new Puppet::Log module.
(Beta version).

The suggested module list line will be :
Puppet::Log  bdpO logging facility based on Tk    DDUMONT

I Think it should go in the "development support" section.

Here's an extract of the readme file:

This class defines a log facility based on Tk usable by any class.

This log class will store all text passed to it. When its display
is not opened, the log text may be written on stdout. If a display is
opened, the text display will be updated with the log text.

When the display is created it will feature all logs written since the
creation of this object or since the clear method was called.

Puppet::* classes are designed to provide an access to the
object using a GUI based on Tk.

The basic idea is when you construct a Puppet::* object, you have all the
functionnality of the object without the GUI. Then, when the need arises,
you may (or the class may decide to) open the GUI of the object.
On the other hand, if the need does not arise, you may instanciare a lot of
object wihout cluttering your display.

For instance, if you have an object (say a ProcessGroup)
controlling a set of proceses (Process objects). The user may start the
ProcessGroup through its GUI. Then all processes are run. If one of them
fails, it will raise its own GUI to display the cause of the problem and
let the user decide what to do.

This Log facility is but the tiniest bit of the Puppet objects I have
in store (or in mind).

Future Puppet will feature :
Puppet::Any
Puppet::Twins (for RPC calls and Puppet features)
Puppet::Process
Puppet::ProcessGroup
Puppet::AtomicTest (no nuke there, its just a test that cannot be divided)

Don't ask me for a release or a release date of them. I have prototypes of
most of them and I'll release them when I get the time to put them in a proper
shape and to document them.

Thanks for your comments

Cheers

--
[email protected]

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.