Hi,
On Tue, May 20, 2014 at 9:55 AM, Simon B <simon.bott...@gmail.com> wrote: > Hi David, > > Your post reminded me of this quote from a (completely unrelated) post on > Stack Overflow: > > "Note that it is generally better to describe the goal, rather than the > strategy. 'Store changed file in Jar' is a strategy, whereas 'Save > preferences between runs' might be the goal" > > > http://stackoverflow.com/questions/5052311/how-can-an-app-use-files-inside-the-jar-for-read-and-write/5052359#5052359 > > You seem to have your mind set on the strategy which doesn't really sit > well > with Wicket. I can understand your frustration as if you had direct access > to the html as you might with a jsp then you could you achieve your goal > very quickly. > Why? What he want can be easily achieved with panels and the factory pattern I mentioned on a previous e-mail. IMHO the problem just arises because he's trying to use wicket in a way it is not intended to be used. > As I understand your post, Wicket doesn't work in the way that would allow > you to achieve your goal with the strategy that you've chosen. > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Conditional-input-types-tp4665924p4665955.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro