really? and here i thought i was using the response from iheadercontributor which is the preferred way of writing out javascript.
and no we cannot get all references because we do not know the markup until after first render. -igor On Fri, Dec 12, 2008 at 11:06 AM, Bruno Cesar Borges <[email protected]> wrote: > Javascript could get all child references to that component (markupId), and > apply that code to them as well. > > In this case you submitted, the problem would be only with reaaally hacked > code, like doing weird stuff with 'response' instead of using Behaviours. > > -----Original Message----- > From: Igor Vaynberg [mailto:[email protected]] > Sent: Friday, December 12, 2008 4:41 PM > To: [email protected] > Subject: Re: how to reuse a label in the same page? > > > huh? so if i have a behavior that does: > > response.write("getElementById('"+getMarkupId()+"').style.display='none';"); > > how does that work??? > > -igor > > On Fri, Dec 12, 2008 at 10:38 AM, Bruno Cesar Borges > <[email protected]> wrote: >> It could continue to return "foo". But when processing ajax responses, >> wicket:ref will register, through Javascript, the references to "foo", >> somehow. So this approach wouldn't break any code. >> >> -----Original Message----- >> From: Igor Vaynberg [mailto:[email protected]] >> Sent: Friday, December 12, 2008 4:35 PM >> To: [email protected] >> Subject: Re: how to reuse a label in the same page? >> >> >> what do we return from getmarkupid() because that is what the code >> uses to output that markupid for the javascript that needs to >> manipulate the dom nodes. >> >> -igor >> >> On Fri, Dec 12, 2008 at 10:28 AM, Bruno Cesar Borges >> <[email protected]> wrote: >>> I'm pretty sure it is possible to register all markup IDs generated to >>> referenced nodes. >>> >>> new Label("foo", "Foo"); >>> >>> <div wicket:id="foo">ddd</div> >>> <div wicket:ref="foo">again</div> >>> >>> outputs: >>> <div id="foo0">Foo</div> >>> <div id="foo1">Foo</div> >>> >>> Then it would be possible to do, for instance, an Ajax update over all >>> nodes. >>> >>> >>> >>> -----Original Message----- >>> From: Igor Vaynberg [mailto:[email protected]] >>> Sent: Friday, December 12, 2008 4:11 PM >>> To: [email protected] >>> Subject: Re: how to reuse a label in the same page? >>> >>> >>> what happens once you add a behavior that uses markup id? or even call >>> setoutputmarkupid(true) on that component? >>> >>> -igor >>> >>> On Fri, Dec 12, 2008 at 9:35 AM, Jeremy Thomerson >>> <[email protected]> wrote: >>>> Oops - you are right there - the component use check was turned off in this >>>> app (I just threw the example into an existing app to test it). >>>> >>>> While I don't typically use this, or have this use case, I'm not clear on >>>> what is "fundamentally wrong" with this - you have a component you want two >>>> places in a page or panel, etc... So, why mustyou create two duplicate >>>> components? That seems more wrong than the former. >>>> >>>> -- >>>> Jeremy Thomerson >>>> http://www.wickettraining.com >>>> >>>> >>>> On Fri, Dec 12, 2008 at 11:23 AM, Martijn Dashorst < >>>> [email protected]> wrote: >>>> >>>>> Now run your application in virgin development mode. The fact that we >>>>> disable the component use check in production mode doesn't make it >>>>> less evil. >>>>> >>>>> Martijn >>>>> >>>>> On Fri, Dec 12, 2008 at 5:56 PM, Jeremy Thomerson >>>>> <[email protected]> wrote: >>>>> > Martijn, >>>>> > Actually, what I described does work - try this on any page: >>>>> > >>>>> > JAVA (added only once - since you couldn't add two with the same ID >>>>> anyway): >>>>> > add(new Label("test", "this is a test")); >>>>> > >>>>> > HTML: >>>>> > <span wicket:id="test">[]</span><br /> >>>>> > <span wicket:id="test">[]</span><br /> >>>>> > >>>>> > OUTPUT: >>>>> > <span wicket:id="test">this is a test</span><br /> >>>>> > <span wicket:id="test">this is a test</span><br /> >>>>> > Right or wrong, it currently works that way. (1.4-SNAPSHOT - and I know >>>>> > I've used it in past versions as well) >>>>> > -- >>>>> > Jeremy Thomerson >>>>> > http://www.wickettraining.com >>>>> > >>>>> > >>>>> > On Fri, Dec 12, 2008 at 1:17 AM, Martijn Dashorst < >>>>> > [email protected]> wrote: >>>>> > >>>>> >> Nope, wicket:id is a 1-1 mapping at the same dom tree level. You can >>>>> >> reuse id's at different levels or in different branches of the dom >>>>> >> tree, but not as siblings. >>>>> >> >>>>> >> <a href="#" wicket:id="foo"><span wicket:id="foo"></span></a> works >>>>> >> but another >>>>> >> <a href="#" wicket:id="foo">....</a> will fail (and rightfully so) >>>>> >> >>>>> >> Martijn >>>>> >> >>>>> >> On Fri, Dec 12, 2008 at 6:20 AM, Jeremy Thomerson >>>>> >> <[email protected]> wrote: >>>>> >> > I'm pretty sure that you can just add it once in Java and multiple >>>>> times >>>>> >> in >>>>> >> > the HTML, although I've never pondered the (potential) side-effects >>>>> >> > of >>>>> >> > this. Give it a shot and let us know how it works for you. With >>>>> >> something >>>>> >> > as stateless / simple as a BookmarkablePageLink, there probably >>>>> couldn't >>>>> >> be >>>>> >> > much in the way of side-effects, although with very complex, stateful >>>>> >> > components, I could see that maybe there would be an issue... >>>>> (maybe??) >>>>> >> > -- >>>>> >> > Jeremy Thomerson >>>>> >> > http://www.wickettraining.com >>>>> >> > >>>>> >> > >>>>> >> > On Thu, Dec 11, 2008 at 3:29 PM, novotny <[email protected]> >>>>> wrote: >>>>> >> > >>>>> >> >> >>>>> >> >> >>>>> >> >> Basically I need two of the same links on the page, and it looks >>>>> >> >> like >>>>> I >>>>> >> >> have >>>>> >> >> to do this which just seems kinda lame... >>>>> >> >> >>>>> >> >> add(new BookmarkablePageLink<String>("personaldetails", >>>>> >> >> PersonalDetailsPage.class)); >>>>> >> >> add(new BookmarkablePageLink<String>("personaldetails2", >>>>> >> >> PersonalDetailsPage.class)); >>>>> >> >> >>>>> >> >> .... >>>>> >> >> >>>>> >> >> Click Here >>>>> >> >> Profile page >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> jWeekend wrote: >>>>> >> >> > >>>>> >> >> > Jason, >>>>> >> >> > >>>>> >> >> > What are you trying to achieve? >>>>> >> >> > >>>>> >> >> > Here are some ideas that may give the desired effect, depending on >>>>> >> what >>>>> >> >> > that is ... >>>>> >> >> > >>>>> >> >> > 1 - Make a model for your data and give that to all the Label >>>>> >> instances >>>>> >> >> as >>>>> >> >> > required, (but each with their unique id and separate markup). >>>>> >> >> > 2 - Use a repeater (like a ListView) to render several labels (no >>>>> >> >> > repetition of Java code or markup). >>>>> >> >> > 3 - Write a method that takes a model (or just a String) and an >>>>> >> >> > id, >>>>> >> that >>>>> >> >> > returns an appropriately configured Label instance (saves on >>>>> >> repeating >>>>> >> >> > Java code - still need markup per component and your own unique >>>>> ids). >>>>> >> >> > >>>>> >> >> > Regards - Cemal >>>>> >> >> > http://www.jWeekend.co.uk <http://www.jweekend.co.uk/> < >>>>> http://www.jweekend.co.uk/> < >>>>> >> http://www.jweekend.co.uk/> jWeekend >>>>> >> >> > >>>>> >> >> > >>>>> >> >> > >>>>> >> >> > novotny wrote: >>>>> >> >> >> >>>>> >> >> >> >>>>> >> >> >> I have a simple label "hello" and I want to display it twice in >>>>> the >>>>> >> same >>>>> >> >> >> page, but wicket complains the wicket:id needs to be unique in my >>>>> >> >> >> page.... what do I need to do, is there an alias or something? >>>>> >> >> >> >>>>> >> >> >> Thanks, Jason >>>>> >> >> >> >>>>> >> >> > >>>>> >> >> > >>>>> >> >> >>>>> >> >> -- >>>>> >> >> View this message in context: >>>>> >> >> >>>>> >> >>>>> http://www.nabble.com/how-to-reuse-a-label-in-the-same-page--tp20964351p20964551.html >>>>> >> >> Sent from the Wicket - User mailing list archive at Nabble.com. >>>>> >> >> >>>>> >> >> >>>>> >> >> --------------------------------------------------------------------- >>>>> >> >> To unsubscribe, e-mail: [email protected] >>>>> >> >> For additional commands, e-mail: [email protected] >>>>> >> >> >>>>> >> >> >>>>> >> > >>>>> >> >>>>> >> >>>>> >> >>>>> >> -- >>>>> >> Become a Wicket expert, learn from the best: http://wicketinaction.com >>>>> >> Apache Wicket 1.3.4 is released >>>>> >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >>>>> >> >>>>> >> --------------------------------------------------------------------- >>>>> >> To unsubscribe, e-mail: [email protected] >>>>> >> For additional commands, e-mail: [email protected] >>>>> >> >>>>> >> >>>>> > >>>>> >>>>> >>>>> >>>>> -- >>>>> Become a Wicket expert, learn from the best: http://wicketinaction.com >>>>> Apache Wicket 1.3.4 is released >>>>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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] >>> >>> *************************************************************************************************** >>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) >>> destinatários(s) acima identificado(s), >>> podendo conter informações e/ou documentos confidencias/privilegiados e seu >>> sigilo é protegido por >>> lei. Caso você tenha recebido por engano, por favor, informe o remetente e >>> apague-a de seu sistema. >>> Notificamos que é proibido por lei a sua retenção, disseminação, >>> distribuição, cópia ou uso sem >>> expressa autorização do remetente. Opiniões pessoais do remetente não >>> refletem, necessariamente, >>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas >>> autorizadas." >>> >>> >>> "Warning: This message was sent for exclusive use of the addressees above >>> identified, possibly >>> containing information and or privileged/confidential documents whose >>> content is protected by law. >>> In case you have mistakenly received it, please notify the sender and >>> delete it from your system. >>> Be noticed that the law forbids the retention, dissemination, distribution, >>> copy or use without >>> express authorization from the sender. Personal opinions of the sender do >>> not necessarily reflect >>> CETIP's point of view, which is only divulged by authorized personnel." >>> *************************************************************************************************** >>> >>> >>> --------------------------------------------------------------------- >>> 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] >> >> *************************************************************************************************** >> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) >> destinatários(s) acima identificado(s), >> podendo conter informações e/ou documentos confidencias/privilegiados e seu >> sigilo é protegido por >> lei. Caso você tenha recebido por engano, por favor, informe o remetente e >> apague-a de seu sistema. >> Notificamos que é proibido por lei a sua retenção, disseminação, >> distribuição, cópia ou uso sem >> expressa autorização do remetente. Opiniões pessoais do remetente não >> refletem, necessariamente, >> o ponto de vista da CETIP, o qual é divulgado somente por pessoas >> autorizadas." >> >> >> "Warning: This message was sent for exclusive use of the addressees above >> identified, possibly >> containing information and or privileged/confidential documents whose >> content is protected by law. >> In case you have mistakenly received it, please notify the sender and delete >> it from your system. >> Be noticed that the law forbids the retention, dissemination, distribution, >> copy or use without >> express authorization from the sender. Personal opinions of the sender do >> not necessarily reflect >> CETIP's point of view, which is only divulged by authorized personnel." >> *************************************************************************************************** >> >> >> --------------------------------------------------------------------- >> 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] > > *************************************************************************************************** > "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) > acima identificado(s), > podendo conter informações e/ou documentos confidencias/privilegiados e seu > sigilo é protegido por > lei. Caso você tenha recebido por engano, por favor, informe o remetente e > apague-a de seu sistema. > Notificamos que é proibido por lei a sua retenção, disseminação, > distribuição, cópia ou uso sem > expressa autorização do remetente. Opiniões pessoais do remetente não > refletem, necessariamente, > o ponto de vista da CETIP, o qual é divulgado somente por pessoas > autorizadas." > > > "Warning: This message was sent for exclusive use of the addressees above > identified, possibly > containing information and or privileged/confidential documents whose content > is protected by law. > In case you have mistakenly received it, please notify the sender and delete > it from your system. > Be noticed that the law forbids the retention, dissemination, distribution, > copy or use without > express authorization from the sender. Personal opinions of the sender do not > necessarily reflect > CETIP's point of view, which is only divulged by authorized personnel." > *************************************************************************************************** > > > --------------------------------------------------------------------- > 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]
