. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.9. Hiding decorating elements with the wicket:enclosure tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 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 model, which will be the topic of chapter 11. 4.5. Summary In this chapter we have seen the basic elements that compose a Wicket application. We have started preparing the configuration artifacts needed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.9. Hiding decorating elements with the wicket:enclosure tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 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 model, which will be the topic of chapter 11. 4.5. Summary In this chapter we have seen the basic elements that compose a Wicket application. We have started preparing the configuration artifacts needed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.9. Hiding decorating elements with the wicket:enclosure tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 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 model, which will be the topic of chapter 11. 4.5. Summary In this chapter we have seen the basic elements that compose a Wicket application. We have started preparing the configuration artifacts needed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.9. Hiding decorating elements with the wicket:enclosure tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 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 model, which will be the topic of chapter 11. 4.5. Summary In this chapter we have seen the basic elements that compose a Wicket application. We have started preparing the configuration artifacts needed

look at a classic example of form to sign in a user with a username and password. ● Text felds elements are handled in Wicket with class TextField ● Example for a TextField: Java new TextField(“username” look at a classic example of form to sign in a user with a username and password. ● Text felds elements are handled in Wicket with class TextField ● Example for a TextField: Java new TextField(“username”