Re: Average number of code lines ina WOComponent, .java
Re: Average number of code lines ina WOComponent, .java
- Subject: Re: Average number of code lines ina WOComponent, .java
- From: Gustavo Pizano <email@hidden>
- Date: Fri, 10 Jul 2009 09:19:17 +0200
Well, so what I have is.
Main WOComponent, that has a Selectable div in the navigation bar (left part of the page) then in the right part it has an AjaxUpdateContianer which has inside another list with the data related to the slelectedItem form the navigation bar.
And on the bottom of the right part is the detailed information of the selectedValue2 that belongs to the 2nd list which is in the upper-right part of the page.
So what I think is divide the navigation bar which will contain the main List of items. then when selected the second list (the one in the upper-rigt) part of the page will get updated, (upper-right) list, which has more things inside, I think should be the seocnd component, - and beloow this one it shoudl be the Detail Component of the selectedValue2 form the 2nd list.
now.. when selecting somethng form the list, how will I tell the other components which have their own java files to get updated with the new values? thats why I tought after reading an old mail to use the parent().
G
On Thu, Jul 9, 2009 at 12:01 PM, Paul Hoadley <
email@hidden> wrote:
On 09/07/2009, at 6:09 PM, Gustavo Pizano wrote:
Hello, well with this app Im doing, I have just one main component with a "few" AjaxupdateContainers, I have realize then that the ,java its quite big, lots of bindings, I was thinking then in divide it in 3 components, a main one and 2 childre,
Sounds reasonable.
so then I can use somehow the parent() and get the valueForkey of some selection to UpdateThe container someting like that I dunno if you understand me.
You _probably_ don't need to do anything like that. Tell us more about the component you're trying to split up.
But I wish to know normally what you do guys, to see if its necesary to split this component into 3( which will give me a headache I know) or leave it as it is.
It shouldn't give you a headache. Tell us what you're trying to do. I split off sub-components all the time, especially if there's any chance they can be re-used. That's the whole point of the component architecture.
--
Paul.
w
http://logicsquad.net/ h
http://paul.hoadley.name/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden