Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Have a look at <a href="http://www.oracle.com/technetwork/articles/javase/index-142890.html" rel="noreferrer">Sun's (Oracle's) suggestions</a>.</p> <p>As one simplification, you could have each component (model, view, controller) register with a top-level application component to provide a single point of reference rather than individual references between each component (your A or B). The article I cite provides ideas for push and pull design; I'd recommend push as a more popular modern approach. Disclosure: I have experience with Java and MVC but not MVC in Swing per se.</p> <blockquote> <p>where should I instantiate the View, the Model and the Controller of the SettingsFrame?</p> </blockquote> <p>Sure, yes, or in a top-level application component.</p> <blockquote> <p>how should I handle more specific features that (apparently) lacks one or two of the MVC "legs" (either Model or View or Controller)?</p> </blockquote> <p>I would implement GUI-only pieces as your own GUI library. And purely algorithm/service pieces as a services library.</p> <blockquote> <p>Should I process massive data in Model or Controller?</p> </blockquote> <p>Data processing algorithms would fit nicely in a controller or even service library; your model should not do much processing at all beyond possibly data type conversion or validation.</p> <blockquote> <p>How to correctly keep and use an object with settings through the whole application?</p> </blockquote> <p>See my note on registration; a singleton may be appropriate.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload