Re: accepting-values recursively

• To: Curt Eggemeyer <curt@eraserhead.jpl.nasa.gov>
• Subject: Re: accepting-values recursively
• From: kanderso@BBN.COM
• Date: Fri, 13 Mar 92 14:21:53 -0500
• Cc: clim@BBN.COM
• In-Reply-To: Your message of Fri, 13 Mar 92 09:52:12 -0800. <9203131752.AA05852@eraserhead.Jpl.Nasa.Gov>

  Date: Fri, 13 Mar 92 09:52:12 PST
  From: Curt Eggemeyer <curt@eraserhead.jpl.nasa.gov>
  To: clim@BBN.COM
  Subject: accepting-values recursively
  
  I'm hitting slow turnaround time in accepting-values with objects that can
  have over a thousand accepts for their parameters.  I can break them down
  by doing recursive calls to accepting-values.  This will require a bit of
  recoding on my part and before I try it I want to know if anybody has tried recursion on accepting-values.  If so, is there any special undocumented
  gotcha's that I will have to worry about?  Will I gain response speed by
  doing this way?  I'm thinking of implementing this beast in the following
  manner:

I don't think using ACCEPTING-VALUES recursively will help.  You should be
using query identifiers, of course.  The best way is to cut down on what
you present to the user.  For example, you might do

 (setq details? (accept 'boolean ...)
 ... accept the details.

This way the user can open and close portions of the dialog.

k

• accepting-values recursively
• From: Curt Eggemeyer <curt@eraserhead.jpl.nasa.gov>

• Prev: accepting-values recursively
• Next: CLIM 1.1 from Lucid
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)