• 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: Long WOForms - Best Practices
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Long WOForms - Best Practices


  • Subject: Re: Long WOForms - Best Practices
  • From: Kieran Kelleher <email@hidden>
  • Date: Tue, 23 Aug 2005 20:08:30 -0400

David,

A quick short-term fix might be to break up the 400 attributes across, say 10 or less, reusable subcomponents with 40 or more attributes each.

Then you just drop the 10 reusables onto the final page and bind the entity to it's API..... plus you can edit the subcomponents without WOBuilder throwing a fit. If the attributes are all in one tabular format, you can put the table tags in the outer wrapper page and just put tables with the same number of columns in the subcomponents and select the table tags in each subcomponent, make them dynamic, and set the omitTags binding to true. Thus the page-generated HTML will all be one table.

Regards, Kieran

On Aug 23, 2005, at 2:58 PM, Sacha Mallais wrote:

On Aug 23, 2005, at 11:42 AM, David Holt wrote:

Hey all,

I have a survey entity with 400 attributes. It has all manner of inputs including checkboxes, radiobuttons, text areas/fields, etc. Currently it is in one component. Up until now I have used the WOTabPanel to give the illusion of pages, but I am discovering a practical limit to the number of elements WOBuilder can handle before spinning the pizza wheel on every click on the interface. It deploys fine, it is just that the edits take forever. I finally had to resort to hand coding my .wod out of necessity!

Is there a better way to go?

Many, many better ways. I would strongly suggest you start with refactoring your 400 attribute entity. Then, look into the WOSwitchComponent, which will allow you to have different WO components displayed into the same page, possibly even using a tab panel paradigm, but without 400 form controls on one page. You could also go with a wizard paradigm, which naturally leads to separate WO components for each page.


I'm sure other's on the list will have their faves...


sacha


-- Sacha Michel Mallais -- President / Senior Developer
Global Village Consulting Inc. http://www.global-village.net/
Hi! I'm a signature virus. Copy me into your sig file and help me spread!




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


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: 
 >Long WOForms - Best Practices (From: David Holt <email@hidden>)
 >Re: Long WOForms - Best Practices (From: Sacha Mallais <email@hidden>)

  • Prev by Date: Force Display Group to refetch, not consistent ??
  • Next by Date: Re: Force Display Group to refetch, not consistent ??
  • Previous by thread: Re: Long WOForms - Best Practices
  • Next by thread: String Encodings
  • Index(es):
    • Date
    • Thread