[wicket] branch master updated: Removed staruml as it's not used

[ad...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

adelbene pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/wicket.git


The following commit(s) were added to refs/heads/master by this push:
     new 066a44c  Removed staruml as it's not used
066a44c is described below

commit 066a44c83ae682a8b8c7b202eeda968cdc424178
Author: Andrea Del Bene <ad...@apache.org>
AuthorDate: Sun Jan 10 20:49:07 2021 +0100

    Removed staruml as it's not used
---
 wicket-user-guide/src/main/asciidoc/helloWorld.adoc | 18 ------------------
 1 file changed, 18 deletions(-)

diff --git a/wicket-user-guide/src/main/asciidoc/helloWorld.adoc b/wicket-user-guide/src/main/asciidoc/helloWorld.adoc
index 52bec1b..3408fb3 100644
--- a/wicket-user-guide/src/main/asciidoc/helloWorld.adoc
+++ b/wicket-user-guide/src/main/asciidoc/helloWorld.adoc
@@ -4,23 +4,5 @@ Both frameworks share the same component-based architecture: in AWT we have a _W
 
 image::../img/uml-component.png[]
 
-....
-@startuml
-package java.awt {
-	class Component
-	class Window extends Component
-	
-	Window "*" *-- "1" Component
-}
-
-package org.apache.wicket {
-	class org.apache.wicket.Component
-	class WebPage extends org.apache.wicket.Component
-	
-	WebPage "*" *-- "1" org.apache.wicket.Component
-}
-@enduml
-....
-
 In both frameworks we find a base class for GUI components called _Component_. Wicket pages can be composed (and usually are) by many components, just like AWT windows are composed by Swing/AWT components. Both frameworks promote the reuse of presentation code and GUI elements building custom components. Even if Wicket already comes with a rich set of ready-to-use components, building custom components is a common practice when working with this framework. We'll learn more about custom c [...]