I just created a JIRA before you replied. https://issues.apache.org/jira/browse/WICKET-2809
I understand your concern, but I dont fully agree with you. As you know, less and clean coding is always a good thing and best to be the part of the tool. Regards. --- On Mon, 3/29/10, Igor Vaynberg <[email protected]> wrote: > From: Igor Vaynberg <[email protected]> > Subject: Re: better way setting up ID for a Wicket component? > To: [email protected] > Date: Monday, March 29, 2010, 10:32 PM > im letting you know. we dont need to > litter the public api with such > trivial methods, the api has a large surface area as it is. > i am sure > as you code more with wicket you will find another 30 such > trivial > methods that will be useful to you, this is what static > imports are > for. > > -igor > > On Mon, Mar 29, 2010 at 6:18 PM, James Carman > <[email protected]> > wrote: > > Perhaps. File a JIRA report (https://issues.apache.org/jira/browse/WICKET) > > and ask for it as a "New Feature." If the core > developers don't like the > > idea, I'm sure they'll let you know. :) > > > > > > On Mon, Mar 29, 2010 at 9:13 PM, David Chang <[email protected]>wrote: > > > >> Using an external helper should do the trick, but > it feels not so natural > >> as a convenince method as mentioned in my previous > email. > >> > >> Would it be possible for such a method make its > way into a future release? > >> > >> Regards. > >> > >> > >> --- On Mon, 3/29/10, James Carman <[email protected]> > wrote: > >> > >> > From: James Carman <[email protected]> > >> > Subject: Re: better way setting up ID for a > Wicket component? > >> > To: [email protected] > >> > Date: Monday, March 29, 2010, 9:07 PM > >> > You could make your own helper method > >> > that sets both to the same thing and > >> > returns the component. Just modify what I > sent > >> > earlier. > >> > > >> > On Mon, Mar 29, 2010 at 9:03 PM, David Chang > <[email protected] > >> >wrote: > >> > > >> > > Not sure whether the help method will do > the trick of > >> > one-liner code. > >> > > > >> > > I feel that it would be much nice if > Wicket could have > >> > the following > >> > > additional method for a Componment: > >> > > > >> > > Component setMarkupIdToWicketId(). > >> > > > >> > > Re-using a Wicket Id as markup id as > convention should > >> > be best practice. Am > >> > > I right? I am new in wicket and sorry if > I am wrong. > >> > > > >> > > Best. > >> > > > >> > > > >> > > > >> > > --- On Mon, 3/29/10, James Carman <[email protected]> > >> > wrote: > >> > > > >> > > > From: James Carman <[email protected]> > >> > > > Subject: Re: better way setting up > ID for a > >> > Wicket component? > >> > > > To: [email protected] > >> > > > Date: Monday, March 29, 2010, 7:16 > PM > >> > > > helper method? > >> > > > > >> > > > protected <T extends > Component> T > >> > setMarkupId(T > >> > > > component, String markupId) > >> > > > { > >> > > > >> > > component.setMarkupId(markupId); > >> > > > return component; > >> > > > } > >> > > > > >> > > > > >> > > > On Mon, Mar 29, 2010 at 7:00 PM, > David Chang > >> > <[email protected] > >> > > >wrote: > >> > > > > >> > > > > Here is what I am using the > follow pattern > >> > to set up > >> > > > ID for a wicket > >> > > > > component: > >> > > > > > >> > > > > Label abc = new Label("abcd", > "abcdedfg"); > >> > > > > > >> > > abc.setOutputMarkupId(true).setMarkupId(abc.getId()); > >> > > > > > >> > > > > It takes two lines to do > this. > >> > > > > > >> > > > > Can I do something like > >> > > > > > >> > > > > Label abc = new Label("abcd", > >> > > > > > >> > > "abcdedfg").setOutputMarkupId(true).setMarkupId(???); > >> > > > > > >> > > > > Is this doable? If yes, then > what should go > >> > to replace > >> > > > ??? > >> > > > > > >> > > > > Thanks! > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > >> > > --------------------------------------------------------------------- > >> > > > > 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] > >> > > > >> > > > >> > > >> > >> > >> > >> > >> > --------------------------------------------------------------------- > >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
