Despite some of the criticisms mentioned here, and including my own frustrations, my opinion is that Perl/Tk is still worth learning. I've tinkered a bit with some others and with the possible exception of Prima it seems to be the most Perlish. Once you get the hang of it, Perl/Tk is not very difficult at all. OTOH I really want to like Wx, but trying to learn it gives me fits and leaves me cross-eyed with a headache.
The collective Perl/Tk docs actually contain sufficient information scattered about to get you going, but its a bit difficult to sort through. The following PODs should cover most of what you need to get started. Also, there should be a lot of example code somewhere under @INC at Tk/demos/.
- Tk::UserGuide - This gives the basics and general overview. It also contains a list of standard widgets you should familiarize yourself with. Complex widgets are generally built with some combination of these.
- Tk::option - Basic introduction to widget options database & methods
- Tk::options - The standard widget options.
- Tk::Widget - Generic methods for widgets.
- Tk::pack - The most common and easiest geometry manager, its best to start with this one. There are also grid and place and form geometry managers.
- To build complex/custom widgets or subclass existing widgets:
- Tk::mega
- Tk::composite
- Tk::Derived
- Tk::ConfigSpecs
- Events, callbacks & binding:
- Tk::callbacks
- Tk::bind
- Tk::bindtags
- Tk::event
- Tk::after
Update: Here's a pdf Perl Tk reference designed to be printed & folded into a booklet. Its for an older version, but may be helpful to you.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|