• 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: takeValueFromRequest phase
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: takeValueFromRequest phase


  • Subject: Re: takeValueFromRequest phase
  • From: Lachlan Deck <email@hidden>
  • Date: Wed, 1 Aug 2007 11:11:34 +1000

Hi again,

On 31/07/2007, at 4:20 PM, Chuck Hill wrote:

Nooooooooooooo. :-)

Believe me - it irked me doing it, but time for playing is not on my side at the moment... and the problem seems limited to that particular page (which is a relief) so later I'll be able to figure out what's different.


Maybe some more detail on what you are doing would help.
These are WOComponent subclasses?

Yes, the sub-component containing each checkbox is directly subclassing WOComponent. The parent page has a few more levels down to WOCompoonent. But I tested removing most of its hierarchy as well and that made no difference. So it must be something else I would think.
e.g.,
WOComponent
- ISHComponent utf8 encoding + building template() from custom dir if available.
- ISHNonSynchronizingComponent (synchronizesVariablesWithBindings:false stateless:false)
- WillowComponent (a number of convenience methods for current project's request + defining resetLocals() called from either sleep/ reset depending on whether we're stateless or not).
- SecurePage (validation holder)
- <Parent>Page (cover methods for particular controller based operations based on the iteration through a list of items against an outer loop.


(There's a few things that become redundant once wonder's in play)

Stateless? Stateful?

parent/child: stateful. However there's a few stateless components being used in the flow of things. e.g., validation containers, mini- detail components etc.


What else do they do?

Essentially this is the main checkout page. There's a set of items shortlisted (outer iteration), a set of objects iterated (inner loop) that the shortlisted items can be applied to via checkboxes plus options to add/remove etc. There's a conditional on whether the checkbox is shown, or if some text is shown instead because it's been previously assigned etc... or if there's no positions left.


with regards,
--

Lachlan Deck

_______________________________________________
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: 
 >takeValueFromRequest phase (From: Lachlan Deck <email@hidden>)
 >Re: takeValueFromRequest phase (From: Chuck Hill <email@hidden>)
 >Re: takeValueFromRequest phase (From: Lachlan Deck <email@hidden>)
 >Re: takeValueFromRequest phase (From: Chuck Hill <email@hidden>)
 >Re: takeValueFromRequest phase (From: Lachlan Deck <email@hidden>)
 >Re: takeValueFromRequest phase (From: Chuck Hill <email@hidden>)
 >Re: takeValueFromRequest phase (From: Lachlan Deck <email@hidden>)
 >Re: takeValueFromRequest phase (From: Chuck Hill <email@hidden>)

  • Prev by Date: Concurrency question
  • Next by Date: Re: excludeObjectFromPropertyWithKey weird error
  • Previous by thread: Re: takeValueFromRequest phase
  • Next by thread: Re: takeValueFromRequest phase
  • Index(es):
    • Date
    • Thread