• Post Reply Bookmark Topic Watch Topic
  • New Topic

OOP computation and GUI - how seperate?  RSS feed

 
Matt Fielder
Ranch Hand
Posts: 158
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yeah, I know its a weird subject.

I understand the concepts of OOP and the benefits of designing software this way. I'm ok with that.

When designing a GUI, how seperate should you make your GUI from your actual program? I'll try to explain...

Every example that I've seen in books etc has shown the computational portion of a prog. in the same class as the GUI creation. I'm assuming that its done that way in these examples for simplicity. In a larger design, is it advisable to design the computation completely seperate from the GUI? How seperate should they be?

Make sense?
[ January 28, 2005: Message edited by: Matt Fielder ]
 
Ernest Friedman-Hill
author and iconoclast
Sheriff
Posts: 24215
37
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You're correct in assuming that most textbook examples are single classes for simplicity. In the real world, even the simplest programs will have dozens of classes, and applications of any substance can easily have many thousands of classes.

In general, you'll want fairly complete separation between computation and the GUI, for a number of reasons ranging from ease of modification to ease of testing.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!