Another aspect of OO design you might find helpful would be to separate purely UI (or purely GUI) logic from "back-end" processing logic. For example, if you have a module (or a few) to implement a set of methods for audio file manipulation, those methods could be invoked by either a command-line style app or a windowing app -- these two UI approaches could (perhaps should?) be separate scripts, but they both invoke the same set of processing methods for audio data, which simply means that they both use the same processing module(s).
As ikegami indicated above, one and/or the other UI approach could make use of functions that are available only for that particular UI, but since these are UI differences, they would have no impact on the back-end data processing module(s).
-
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.
|
