WxPerl is nice because I could make native GUIs for Mac OS X (pTk and Gtk-perl require X11).
And I believe perl/tk doesn't work at all on older versions of MacOS X, so choosing perl/tk means locking out users who haven't stayed on the $130/version upgrade treadmill. My perl/tk app was meant to be cross-platform, but I ended up deciding not to support it any more on any platform but Linux, because supporting Windows users was eating up large amounts of my time, and it was an open-source project that I wasn't making any money on. No matter how cross-platform one of these toolkits is supposed to be, I think making an app cross-platform still requires an order of magnitude more maintenance work once the app is mature. I've also soured on the whole idea of bringing OSS to the Windows-using masses -- I think it just sucks energy out of the OSS movement, and there's no real return on the investment, because those folks are happy with Windows, and are going to keep on using it.
-
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.
|
