anchor.diff:   * MVC Group parent-child relationships
    * MVC Group lifecycle
   
  -The goal of the Editor application shown here is to be provide basic editing capabilities fo text files. Each
  +The goal of the Editor application shown here is to provide basic editing capabilities for text files. Each
   file will be handled by its own tab; tabs will be located inside a tab container.
   
   . <<_tutorial_2_1,Creating an Editor application>>
  
positive.code: application. We select `editor` as the name of the new MVC group. There are 5 new files generated using the
  default templates. Take special care of the last message; the files were created but this doesn't mean the application
  will be able to instantiate the MVC group at runtime. The final piece of the puzzle is letting the application know
  that about this new MVC group, this is done by editing `Config.java`
  
  [source,java,options="nowrap"]
  .griffon-app/conf/Config.java
  
negative.code: include::{editor-swing-java}/griffon-app/views/editor/ContainerView.java[lines=16..-1]
  ----
  
  Here we find a `Window` object containing a `JMenuBar` and a tab container (a `JTabbedPane`) named _tabGroup_.
  This tab container is exposed to the outside world via a getter method; we'll see why it's done this way when the
  second MVC group comes into play. The View is also responsible for managing a `JFileChooser` that will be used to
  select files for reading. Notice the conditional enabling of the `save` action given the state of the `dirty` property
  