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 protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
