[PyKDE] Seperating logic code from gui code?

Arthur Pemberton pemboa at gmail.com
Fri Dec 16 15:47:13 GMT 2005

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.

On 12/15/05, David Boddie <david at boddie.org.uk> wrote:
> On Thu, 15 Dec 2005, Arthur Pemberton wrote:
> > I am new to Qt programming and PyQt. I am attempting to build a client
> for
> > AllofMp3.com, I already have most of the logic code down. But now I want
> to
> > build a GUI with PyQt. What rules should I follow to make the program
> > useable in the console, but also with a GUI?
> It depends on how the client is supposed to work. Will you run it each
> time you want to interact with the server, or will you use it
> interactively?
> Do you want to implement different behaviour for the GUI version to that
> provided by the console version?
> If you can give us a better idea of the architecture/logic, we can suggest
> ways to "wrap up" the console behaviour in a GUI, or other techniques to
> keep the logic separate from the GUI code.
> David
> _______________________________________________
> PyKDE mailing list    PyKDE at mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

As a boy I jumped through Windows, as a man I play with Penguins.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.riverbankcomputing.com/pipermail/pyqt/attachments/20051216/73370912/attachment.html

More information about the PyQt mailing list