Path: news.cs.au.dk!noatun.mjolner.dk!mail-to-news
From: Flemming Gram Christensen <gram@mjolner.dk>
Newsgroups: comp.lang.beta
Subject: Re: More GUI
Date: Tue, 7 Nov 2000 17:40:41 +0100
Organization: Posted to comp.lang.beta by a mailtonews script
Lines: 97
Sender: lbr@mjolner.dk
Approved: mailtonews@cs.au.dk
Message-ID: <8u9g1u$63dui$1@gjallar.cs.au.dk>
References: <3A083686.C03A34DE@skynet.be>
NNTP-Posting-Host: bifrost.mjolner.dk
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: gjallar.cs.au.dk 973620094 6404050 130.225.8.27 (7 Nov 2000 18:01:34 GMT)
X-Complaints-To: usenet@cs.au.dk
NNTP-Posting-Date: Tue, 7 Nov 2000 18:01:34 +0000 (UTC)
Mailing-List: contact usergroup-help@mjolner.dk; run by ezmlm
X-No-Archive: yes
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3A083686.C03A34DE@skynet.be>; from trollet@skynet.be on Tue, Nov 07, 2000 at 06:06:14PM +0100
X-Original-Message-ID: <20001107174041.C19335@mjolner.dk>
Xref: news.cs.au.dk comp.lang.beta:12635

On Tue, Nov 07, 2000 at 06:06:14PM +0100, Atle wrote:
> First of all, thanks for GUIding me in the right direction :-)
> 
> Now, I have done as you said, defined a
> 
> SymptomWindow : window(# .. #);
> DiagnosisWindow : window(# .. #);
> 
> in symptoms.bet and diagnosis.bet, respectively.
> 
> In acubase.bet, it looks like this:
> 
> GIUenv
> (#
> 	Sympt : @SymptomsWindow;
> 	Diag  : @DiagnosisWindow;
> 	...
> 
> 	Sympt.Open; (* This is where it starts *)
> #)
> 
> Now, the Diag.Open should really first occur when the user asks for a diagnosis.
> I can open the window from acubase.bet to give access to 'diagnosis-related'
> stuff ('Generate Diagnosis' PushButton, or something) ...
> 
> .. but I wonder about alternatives: Semantically, doesn't this belong to the top-level pattern?
> Shouldn't Sympt pass up anything that is not directly related to selecting symptoms?
> And therefore, the decision to 'Generate Diagnosis' should be taken in acubase.bet?

Yes, I think it should.

> 
> Of course, it will work either way, but this being a 'case study' :-)

Please allways do things like that. (not only in gui programs)

Here is an example:

SymptomWindow : window
(# 
   (* will be called when user presses 'Generate Diagnosis' PushButton, or something) *)
   openDiagnosticsWindow:<Object;

   ...

   pb:@pushbutton
   (# 
     eventhandler::
      (#
        onMouseUp::(# do (* call the virtual callback *)
                         openDiagnosticsWindow
                   #)
      #);
   #);
#);


So, when the user presses the pushbutton, the openDiagnosticsWindow will be called.

This virtual can be further bound in the main program where you instantiate the 
SymptomWindow. Like this:

GUIenv
(#
	Sympt : @SymptomsWindow
	      (# openDiagnosticsWindow::<
                 (#  
		 do  (* some code to set up current diagnostics *)
                      Diag.show;
                 #)
               #);
	Diag  : @DiagnosisWindow;
	...

	Sympt.Open; (* This is where it starts *)
#)

This way the two windows functionality can be separated

Regards
Flemming



> 
> Thanks, Atle
> 

-- 
Flemming Gram Christensen, M.Sc., Software Engineer, Mjølner Informatics
------------------------------------------------------------------------
Mjolner Informatics A/S                   Phone:  +45 70 27 43 43       
Science Park Aarhus                       Fax:    +45 70 27 43 44
Gustav Wieds Vej 10                                             
DK-8000 Aarhus C                                                     
Denmark                                   E-mail: gram@mjolner.dk    
------------------------------------------------------------------------