While the style guidelines would be the same as any non-Tk application, the design will be different.

While design patterns are not applicable for all applications, for GUI applications, adopting a good design pattern (I recommend the Model-View-Controller (MVC) pattern) can improve your general sanity considerably.

I would also strongly using OO Perl if you don't already. Trying to write a GUI app without proper encapsulation results in monolithic testaments to spaghetti and long sleepless nights in front of a monitor.

With both these things in mind, I would recommend creating an object diagram and a sample class diagram, presenting them to the development team and incorporating them into your set of artifacts, and performing design reviews periodically to make sure folks conform to the standard model you choose.

If you don't use UML right now, allow me to offer a plug: I find Dia a simple but stable and highly useful UML diagramming tool if you need to create some diagrams but don't need the full feature set of something like Rational Rose or Object Domain (which don't forward or reverse engineer Perl anyway). I think it comes default with most Red Hat installs these days ....

Hope this helps :-)

In reply to Re: Perl Tk coding guidelines? by Starky
in thread Perl Tk coding guidelines? by Snowman

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.