Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

I would also advise looking at the "webapp" route, for the following reasons:

  • Everyone already has a web browser - so there's nothing to distribute/install.
  • The browser becomes your interface/GUI - everyone is already familiar with this stuff, so there's no need to document/explain basic stuff.
  • You only have to install/maintain one version of your app - the one on the web server. If you need to fix a bug, add a new feature, etc. you can do it in one place and all users instantly benefit from the change. Otherwise, you have to worry about pushing out the new version, dealing with users who won't upgrade, etc.
  • Documentation can be centralized to the web also - no need to distribute doc files, worry with old versions, etc.

I realize that not every desktop utility can be converted into a web app. Some things are easier to do than others, some are hard, some impossible. But if there's anyway to make it work, it's totally worth it.

I haven't done any development with wxPerl - but I've done lots of work with C++ using the wxWidgets library. The library is very large, and even a small "hello world" program results in a 15MB exe (but the overhead becomes less notable as your app gets larger). There are numerous DLL files that have to be installed along with the app. I've used something called "inno compiler" to bundle everything - but it's still a pain, especially if you have to support Win95, Win98, WinXP, Vista, Win7, etc. Some stuff doesn't work on all systems, some stuff doesn't work the *same* on all systems. It sounds like you're trying to do this PLUS bundle perl into the mix... not fun! Find a way to "webify" and I think you'll be much happier.


In reply to Re: Packaging Perl Programs (is) Painful by scorpio17
in thread Packaging Perl Programs (is) Painful by Sue D. Nymme

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others lurking in the Monastery: (11)
    As of 2014-10-23 21:35 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      For retirement, I am banking on:










      Results (129 votes), past polls