Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!forsight!jato!mars.jpl.nasa.gov!hashem
From: hashem@mars.jpl.nasa.gov (Basil Hashem)
Newsgroups: comp.windows.x
Subject: Shared Memory and Widgets
Keywords: shared memory, toolkit, widgets
Message-ID: <3988@jato.Jpl.Nasa.Gov>
Date: 11 Jun 90 17:21:54 GMT
Sender: news@jato.Jpl.Nasa.Gov
Reply-To: hashem@mars.jpl.nasa.gov (Basil Hashem)
Organization: Jet Propulsion Lab, La Canada, CA
Lines: 28

Dear xperts,

Any light you can shed on this topic would be most appreciated.  I am writing
a toolkit-based application which creates *thousands* of widgets over the
lifetime of the program.  This client will only create widgets and never
do an XtDestroyWidget().  It will simply XtUnmanageChildren() and then
re-XtManageChildren(), i.e. it will display only certain groups of widgets
at a time.

To complicate matters, I need approximately 12 instances of this program to
run simultaneously.  One quickly realizes the need and advantages of using a
shared memory architecture for this kind of application.

What I am trying to do is pre-allocate (create) all the needed widgets in the
shared memory segment, then, have each instance of the program attach to that
segment and instantiate by Managing and Realizing its own "copy" of the
widgets.

Has anyone written or have examples of using widgets under any shared memory
scheme?  I've tried writing some short programs without success.

Any help will be useful.

Thanks,
                "WOOOSH!  If they only knew what I was up to."
                                 Basil Hashem
                            hashem@mars.jpl.nasa.gov
            Jet Propulsion Laboratory     La Canada Flintridge, CA