Caching CLIM generated menus?

• To: kanderso@BBN.COM
• Subject: Caching CLIM generated menus?
• From: Scott McKay <swm@harlequin.com>
• Date: Thu, 2 Jun 94 14:09:54 EDT
• Cc: swm@harlequin.com, clarisse@iexist.att.com, clim@BBN.COM, bugs@franz.com
• In-Reply-To: kanderso@BBN.COM's message of Thu, 02 Jun 94 12:37:42 -0400 <11801.199406021717@hilly.harlequin.com>

   Date: Thu, 02 Jun 94 12:37:42 -0400
   From: kanderso@BBN.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.

I just started prototyping this.  I was, unfortunately, more correct
about my "CLIM can't just do this..." claim than I would like.
There's still good stuff we can do, but it will have limitations.

• Prev: to display bitmap, ps file, or gif file on CLIM
• Next: tracking current command
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)