Boris, thanks for sharing your thoughts: > IDs are needed for e.g. AJAX > functionality.
I cannot agree on this. In the context of wicket for the web framework, you actually dont need to create ID. Let Wicket to create whatever ID wicket deems right. In my understanding, and actually in my case that initiated this thread, is to style certain elements and I hope to have meaningful markup IDs. I have meaningful wicket IDs in my case, and I simply want to do the same for markup IDs. Thanks, David --- On Tue, 3/30/10, Boris Goldowsky <[email protected]> wrote: > From: Boris Goldowsky <[email protected]> > Subject: Re: better way setting up ID for a Wicket component? > To: [email protected] > Date: Tuesday, March 30, 2010, 5:06 PM > IDs are needed for e.g. AJAX > functionality. The default Wicket implementation of > markup IDs will create them smartly, never creating > duplicate ids even in the case of multiple instances of > panels, repeaters, etc. > > As I understand Wicket best practice, it is never to call > setMarkupId() at all, and just let the smart default thing > happen. If you *must* call it because you have some > special requirement for particular IDs, then you take on the > responsibility for making sure your IDs are unique > yourself. In this light, a setMarkupIdToWicketId() > method is a dangerous thing. > > Bng > > David Chang wrote: > > Craig, I really appreciate your input. If a panel is > reused more than one time on the same page, then the panel's > components should not use IDs in the first place. It would > always violate valid HTML. Correct? > > > > Regards. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
