From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4263b4a969a750a X-Google-Attributes: gid103376,public From: jerry@jvdsys.nextjk.stuyts.nl (Jerry van Dijk) Subject: Re: Ada in control - Win32 GUI - Possible? Date: 1997/11/05 Message-ID: <878705737.72snx@jvdsys.nextjk.stuyts.nl>#1/1 X-Deja-AN: 287099804 Distribution: world References: <345F4B6A.7FDA@gsfc.nasa.gov> Organization: *JerryWare HQ*, Leiden, Holland Newsgroups: comp.lang.ada Date: 1997-11-05T00:00:00+00:00 List-Id: In article <345F4B6A.7FDA@gsfc.nasa.gov> Stephen.Leake@gsfc.nasa.gov writes: >Dave Smith wrote: >> >> >> >> Can an Ada program be in control of a Win32 GUI? >> >I'm not clear what you mean by "in control". The DLL has an init >procedure called when it is loaded; that does the Ada elaboration. Ada >finalization takes care of cleaning up. What more "control" do you need? As I understand the question: a) the main program is actually the middleware layer, in Ada, rebuild for W32 b) this main program, when ready, starts the client program in VB c) the client then wants to use the middleware layer functionality d) when the client finishes running, the middleware layer gets back control and finishes. e) due to well-known constrains, redesign is not feasible how to archieve this ? Unknown is whether there is just one client (and number of instances) or why (if there is 3 months time) the client isn't also written using Ada (possibly using an GUI builder). However, if I am correct in the above, the question has little to do with Ada. The real question is how to mold an existing application architecture to fit into the Win32 environment. Can this be done ? Yes, of course, in a lot of ways. How, that would depend on a lot of other parameters which are unknown to us. In general though I would suggest running the middleware layer as a invisible process, starting the client in the foreground. Communication by whichever means are most appropiate (lots of choices here). Client before going down informing the middleware, which will then also shutdown. Although, as Stephen suggested, running the middleware from a DLL is also possible, although feasebility would depend on its current design. However, there are probably a lot of -to us- unknown complexities and requirements here, so a specific answer would require a lot more info and study. Best advise, if my assumptions are correct, is to call in a application architect with Ada and Win32 experience. -- -- Jerry van Dijk | Leiden, Holland -- Consultant | Team Ada -- Ordina Finance | jdijk@acm.org