• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Average number of code lines ina WOComponent, .java
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Average number of code lines ina WOComponent, .java


  • Subject: Re: Average number of code lines ina WOComponent, .java
  • From: Kieran Kelleher <email@hidden>
  • Date: Thu, 9 Jul 2009 08:09:19 -0400

Hi Gustavo, I was thinking part of your question might allude to this: A parent can have an AjaxUpdateContainer named Foo for example and a subcomponent can just use the javascript 'FooUpdate()' or simply bind 'Foo' to the updateContainerID of an AjaxUpdateLink in the subcomponent. The fact that the AjaxUpdateContainer and the AjaxUpdateLink are in separate or nested WOComponents makes no difference since thay are on the same page on the client side.

HTH, (Hope That Helps)

Kieran

On Jul 9, 2009, at 6:01 AM, Paul Hoadley 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

_______________________________________________ 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
References: 
 >Average number of code lines ina WOComponent, .java (From: Gustavo Pizano <email@hidden>)
 >Re: Average number of code lines ina WOComponent, .java (From: Paul Hoadley <email@hidden>)

  • Prev by Date: Re: Average number of code lines ina WOComponent, .java
  • Next by Date: Re: WO Deployment [was:A WebObjects article on Appleinsider]
  • Previous by thread: Re: Average number of code lines ina WOComponent, .java
  • Next by thread: Re: Average number of code lines ina WOComponent, .java
  • Index(es):
    • Date
    • Thread