In this exercise, Buttons play a product role and Dialogs act as creators. Different types of dialogs require their own types of elements. We will create a subclass for each dialog type and override their factory methods. Each dialog type will instantiate proper button classes. Base dialog works with products using their common interface, so its code remains functional after all changes.

$```$

$1.$ We have an interface, called Button, which defines two methods, render$()$ and onClick$().$

$2.$ Create an HtmlButton class, which implements Button. Provide the implementation for both

render$()$ and onClick$()$ methods.

public void render$()\{$

Systemeoutebrintlo$("$Test Button"$$

$\}$

enclick$($L:

public void orClick$()\{$

Systemeout$\mathrm{.}0$Rintlo$("$Click$!$ Button says $-$ 'Hello World!$\text{'}")$;

$\}$

$```$

$3.$ Create a WindowsButton class, which also implements Button. Provide the implementation for both render$()$ and onClick$()$ methods.

$```$

JPanel panel $=$ new JPanel$()$:

dLrame frame $=$ new liErave$($F$)$

$3$Button hutton:

public void render$()\{$

$\}$

public void ooClick$()\{$

$\}$

$\}$

$```$

$4.$ Create a base creator, called Dialog. Have two methods in it$.$

public void ceoderbiodow$()\{$

$\}$

public abstract Button sceateButton$()$:

$5.$ Create two concrete creators: HtmlDialog and WindowsDialog, by providing implementation for the abstract method createButton$().$ One returns new WindowsButton$(),$ the other returns new HtrolButton$().$

$6.$ Use the following client code to test it$.$

$```$

public class Client $\{$

private static Dialog dialeg:

public static void main$($String$[]$ acgs$)\{$

configure$()$:

$\}$

run$($$$)$

$/**$

$*$ The concrete factory is usually chosen depending on configuration or

$*$ environment options.

$*/$

static void configure$()\{$

$```$