Re: Page Markup Inheritance Problem...
I would like to confirm to folks here that you can use a page that has a wicket:child element in it directly. You do not have to subclass it! I found that to be quite weird, but it was very helpful in our situation! On Thu, Oct 23, 2008 at 10:42 PM, Richard Paul [EMAIL PROTECTED] wrote: From the testing that I have done so far. Yes. This has been such an extra ordinary find for me. It is what I call a HOWZAT!!! wicket moment !! This is such a powerful feature. Hopefully someone can give us the official description of this concept. -Richard Paul Independent Contractor Chicago Area. On Thu, Oct 23, 2008 at 8:29 PM, James Carman [EMAIL PROTECTED] wrote: What if SuperPage is a page that is concrete? Can it display itself without having the wicket:child elements plugged in? On Thu, Oct 23, 2008 at 4:56 PM, Richard Paul [EMAIL PROTECTED] wrote: I ran into a similar situation last night. Not sure if this is what your looking for. BasePage - My Site Layout SuperPage - My Page Layout (e.g. a header area for what I am working with) SubPage - Actions ( e.g. forms for adding stuff etc.) When first navigating to SuperPage I only want to show links that the user needs to click on to access the different SubPages. In this case I used a wicket:child in my SuperPage. I can still navigate to SuperPage even if I am calling the class SuperPage directly. Then each link in SuperPage called my SubPage class, with only the extra component added by the SubPage. Hope this helps. But as Igor said you have to make SuperPage have the wicket:child in its markup. -Richard On Thu, Oct 23, 2008 at 3:37 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: just like in object inheritance your superpage would have to provide a way to plug this extra component in... -igor On Thu, Oct 23, 2008 at 1:30 PM, James Carman [EMAIL PROTECTED] wrote: Suppose I have this page hierarchy: BasePage - SuperPage - SubPage. In BasePage.html, I've got wicket:child and in SuperPage.html I've got wicket:extend. Now, in SubPage.html, I can't just override the markup of SuperPage.html by using a wicket:extend. Suppose I wanted to just add in an extra component in SubPage.html and then override the markup for SuperPage with the markup for SubPage, but still allowing myself to extend from BasePage. I can't do that! - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Page Markup Inheritance Problem...
I dont find it a bit wierd.. It just means that you've prepped the class for inheritance (by telling wicket that markup should be inserted where wicket:child are), so that if someone comes along latter and extends your component they are allowed todo so:) I actually think this is a very nice feature.. James Carman wrote: I would like to confirm to folks here that you can use a page that has a wicket:child element in it directly. You do not have to subclass it! I found that to be quite weird, but it was very helpful in our situation! On Thu, Oct 23, 2008 at 10:42 PM, Richard Paul [EMAIL PROTECTED] wrote: From the testing that I have done so far. Yes. This has been such an extra ordinary find for me. It is what I call a HOWZAT!!! wicket moment !! This is such a powerful feature. Hopefully someone can give us the official description of this concept. -Richard Paul Independent Contractor Chicago Area. On Thu, Oct 23, 2008 at 8:29 PM, James Carman [EMAIL PROTECTED] wrote: What if SuperPage is a page that is concrete? Can it display itself without having the wicket:child elements plugged in? On Thu, Oct 23, 2008 at 4:56 PM, Richard Paul [EMAIL PROTECTED] wrote: I ran into a similar situation last night. Not sure if this is what your looking for. BasePage - My Site Layout SuperPage - My Page Layout (e.g. a header area for what I am working with) SubPage - Actions ( e.g. forms for adding stuff etc.) When first navigating to SuperPage I only want to show links that the user needs to click on to access the different SubPages. In this case I used a wicket:child in my SuperPage. I can still navigate to SuperPage even if I am calling the class SuperPage directly. Then each link in SuperPage called my SubPage class, with only the extra component added by the SubPage. Hope this helps. But as Igor said you have to make SuperPage have the wicket:child in its markup. -Richard On Thu, Oct 23, 2008 at 3:37 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: just like in object inheritance your superpage would have to provide a way to plug this extra component in... -igor On Thu, Oct 23, 2008 at 1:30 PM, James Carman [EMAIL PROTECTED] wrote: Suppose I have this page hierarchy: BasePage - SuperPage - SubPage. In BasePage.html, I've got wicket:child and in SuperPage.html I've got wicket:extend. Now, in SubPage.html, I can't just override the markup of SuperPage.html by using a wicket:extend. Suppose I wanted to just add in an extra component in SubPage.html and then override the markup for SuperPage with the markup for SubPage, but still allowing myself to extend from BasePage. I can't do that! - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Page Markup Inheritance Problem...
In my mind, I think of wicket:child like an abstract method in an abstract superclass. That's why I find it a bit weird. On Wed, Oct 29, 2008 at 3:31 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: I dont find it a bit wierd.. It just means that you've prepped the class for inheritance (by telling wicket that markup should be inserted where wicket:child are), so that if someone comes along latter and extends your component they are allowed todo so:) I actually think this is a very nice feature.. James Carman wrote: I would like to confirm to folks here that you can use a page that has a wicket:child element in it directly. You do not have to subclass it! I found that to be quite weird, but it was very helpful in our situation! On Thu, Oct 23, 2008 at 10:42 PM, Richard Paul [EMAIL PROTECTED] wrote: From the testing that I have done so far. Yes. This has been such an extra ordinary find for me. It is what I call a HOWZAT!!! wicket moment !! This is such a powerful feature. Hopefully someone can give us the official description of this concept. -Richard Paul Independent Contractor Chicago Area. On Thu, Oct 23, 2008 at 8:29 PM, James Carman [EMAIL PROTECTED] wrote: What if SuperPage is a page that is concrete? Can it display itself without having the wicket:child elements plugged in? On Thu, Oct 23, 2008 at 4:56 PM, Richard Paul [EMAIL PROTECTED] wrote: I ran into a similar situation last night. Not sure if this is what your looking for. BasePage - My Site Layout SuperPage - My Page Layout (e.g. a header area for what I am working with) SubPage - Actions ( e.g. forms for adding stuff etc.) When first navigating to SuperPage I only want to show links that the user needs to click on to access the different SubPages. In this case I used a wicket:child in my SuperPage. I can still navigate to SuperPage even if I am calling the class SuperPage directly. Then each link in SuperPage called my SubPage class, with only the extra component added by the SubPage. Hope this helps. But as Igor said you have to make SuperPage have the wicket:child in its markup. -Richard On Thu, Oct 23, 2008 at 3:37 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: just like in object inheritance your superpage would have to provide a way to plug this extra component in... -igor On Thu, Oct 23, 2008 at 1:30 PM, James Carman [EMAIL PROTECTED] wrote: Suppose I have this page hierarchy: BasePage - SuperPage - SubPage. In BasePage.html, I've got wicket:child and in SuperPage.html I've got wicket:extend. Now, in SubPage.html, I can't just override the markup of SuperPage.html by using a wicket:extend. Suppose I wanted to just add in an extra component in SubPage.html and then override the markup for SuperPage with the markup for SubPage, but still allowing myself to extend from BasePage. I can't do that! - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - 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]
Re: Page Markup Inheritance Problem...
Ahh, and in my mind It just goes hand in hand with classes which are not final:) I guess different mindsets.. So my idea is that if you can extend something you place in wicket:child. and if not you leave it out. James Carman wrote: In my mind, I think of wicket:child like an abstract method in an abstract superclass. That's why I find it a bit weird. On Wed, Oct 29, 2008 at 3:31 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: I dont find it a bit wierd.. It just means that you've prepped the class for inheritance (by telling wicket that markup should be inserted where wicket:child are), so that if someone comes along latter and extends your component they are allowed todo so:) I actually think this is a very nice feature.. James Carman wrote: I would like to confirm to folks here that you can use a page that has a wicket:child element in it directly. You do not have to subclass it! I found that to be quite weird, but it was very helpful in our situation! On Thu, Oct 23, 2008 at 10:42 PM, Richard Paul [EMAIL PROTECTED] wrote: From the testing that I have done so far. Yes. This has been such an extra ordinary find for me. It is what I call a HOWZAT!!! wicket moment !! This is such a powerful feature. Hopefully someone can give us the official description of this concept. -Richard Paul Independent Contractor Chicago Area. On Thu, Oct 23, 2008 at 8:29 PM, James Carman [EMAIL PROTECTED] wrote: What if SuperPage is a page that is concrete? Can it display itself without having the wicket:child elements plugged in? On Thu, Oct 23, 2008 at 4:56 PM, Richard Paul [EMAIL PROTECTED] wrote: I ran into a similar situation last night. Not sure if this is what your looking for. BasePage - My Site Layout SuperPage - My Page Layout (e.g. a header area for what I am working with) SubPage - Actions ( e.g. forms for adding stuff etc.) When first navigating to SuperPage I only want to show links that the user needs to click on to access the different SubPages. In this case I used a wicket:child in my SuperPage. I can still navigate to SuperPage even if I am calling the class SuperPage directly. Then each link in SuperPage called my SubPage class, with only the extra component added by the SubPage. Hope this helps. But as Igor said you have to make SuperPage have the wicket:child in its markup. -Richard On Thu, Oct 23, 2008 at 3:37 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: just like in object inheritance your superpage would have to provide a way to plug this extra component in... -igor On Thu, Oct 23, 2008 at 1:30 PM, James Carman [EMAIL PROTECTED] wrote: Suppose I have this page hierarchy: BasePage - SuperPage - SubPage. In BasePage.html, I've got wicket:child and in SuperPage.html I've got wicket:extend. Now, in SubPage.html, I can't just override the markup of SuperPage.html by using a wicket:extend. Suppose I wanted to just add in an extra component in SubPage.html and then override the markup for SuperPage with the markup for SubPage, but still allowing myself to extend from BasePage. I can't do that! - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - 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] -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Page Markup Inheritance Problem...
just like in object inheritance your superpage would have to provide a way to plug this extra component in... -igor On Thu, Oct 23, 2008 at 1:30 PM, James Carman [EMAIL PROTECTED] wrote: Suppose I have this page hierarchy: BasePage - SuperPage - SubPage. In BasePage.html, I've got wicket:child and in SuperPage.html I've got wicket:extend. Now, in SubPage.html, I can't just override the markup of SuperPage.html by using a wicket:extend. Suppose I wanted to just add in an extra component in SubPage.html and then override the markup for SuperPage with the markup for SubPage, but still allowing myself to extend from BasePage. I can't do that! - 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]
