It depends. ;-)
I've used MVC in the past. But I've also split my applications by function: use a module that, say, deals with displaying an image. It'll both have the "business logic" and the interaction with the widgets to display it.
But most often, I use something in between. In the backend, there's code that deals with the "model", but the frontend code that deals with displaying and input also does input validation and some state transisitions.
In reply to Re: How to organize a Perl TK application?
by JavaFan
in thread How to organize a Perl TK application?
by Brutha
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |