I cannot say if it is 'correct', but I like it. It separates everything out nicely and keeps each class down to a manageable length. Each class then has a very specific function.
The only minor part that took me a couple reads to get my head around was this part in the StopwMain class.
It seemed cumbersome to declare the view and controller and then have to assign the view to the controller and use two controller methods to configure the view. It is nice having them split out, but at the same time the two classes are so dependent on each other, it results in this kind of required information
exchange. I suppose that is the big issue with MVC coding. Trying to separate everything without obfuscating it too much.
Though I blame my slow-moving brain cells more than the code itself for the time it took me to grasp that piece.
I need to read up on Action and AbstractAction. I like that approach better than defining ActionPerformed with an endless if...else construct.
Thanks,
John S.