Ideally, the console client would be simply a downloader, while the GUI
would use the same mechanisms to access the data, but give more
interactivty (renaming, prioritizing of downloads, etc.) Not sure if
this is the information you meant that was missing.<br><br><div><span class="gmail_quote">On 12/15/05, <b class="gmail_sendername">David Boddie</b> <<a href="mailto:david@boddie.org.uk">david@boddie.org.uk</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Thu, 15 Dec 2005, Arthur Pemberton wrote:<br><br>> I am new to Qt programming and PyQt. I am attempting to build a client for
<br>> AllofMp3.com, I already have most of the logic code down. But now I want to<br>> build a GUI with PyQt. What rules should I follow to make the program<br>> useable in the console, but also with a GUI?<br><br>
It depends on how the client is supposed to work. Will you run it each<br>time you want to interact with the server, or will you use it interactively?<br>Do you want to implement different behaviour for the GUI version to that
<br>provided by the console version?<br><br>If you can give us a better idea of the architecture/logic, we can suggest<br>ways to "wrap up" the console behaviour in a GUI, or other techniques to<br>keep the logic separate from the GUI code.
<br><br>David<br><br>_______________________________________________<br>PyKDE mailing list <a href="mailto:PyKDE@mats.imk.fraunhofer.de">PyKDE@mats.imk.fraunhofer.de</a><br><a href="http://mats.imk.fraunhofer.de/mailman/listinfo/pykde">
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde</a><br></blockquote></div><br><br clear="all"><br>-- <br>As a boy I jumped through Windows, as a man I play with Penguins.