- Strip trailing dots from a few lines (and put one back I've previously
wrongly removed in a similar raid)
- Reduce excessive whitespace in several places
Tk::Role::Dialog is meant to be used as a Moose role to be composed for easy Tk
dialogs creation.
It will create a new toplevel with a title, and possibly a header as well as
some buttons.
One can create the middle part of the dialog by providing a _build_gui() method,
that will receive a Tk::Frame where widgets are supposed to be placed.
The attributes (see below) can be either defined as defaults using the
_build_attr() methods, or passed arguments to the constructor call. The only
mandatory attribute is parent, but you'd better provide some other attributes if
you want your dialog to be somehow usable! :-)
WWW: http://search.cpan.org/dist/Tk-Role-Dialog/
Menu entries are often also available in toolbars or other widgets. And
sometimes, we want to enable or disable a given action, and this means having to
update everywhere this action is allowed.
This module helps managing actions in a Tk GUI: just create a new object,
associate some widgets and bindings with add_widget() and then de/activate the
whole action at once with enable() or disable().
WWW: http://search.cpan.org/dist/Tk-Action/
Tk is a great graphical toolkit to write desktop applications. However, one can
get bothered with the constant typing of quotes and options. Tk::Sugar provides
handy subs for common options used when programming Tk.
Benefits are obvious:
- Reduced typing: The constant need to type => and '' is fine for one-off cases,
but the instant you start using Tk it starts to get annoying.
- More compact statements: Reduces much of the redundant typing in most cases,
which makes your life easier, and makes it take up less visual space, which
makes it faster to read.
- No string worries: Strings are often problematic, since they aren't checked at
compile-time. Sometimes it makes spotting an error a difficult task. Using
this alleviates that worry.
WWW: http://search.cpan.org/dist/Tk-Sugar/
When programming Tk, it's almost always a good idea to keep a reference to the
widgets that you created in the interface. Most of the time, a simple hash is
enough; but it is usually wrapped up in methods to make the hash private to the
window object. And of course, those methods are duplicated in all modules, under
a form or another.
Since duplication is bad, this module implements a Moose role implementing those
methods once and forever. This implies that your class is using Moose in order
to consume the role.
WWW: http://search.cpan.org/dist/Tk-Role-HasWidgets/
Unless you need to communicate with Zope 2 APIs, you're probably
better off using Python's built-in datetime module.
WWW: http://pypi.python.org/pypi/DateTime
Submitted by: Ruslan Mahmatkhanov <cvs-src@yandex.ru> (via email)
