> Then why not just create a configuration panel so your designer can > configure the number of items to display?
Scenario: Let's say 8 different pages use the same SongChartPanel and each wants to list a different number of songs. Providing a configuration panel for the web designer to configure a 'count' value for each instance where the panel is used is more work and it adds presentation domain stuff to the database. It also has the requirement of associating the 'count' parameter with each 'usage' of the panel in the model. Whenever they want to add another panel to a markup a new configuration property needs to be made available for configuration in the configuration panel and somehow specify 'which' panel instance in 'which' markup they are configuring. Seems much more simple and quicker and more MVC if they could simply specify that presentation oriented information right there in the presentation layer (markup) in which they use the instance: <span wicket:id="songChartPanel" wicket:attr="count=50" /> I've thought of a very ugly way of doing it with the current version of wicket but it relies on quite a lot of smoke and mirrors and hooking into the component creation process. I'll give that a go for now. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
