- GUI: use for cross platform *native* gui client side development - (only if you think Tk is the best you can do.)
- PPM: use for gui client side development on MS Windows using CPAN - (because ActiveState ppm is horribly broken and you cant utilise CPAN.
- Shipping: problems with MS Windows GUI/Perl apps when shipping - (because existing tools are bloated, proprietary).
I am ambivalent about using Perl for client
side *native* gui programming.
There is a great article by Eric Burke on
why GUI programming is hard that sums up why nicely -
namely server side development (with languages like Perl) allow for automation once the design problem(s)
can be defined.
Gui development on the otherhand, cannot be automated as easily. The other thing the mismatch between
skill sets between server side and gui client developers.
I would also be interested to know who develops gui apps aside from MS Windows? Any commercial apps or are they all inhouse? How do you ship? What front end do you use?
update: sp.
-
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.
|
