Hi.. I've made some simple Tk apps, used a bunch of the different widgets, but I'm now wanting to put together an application that is more sizeable in the tasks it performs and the hardest part for me is how to organize the code. I'm using a "Notebook" widget to hold 4 tabs worth of functionality. Each tab is then a sizeable screen holding a number of other widgets.

One layout I pondered was that the functionality(subs) for each screen(tab of notebook) should be each be in their own namespace.(package) Another was I should keep everything in one namespace and just pre-pend the subroutine names with the name of the screen/tab they act upon.

Re-organizing code after its written can be somewhat painful, so I'd appreciate any perspectives or links to help me decide. thanks!

In reply to Seeking input on perl/Tk code design by blueAdept

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!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            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.