session 0.01
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1113
Lemonldap::Portal::Session 0.01
Lemonldap::Portal::Session is a Perl extension for Lemonldap websso. more>>
Lemonldap::Portal::Session is a Perl extension for Lemonldap websso.
SYNOPSIS
use Lemonldap::Portal::Session;
my $paramxml = $test->{DefinitionSession} ; # $test is the result of XML parsing
my $obj = Lemonldap::Portal::Session->init ($paramxml,entry =>$entry) ;
Lemonldap::Portal::Session is a parser of XML description of session to keys,values of hash .
It is a piece of lemonldap websso framework . see eg directory for implementation .
<<lessSYNOPSIS
use Lemonldap::Portal::Session;
my $paramxml = $test->{DefinitionSession} ; # $test is the result of XML parsing
my $obj = Lemonldap::Portal::Session->init ($paramxml,entry =>$entry) ;
Lemonldap::Portal::Session is a parser of XML description of session to keys,values of hash .
It is a piece of lemonldap websso framework . see eg directory for implementation .
Download (0.005MB)
Added: 2007-03-21 License: Perl Artistic License Price:
947 downloads
ROX-Session 0.29
ROX-Session is a simple session manager. more>>
ROX-Session is a simple session manager. It loads, runs any programs you asked it to, and then quits when you run it a second time (thus ending your session). ROX-Session does not display any windows until you ask it to quit.
The first time you run it it will offer to make itself your session manager, so that youll get a ROX desktop when you log in (see screenshots below).
ROX-Session will automatically run any programs in your Auto Start directory when you log in. You can open this directory by bringing up the menu over ROX-Sessions icon and choosing Auto Start...
Enhancements:
- A large number of small bugs were fixed.
- New settings for the Gamma, Screensaver, and Keyboard configlets were added.
- The freedesktop.org configuration directories are now used instead of the old CHOICESPATH ones.
<<lessThe first time you run it it will offer to make itself your session manager, so that youll get a ROX desktop when you log in (see screenshots below).
ROX-Session will automatically run any programs in your Auto Start directory when you log in. You can open this directory by bringing up the menu over ROX-Sessions icon and choosing Auto Start...
Enhancements:
- A large number of small bugs were fixed.
- New settings for the Gamma, Screensaver, and Keyboard configlets were added.
- The freedesktop.org configuration directories are now used instead of the old CHOICESPATH ones.
Download (0.12MB)
Added: 2006-09-09 License: GPL (GNU General Public License) Price:
1140 downloads
PHP::Session 0.26
PHP::Session is a Perl module to read / write PHP session files. more>>
PHP::Session is a Perl module to read / write PHP session files.
SYNOPSIS
use PHP::Session;
my $session = PHP::Session->new($id);
# session id
my $id = $session->id;
# get/set session data
my $foo = $session->get(foo);
$session->set(bar => $bar);
# remove session data
$session->unregister(foo);
# remove all session data
$session->unset;
# check if data is registered
$session->is_registered(bar);
# save session data
$session->save;
# destroy session
$session->destroy;
# create session file, if not existent
$session = PHP::Session->new($new_sid, { create => 1 });
PHP::Session provides a way to read / write PHP4 session files, with which you can make your Perl application session shared with PHP4.
If you like Apache::Session interface for session management, there is a glue for Apache::Session of this module, Apache::Session::PHP.
<<lessSYNOPSIS
use PHP::Session;
my $session = PHP::Session->new($id);
# session id
my $id = $session->id;
# get/set session data
my $foo = $session->get(foo);
$session->set(bar => $bar);
# remove session data
$session->unregister(foo);
# remove all session data
$session->unset;
# check if data is registered
$session->is_registered(bar);
# save session data
$session->save;
# destroy session
$session->destroy;
# create session file, if not existent
$session = PHP::Session->new($new_sid, { create => 1 });
PHP::Session provides a way to read / write PHP4 session files, with which you can make your Perl application session shared with PHP4.
If you like Apache::Session interface for session management, there is a glue for Apache::Session of this module, Apache::Session::PHP.
Download (0.015MB)
Added: 2007-04-03 License: Perl Artistic License Price:
934 downloads
App::Session 0.962
App::Session can represents a sequence of multiple events perhaps executed in separate processes. more>>
App::Session can represents a sequence of multiple events perhaps executed in separate processes.
SYNOPSIS
# ... official way to get a Session object ...
use App;
$session = App->context();
$context = $session->session(); # get the session
# any of the following named parameters may be specified
$session = $context->session(
);
# ... alternative way (used internally) ...
use App::Session;
A Session class models the sequence of events associated with a use of the system. These events may occur in different processes.
For instance, in a web environment, when a new user arrives at a web site, he is allocated a new Session, even though he may not even be authenticated. In subsequent requests, his actions are tied together by a Session ID that is transmitted from the browser to the server on each request. During the Session, he may log in, log out, and log in again. Finally, Sessions in the web environment generally time out if not accessed for a certain period of time.
Conceptually, the Session may span processes, so they generally have a way to persist themselves so that they may be reinstantiated wherever they are needed. This would certainly be true in CGI or Cmd Contexts where each CGI request or command execution relies on and contributes to the running state accumulated in the Session. Other execution Contexts (Curses, Gtk) only require trivial implementations of a Session because it stays in memory for the duration of the process. Nonetheless, even these Contexts use a Session object so that the programming model across multiple platforms is the same.
<<lessSYNOPSIS
# ... official way to get a Session object ...
use App;
$session = App->context();
$context = $session->session(); # get the session
# any of the following named parameters may be specified
$session = $context->session(
);
# ... alternative way (used internally) ...
use App::Session;
A Session class models the sequence of events associated with a use of the system. These events may occur in different processes.
For instance, in a web environment, when a new user arrives at a web site, he is allocated a new Session, even though he may not even be authenticated. In subsequent requests, his actions are tied together by a Session ID that is transmitted from the browser to the server on each request. During the Session, he may log in, log out, and log in again. Finally, Sessions in the web environment generally time out if not accessed for a certain period of time.
Conceptually, the Session may span processes, so they generally have a way to persist themselves so that they may be reinstantiated wherever they are needed. This would certainly be true in CGI or Cmd Contexts where each CGI request or command execution relies on and contributes to the running state accumulated in the Session. Other execution Contexts (Curses, Gtk) only require trivial implementations of a Session because it stays in memory for the duration of the process. Nonetheless, even these Contexts use a Session object so that the programming model across multiple platforms is the same.
Download (0.072MB)
Added: 2006-07-20 License: GPL (GNU General Public License) Price:
1191 downloads
AmarokFS-session 0.0.2
marokFS-session is an Amarok script that lets you start your Amarok from KDM with AmarokFS in fullscreenmode. more>>
AmarokFS-session is an Amarok script that lets you start your "Amarok" from KDM with "AmarokFS" in fullscreenmode, then you have a dedicated session only for "Amarok".
<<less Download (MB)
Added: 2007-03-09 License: GPL (GNU General Public License) Price:
959 downloads
Lexi 0.01
Lexi project is a dict client and vocabulary builder. more>>
Lexi project is a dict client and vocabulary builder.
Lexi is a dict client that also serves as a personalized vocabulary builder.
It caches definitions and has a persistent word list.
The interface is structured to be quick and easy and features synonym clicking, drag and drop word queries, and spelling suggestions.
<<lessLexi is a dict client that also serves as a personalized vocabulary builder.
It caches definitions and has a persistent word list.
The interface is structured to be quick and easy and features synonym clicking, drag and drop word queries, and spelling suggestions.
Download (0.025MB)
Added: 2006-10-31 License: GPL (GNU General Public License) Price:
1089 downloads
POE::Session 0.9989
POE::Session is a Perl module for event driven abstract state machine. more>>
POE::Session is a Perl module for event driven abstract state machine.
SYNOPSIS
# Import POE::Session constants.
use POE::Session;
POE::Session->create(
# Inline or coderef states.
inline_states => {
state_one => &coderef_one,
state_two => sub { ... },
},
# Plain and mapped object states.
object_states => [
$object_one => [ state_three, state_four, state_five ],
$object_two => { state_nine => method_nine },
],
# Plain and mapped package states.
package_states => [
$package_one => [ state_six, state_seven, state_eight ],
$package_two => { state_ten => method_ten },
],
# Parameters for the sessions _start state.
args => [ argument_zero, argument_one, ... ],
# Initial options. See the option() method.
options => %options,
# Change the sessions heap representation.
heap => [ ],
);
Other methods:
# Retrieve a sessions unique identifier.
$session_id = $session->ID;
# Retrieve a reference to the sessions heap.
$session_heap = $session->get_heap();
# Set or clear session options.
$session->option( trace => 1, default => 1 );
$session->option( trace );
# Create a postback, then invoke it and pass back additional
# information.
$postback_coderef = $session->postback( $state_name, @state_args );
$postback_coderef->( @additional_args );
# Or do the same thing synchronously
$callback_coderef = $session->callback( $state_name, @state_args );
$retval = $callback_coderef->( @additional_args );
POE::Session combines a runtime context with an event driven state machine. Together they implement a simple cooperatively timesliced thread.
Sessions receive their timeslices as events from POE::Kernel. Each event has two fields, a state name and a session identifier. These fields describe the code to run and the context to run it in, respectively.
Events carry several other fields which will be discussed in the "Predefined Event Fields" section.
States are re-entrant since they are invoked with their runtime contexts. Although its not usually necessary, this re-entrancy allows a single function to be bound to several different sessions, under several different state names.
As sessions run, they post new events through the Kernel. These events may be for themselves or other sessions, in which case they act as a form of inter-session communications. The Kernel can also generate events based on external conditions such as file activity or the passage of time.
POE provides some convenient built-in states with special meanings. They will be covered later on in the "Predefined States" section.
<<lessSYNOPSIS
# Import POE::Session constants.
use POE::Session;
POE::Session->create(
# Inline or coderef states.
inline_states => {
state_one => &coderef_one,
state_two => sub { ... },
},
# Plain and mapped object states.
object_states => [
$object_one => [ state_three, state_four, state_five ],
$object_two => { state_nine => method_nine },
],
# Plain and mapped package states.
package_states => [
$package_one => [ state_six, state_seven, state_eight ],
$package_two => { state_ten => method_ten },
],
# Parameters for the sessions _start state.
args => [ argument_zero, argument_one, ... ],
# Initial options. See the option() method.
options => %options,
# Change the sessions heap representation.
heap => [ ],
);
Other methods:
# Retrieve a sessions unique identifier.
$session_id = $session->ID;
# Retrieve a reference to the sessions heap.
$session_heap = $session->get_heap();
# Set or clear session options.
$session->option( trace => 1, default => 1 );
$session->option( trace );
# Create a postback, then invoke it and pass back additional
# information.
$postback_coderef = $session->postback( $state_name, @state_args );
$postback_coderef->( @additional_args );
# Or do the same thing synchronously
$callback_coderef = $session->callback( $state_name, @state_args );
$retval = $callback_coderef->( @additional_args );
POE::Session combines a runtime context with an event driven state machine. Together they implement a simple cooperatively timesliced thread.
Sessions receive their timeslices as events from POE::Kernel. Each event has two fields, a state name and a session identifier. These fields describe the code to run and the context to run it in, respectively.
Events carry several other fields which will be discussed in the "Predefined Event Fields" section.
States are re-entrant since they are invoked with their runtime contexts. Although its not usually necessary, this re-entrancy allows a single function to be bound to several different sessions, under several different state names.
As sessions run, they post new events through the Kernel. These events may be for themselves or other sessions, in which case they act as a form of inter-session communications. The Kernel can also generate events based on external conditions such as file activity or the passage of time.
POE provides some convenient built-in states with special meanings. They will be covered later on in the "Predefined States" section.
Download (0.35MB)
Added: 2007-04-18 License: Perl Artistic License Price:
919 downloads
ATmission 2.0-01
ATmission is a Fedora-based Linux live CD. more>>
ATmission is a Fedora-based Linux live CD that enables you to experiment with the Linux operating system and other open source software, without the requirement to install Linux on your PC.
The ATmission Live CD contains the KDE desktop, OpenOffice.org, and many other application programs.
This implies that you can:
create user accounts,
install additional RPMs,
start a database on boot,
configure a firewall,
...... anything you can do with a normal Linux system, and
preserve your changes in a file located on hard disk or a USB memory stick
Enhancements:
- With Cowloop 2.16 and more updated packages, based on Fedora Core 4.
<<lessThe ATmission Live CD contains the KDE desktop, OpenOffice.org, and many other application programs.
This implies that you can:
create user accounts,
install additional RPMs,
start a database on boot,
configure a firewall,
...... anything you can do with a normal Linux system, and
preserve your changes in a file located on hard disk or a USB memory stick
Enhancements:
- With Cowloop 2.16 and more updated packages, based on Fedora Core 4.
Download (711MB)
Added: 2005-10-03 License: GPL (GNU General Public License) Price:
1481 downloads
PHP::Session::DB 0.2
PHP::Session::DB is a Perl module to read / write PHP sessions stored in data bases. more>>
PHP::Session::DB is a Perl module to read / write PHP sessions stored in databases.
SYNOPSIS
use PHP::Session::DB;
my $session = PHP::Session::DB->new($id, { DBUSER => $dbuser, DBPASSWD => $dbpasswd, DBNAME => $dbname });
# session id
my $id = $session->id;
# get/set session data
my $foo = $session->get(foo);
$session->set(bar => $bar);
# remove session data
$session->unregister(foo);
# remove all session data
$session->unset;
# check if data is registered
$session->is_registered(bar);
# save session data
$session->save;
# destroy session
$session->destroy;
# create a new session, if not existent
$session = PHP::Session->new($new_sid, { %dbvars, create => 1 });
PHP::Session::DB provides a way to read / write PHP4 sessions stored on databases, with which you can make your Perl application session shared with PHP4.
<<lessSYNOPSIS
use PHP::Session::DB;
my $session = PHP::Session::DB->new($id, { DBUSER => $dbuser, DBPASSWD => $dbpasswd, DBNAME => $dbname });
# session id
my $id = $session->id;
# get/set session data
my $foo = $session->get(foo);
$session->set(bar => $bar);
# remove session data
$session->unregister(foo);
# remove all session data
$session->unset;
# check if data is registered
$session->is_registered(bar);
# save session data
$session->save;
# destroy session
$session->destroy;
# create a new session, if not existent
$session = PHP::Session->new($new_sid, { %dbvars, create => 1 });
PHP::Session::DB provides a way to read / write PHP4 sessions stored on databases, with which you can make your Perl application session shared with PHP4.
Download (0.004MB)
Added: 2007-04-03 License: Perl Artistic License Price:
934 downloads
doinkd 0.01
doinkd project is a daemon that runs on a machine to keep an eye on current users. more>>
doinkd project is a "daemon" that runs on a machine to keep an eye on current users. If users have been idle for too long, or have been logged on for too long, it will warn them and log them out appropriately. The types of checks that doinkd performs are the following:
maxuser: *NEW* If a declared number of sessions, either by group or userid, are active, that user and subsequent users/sessions are warned and their sessions are terminated.
idle: If a user is idle more than their allotted time, as specified by the doinkd configuration file, he/she will be warned. If no action has taken place during the warn time, the user will then be logged out.
session: If a user is logged on for longer than the allotted time, he/she will be warned and logged out in warntime seconds if the user is still logged on then.
multiple: If too many user sessions are active (ie. many users logged on, or some users logged on many times), doinkd will choose X many sessions for each user to keep, waning the others, and logging those out in sleep seconds (such as 120) if there are still too many logged in then. X is either specified as a number of multiples per user, or is proportional to the threshold of sessions before multiple logouts are in effect.
refuse: If a user matches this setting, doinkd will terminate the users session after about a 5 second warning. The basically "refuse"s access for that user (or tty, or group) to the machine, though there may be some time allowed when doinkd is sleeping between checks.
doinkd is configurable without recompilation for its settings, such as the maximum allowed idle times, session limits, thresholds before session limits and multiple login checks begin, and also the important exemption lists. The configuration file is automatically re-read every sleep seconds (specified in the configuration file). If the
configuration file missing or contains errors when doinkd attempts to update its configuration, it will simply report the errors to its log file and continue normal operation, either with its previous settings (in the event of the file not being there or not being readable) or with all valid settings (in the event of errors in the conf file). doinkd must exit, however, if the configuration file is doesnt exist or is not readable when it first starts, and will also exit at the start if there are errors in the configuration file (since they should be fixed then).
Exemptions can be set for any user, group, host the user is logged in from, or tty for any of the checks that doinkd performs, such as allowing idle timeouts to default to 60 minutes for everyone, but exempting the staff group from these timeouts.
doinkd has the ability to handle the console as special, so that X-Windows environments can have appropriate settings. The special handling includes giving an idle time, session limit, and allowed multiple logins specifically for the user on console. All of these logout checks can also be disabled for the windows owned by the user on console. Idle activity is found by checking the keyboard and mouse if the user is in X-Windows. Special checking is also done to see if the person on console is running xlock (or some terminal locking program--the name is configurable at
compilation time) and logging the user off if the xlock program runs longer than the allowed console idle time. The special xlock check prevents users from running xlock and leaving the terminal for a long period of time, but not getting logged off, since other users may press a key or move the mouse to see if the machine is available, and in doing so makes the logged in user no longer idle. See TODO file for a comment on xlock. doinkd also has the ability to work with some implementations of XDM.
The configuration files path may be specified on the command line, so that one executable can be used on multiple machines with different path structures. Also, doinkd can read in separate files (specified in the config file) to get a list of users to apply a timeout/session/refuse/exempt command to.
<<lessmaxuser: *NEW* If a declared number of sessions, either by group or userid, are active, that user and subsequent users/sessions are warned and their sessions are terminated.
idle: If a user is idle more than their allotted time, as specified by the doinkd configuration file, he/she will be warned. If no action has taken place during the warn time, the user will then be logged out.
session: If a user is logged on for longer than the allotted time, he/she will be warned and logged out in warntime seconds if the user is still logged on then.
multiple: If too many user sessions are active (ie. many users logged on, or some users logged on many times), doinkd will choose X many sessions for each user to keep, waning the others, and logging those out in sleep seconds (such as 120) if there are still too many logged in then. X is either specified as a number of multiples per user, or is proportional to the threshold of sessions before multiple logouts are in effect.
refuse: If a user matches this setting, doinkd will terminate the users session after about a 5 second warning. The basically "refuse"s access for that user (or tty, or group) to the machine, though there may be some time allowed when doinkd is sleeping between checks.
doinkd is configurable without recompilation for its settings, such as the maximum allowed idle times, session limits, thresholds before session limits and multiple login checks begin, and also the important exemption lists. The configuration file is automatically re-read every sleep seconds (specified in the configuration file). If the
configuration file missing or contains errors when doinkd attempts to update its configuration, it will simply report the errors to its log file and continue normal operation, either with its previous settings (in the event of the file not being there or not being readable) or with all valid settings (in the event of errors in the conf file). doinkd must exit, however, if the configuration file is doesnt exist or is not readable when it first starts, and will also exit at the start if there are errors in the configuration file (since they should be fixed then).
Exemptions can be set for any user, group, host the user is logged in from, or tty for any of the checks that doinkd performs, such as allowing idle timeouts to default to 60 minutes for everyone, but exempting the staff group from these timeouts.
doinkd has the ability to handle the console as special, so that X-Windows environments can have appropriate settings. The special handling includes giving an idle time, session limit, and allowed multiple logins specifically for the user on console. All of these logout checks can also be disabled for the windows owned by the user on console. Idle activity is found by checking the keyboard and mouse if the user is in X-Windows. Special checking is also done to see if the person on console is running xlock (or some terminal locking program--the name is configurable at
compilation time) and logging the user off if the xlock program runs longer than the allowed console idle time. The special xlock check prevents users from running xlock and leaving the terminal for a long period of time, but not getting logged off, since other users may press a key or move the mouse to see if the machine is available, and in doing so makes the logged in user no longer idle. See TODO file for a comment on xlock. doinkd also has the ability to work with some implementations of XDM.
The configuration files path may be specified on the command line, so that one executable can be used on multiple machines with different path structures. Also, doinkd can read in separate files (specified in the config file) to get a list of users to apply a timeout/session/refuse/exempt command to.
Download (0.056MB)
Added: 2006-05-30 License: LGPL (GNU Lesser General Public License) Price:
1242 downloads
Tivoli 0.01
Tivoli is a Perl extension for Tivoli TME10. more>>
Tivoli is a Perl extension for Tivoli TME10.
SYNOPSIS
Not (yet) Autoloader implemented.
use Tivoli::DateTime;
use Tivoli::Logging;
use Tivoli::Fwk;
use Tivoli::Endpoints;
This Module will handle about everything you may need for Tivoli TME10. If anything has been left out, please contact me at tivoli.rhase@muc-net.de so it can be added.
Tivoli::DateTime
This Package will handle about everything you may need for handling the date / time.
Tivoli::Logging
This Package will handle about everything you may need for Logging.
Tivoli::Fwk
This Package will handle about everything you may need for Framework.
Tivoli::Endpoints
This Package will handle about everything you may need for Endpoints.
<<lessSYNOPSIS
Not (yet) Autoloader implemented.
use Tivoli::DateTime;
use Tivoli::Logging;
use Tivoli::Fwk;
use Tivoli::Endpoints;
This Module will handle about everything you may need for Tivoli TME10. If anything has been left out, please contact me at tivoli.rhase@muc-net.de so it can be added.
Tivoli::DateTime
This Package will handle about everything you may need for handling the date / time.
Tivoli::Logging
This Package will handle about everything you may need for Logging.
Tivoli::Fwk
This Package will handle about everything you may need for Framework.
Tivoli::Endpoints
This Package will handle about everything you may need for Endpoints.
Download (0.014MB)
Added: 2007-05-25 License: Perl Artistic License Price:
885 downloads
VNC Session Manager 0.8
VNC Session Manager provides a disconnected session manager for VNC. more>>
VNC Session Manager provides a disconnected session manager for VNC.
VNC Session Manager adds the necessary glue code between VNCs two execution modes, enabling XDM-based login to disconnected sessions. This gives a Terminal Services-like login for Unix-based VNC servers.
<<lessVNC Session Manager adds the necessary glue code between VNCs two execution modes, enabling XDM-based login to disconnected sessions. This gives a Terminal Services-like login for Unix-based VNC servers.
Download (0.012MB)
Added: 2007-03-06 License: GPL (GNU General Public License) Price:
968 downloads
Race Timing 0.01
Race Timing lets you manage races by describing a race and the rules associated with it. more>>
Race Timing lets you manage races by describing a race and the rules associated with it. You can time the racers and provide realtime standing of the race participants.
You can manage various race events (pilot changes, refuelling, laps, intermediate sprints, etc.) and broadcast various information to the participants. Race Timing is best used with transponders, but manual operation is also provided.
<<lessYou can manage various race events (pilot changes, refuelling, laps, intermediate sprints, etc.) and broadcast various information to the participants. Race Timing is best used with transponders, but manual operation is also provided.
Download (1.1MB)
Added: 2006-07-12 License: GPL (GNU General Public License) Price:
1202 downloads
Qubit 0.01
Qubit (Qmail Ultimate Backend Integration Tool) is a fully Web-based qmail server configuration and administration suite. more>>
Qubit (Qmail Ultimate Backend Integration Tool) is a fully Web-based qmail server configuration and administration suite.
Qubit project is based on the qmailrules qmail server installation style. It has the same features as other similar tools (like vqadmin and qmailadmin), and it also gives you full control to administer your server with all sorts of features and applications.
<<lessQubit project is based on the qmailrules qmail server installation style. It has the same features as other similar tools (like vqadmin and qmailadmin), and it also gives you full control to administer your server with all sorts of features and applications.
Download (0.038MB)
Added: 2006-02-22 License: GPL (GNU General Public License) Price:
1341 downloads
POE::Session::GladeXML2 0.3.1
POE::Session::GladeXML2 is a Perl module that can emit POE events for Gtk2 callbacks. more>>
POE::Session::GladeXML2 is a Perl module that can emit POE events for Gtk2 callbacks.
SYNOPSIS
package test;
use POE::Session::GladeXML2;
# the name of the sub needs to match with the name you entered in
# the glade signal handler dialog.
sub on_button1_clicked {
print STDERR "button clickedn";
}
sub new {
[... object creation ...]
my $session = POE::Session::GladeXML2->create (
glade_object => $self,
glade_file => test.glade,
glade_args => widgetname,
[... POE Session params ...]
);
return $self;
}
Gtk2::GladeXML->init;
my $foo = test->new;
$poe_kernel->run();
A simple helper module that lets you connect callback names from your .glade file with methods of an object. These methods are called as POE callback or postback methods. POE::Session::GladeXML automatically determines whether gtk expects the signal handler to return a value. If it does, a callback is used, otherwise a postback will be used.
<<lessSYNOPSIS
package test;
use POE::Session::GladeXML2;
# the name of the sub needs to match with the name you entered in
# the glade signal handler dialog.
sub on_button1_clicked {
print STDERR "button clickedn";
}
sub new {
[... object creation ...]
my $session = POE::Session::GladeXML2->create (
glade_object => $self,
glade_file => test.glade,
glade_args => widgetname,
[... POE Session params ...]
);
return $self;
}
Gtk2::GladeXML->init;
my $foo = test->new;
$poe_kernel->run();
A simple helper module that lets you connect callback names from your .glade file with methods of an object. These methods are called as POE callback or postback methods. POE::Session::GladeXML automatically determines whether gtk expects the signal handler to return a value. If it does, a callback is used, otherwise a postback will be used.
Download (0.011MB)
Added: 2006-07-18 License: Perl Artistic License Price:
1193 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above session 0.01 search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
