Re: Caching CLIM generated menus?

• To: Scott McKay <swm@harlequin.com>
• Subject: Re: Caching CLIM generated menus?
• From: kanderso@BBN.COM
• Date: Thu, 02 Jun 94 12:37:42 -0400
• Cc: clarisse@iexist.att.com, clim@BBN.COM, bugs@franz.com
• In-Reply-To: Your message of Thu, 02 Jun 94 11:06:01 -0400. <27096.9406021506@tigris.harlequin.com>

  From: Scott McKay <swm@harlequin.com>
  Date: Thu, 2 Jun 94 11:06:01 EDT
  To: kanderso@BBN.COM
  Cc: clarisse@iexist.att.com, swm@harlequin.com, clim@BBN.COM, bugs@franz.com
  Subject: Caching CLIM generated menus? 
  
  ...

  The hash table would get enormous, and the amount of data each entry
  hangs on to is not exactly small.  I will try to come up with
  something an application can use on a case by case basis (where one
  "case" is a presentation-type X input context), but that's the best I
  can do.  In general, CLIM just can't do this automatically, it's just
  too expensive.
  
I think an application based approach would be good.  Also, a finite cache
might be good too, say only keeping the last few (10?) menus.


  ...

• Caching CLIM generated menus?
• From: Scott McKay <swm@harlequin.com>

• Prev: Caching CLIM generated menus?
• Next: to display bitmap, ps file, or gif file on CLIM
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)