anchor.diff:   Denotes the method that returns the Panel's view. The view can be any
    class that extends GWT's `Widget` class or implements GWT's
    `IsWidget` interface. In this example, we're returning a GWT `Label`,
  - which is a GWT widget that represents `<div>` element with text in
  - it. Every Panel must have a `@WorkbenchPartView` method.
  + which is a GWT API for a `<div>` element with text in it. Every Screen
  + must have a `@WorkbenchPartView` method.
   
   .About Client-Side Scopes
   NOTE: CDI scopes in the client side are tied to the lifecycle of the
  
positive.code: inherit a GWT module, make sure it's also a dependency in your
  pom.xml.
  
  
  == Time to see it work!
  
  We've come a long way since we started with that empty
  
negative.code: you normally put in there for bootstrapping an UberFire app? Let's
  first create a panel and then come back to that question.
  
  == Create a Workbench Screen
  
  UberFire interfaces are made up of a few fundamental building blocks:
  Widgets, Layout Panels, Screens, Workbench Panels, Menu Bars, Tool
  Bars, and Perspectives. Layout Panels can contain Widgets and other
  Layout Panels, and Perspectives contain Workbench Panels, an optional
  Menu Bar, and an optional Tool Bar. Perspectives split up the screen
  into multiple resizeable regions, and end users can drag and drop
  Panels between these regions to customize their workspace.
  
  To create your first screen, create the file
  `src/main/java/com/mycompany/uftutorial/client/HelloWorldScreen.java`:
  
  [source,java]
  ---------
  package com.mycompany.uftutorial.client;
  
  import javax.enterprise.context.Dependent;
  
  import org.uberfire.client.annotations.WorkbenchPartTitle;
  import org.uberfire.client.annotations.WorkbenchPartView;
  