Oh yeah, and to answer your question regarding efficiency and time savings: what kind of efficiency and time saving are you looking for? There's a quote I like to cite:
Donald Knuth, preeminent computer scientist, wrote:"Premature optimization is the root of all evil."
If you mean efficiency and time savings in terms of computer cycles, then in a program as small as this, any differences coming from the way it's coded will be practically insignificant.
However, the more important and more costly consideration is ease of understanding, maintaining, and enhancing the code. That makes up the biggest chunk of cost in developing software. The whole point of using an object-oriented language, or any higher level language in fact, is to clarify concepts and relationships between information and actions taken on it. If you have one big glob of code in one class, it will be much more difficult to understand, maintain, and enhance in the long run than if you had responsibilities separated as I described in my previous reply.