PerlGTK is pretty cool, it's relatively easy to use if you know how to use it. Documentation is completely lacking. I would not try to program with it unless you've programmed with GTK+ in some form or another previously. Most things mimic the C calling sequece pretty well, such as

gtk_label_new("text");
[download]

is

Gtk::Label->new("text");
[download]

and so on.

The bad part is when you get into some of the C calls that return things through the parameter list, i.e. a function that returns a value, but takes 2 pointers in its arguments which it sets to valuable information later. What is the way to mimic this call? Should it return a list of items that it normally would have assigned via pointers, or should it do something else? If it returns a list, then where are the gaps in the arguments, etc.

A lot of figuring it out is hit and miss just trying things out. Alternatively, you can dig through the source code of the example programs that come with perlgtk.

If you're comfortable with perl, perl objects, and modules, and you've programmed with gtk before, go for it. Otherwise, you might want to wait until some documentation is out and about.

---

---

• 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.