It makes sense when you look at a component as a holder of a set of components. However, I don't think put makes much sense when you think about building a component tree.
Technically, put may be right, but I would say it's a little bit late in the game to change add to put isn't it? And personally, I don't think it sounds better nor is the more obvious choice. And having put instead of replace and addOrReplace is only more confusing imo. Eelco On 4/1/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
To join in on the 3 letter lingo [1]: put() would be more accurate, as it resembles the contract for a Set. Martijn [1] http://en.wikipedia.org/wiki/Lingo_(game_show) -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
