Re: Long WOForms - Best Practices
Re: Long WOForms - Best Practices
- Subject: Re: Long WOForms - Best Practices
- From: Sacha Mallais <email@hidden>
- Date: Tue, 23 Aug 2005 11:58:11 -0700
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:
This email sent to email@hidden