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

Re: Nested WOSwitchComponents


  • Subject: Re: Nested WOSwitchComponents
  • From: Guido Neitzer <email@hidden>
  • Date: Mon, 31 Aug 2009 14:19:06 -0700

Oh, now I get it.

Yeah, no, that's not what I thought it was. Sorry, my fault.

Guido

On Aug 31, 2009, at 2:15 PM, David Holt wrote:

Hi Guido,

Thanks for your response. Okay, so I would love to do that, but I don't see what to do with D2W.

My (limited) understanding is that you need a model for D2W to do its magic.

Are you saying that I can actually use D2W to

1. allow the user to build a form, then
2. display the form
3. allow the form to be used to capture data

I understand how D2W can be used to generate the form elements and order them. I also get how if I had a model ready to capture data D2W would be able to generate an interface that would be usable based on the model.

I just don't quite get how the two sides can be married (i.e. How do you create a form item and its associated data capture [also variable depending on the data type] using D2W). Do I just use yet one more nested WOSwitchComponent?

Can you shed any light?

Thanks,
David

On 31-Aug-09, at 2:03 PM, Guido Neitzer wrote:

I did this years ago until I found out that I was re-inventing the wheel. Switched to D2W at that point.

To answer your question: this works fine.

Guido

On Aug 31, 2009, at 1:32 PM, David Holt wrote:

Does anyone know whether I will run into difficulties trying to nest WOSwitchComponents?

I am building a form builder and I am thinking of structuring the page with a loop over elements (an element being text, horizontal rule, or form item). The switch component would be based on the type of element. If the element is a form item, then there would need to be an additional WOSwitchComponent inside the element's switch component that would be set according to the form item type. Has anyone had success building such a thing?

Thanks,

David_______________________________________________
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: 
 >Nested WOSwitchComponents (From: David Holt <email@hidden>)
 >Re: Nested WOSwitchComponents (From: David Holt <email@hidden>)

  • Prev by Date: Re: Nested WOSwitchComponents
  • Next by Date: weird sql generation problem
  • Previous by thread: Re: Nested WOSwitchComponents
  • Next by thread: weird sql generation problem
  • Index(es):
    • Date
    • Thread