Motif Bindings

Motif Bindings

[Dan Olson]

Question 1: Are bindings available to build Motif interfaces?

Question 2: How are callbacks done without pointer to functions
            (assuming that bindings do exist)?



-- 
    UUCP: ..!uunet!bcstec!plato!dogfish!dano
Internet:  dano@dogfish.ds.boeing.com

Re: Motif Bindings

[cis.ohio-state.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!darwi]

dano@dogfish.boeing.com (Dan Olson) writes:

>Question 1: Are bindings available to build Motif interfaces?

>Question 2: How are callbacks done without pointer to functions
>            (assuming that bindings do exist)?


Answer to Question One:  Yes, there are bindings available.  The
STARS repository should have a copy of the Boeing bindings.  At 
AFIT we are using a commercial set of bindings that give full
X lib, Xt and Motif functionality.  The company that markets this set
of bindings is Systems Engineering Research Corporation.  The product
is called Ada/Motif.  There are other public domain and commercial
binding sets available beyond these.

Answer to Question Two:  Callbacks are registered by supplying the
address of the function.  

    Xt_Add_Callback( Target_Widget, Xm_N_activate_Callback,
		     Callback_Function'ADDRESS, Data'ADDRESS);

Note that the 'ADDRESS attribute does supply a pointer to the function.





Capt Karl Mathias                                  kmathias@afit.af.mil
Graduate Student, Air Force Institute of Technology
"Opinions expressed are my own and not those of the U.S. Air Force" 

Re: Motif Bindings

[Donn Hines]

In article LG5@plato.ds.boeing.com, dano@dogfish.boeing.com (Dan Olson) writes:
>Question 1: Are bindings available to build Motif interfaces?
>
>Question 2: How are callbacks done without pointer to functions
>            (assuming that bindings do exist)?
>
>
>
>-- 
>    UUCP: ..!uunet!bcstec!plato!dogfish!dano
>Internet:  dano@dogfish.ds.boeing.com



Hello,

Dan, email bounced, so I'm posting the recent responses I received on the subje
ct,
figuring it is of general enough interest to warrant a post.

>From serc@well.sf.ca.us Wed Apr 21 16:13:52 1993
Return-Path: <serc@well.sf.ca.us>
Received: from nkosi.well.sf.ca.us by paloverde.lanl.gov (4.1/SMI-4.1)
	id AA06601; Wed, 21 Apr 93 16:13:50 MDT
Received: from well.sf.ca.us by nkosi.well.sf.ca.us with SMTP id AA03245
  (5.65c/IDA-1.4.4 for <hines@paloverde.lanl.gov>); Wed, 21 Apr 1993 15:12:37 -
0700
Received: by well.sf.ca.us (5.65c/SMI-4.1/well-930413-1)
	id AA28864; Wed, 21 Apr 1993 15:12:25 -0700
Date: Wed, 21 Apr 1993 15:12:25 -0700
From: Systems Engineering Research Corporation <serc@well.sf.ca.us>
Message-Id: <199304212212.AA28864@well.sf.ca.us>
To: hines@paloverde.lanl.gov
Subject: Re: Ada and OSF/Motif
Newsgroups: comp.lang.ada
References: <C5Iw63.5Bv@speedy.cci.de> <1993Apr16.152029.18821@newshost.lanl.go
v>
Content-Length: 1193
X-Lines: 32
Status: RO

In comp.lang.ada you write:

>In article 5Bv@speedy.cci.de, peek@speedy.cci.de (Ruth Peek) writes:
>>
>>Ada and OSF/Motif
>>=================
>>
>>I am looking for an interface builder which supports the development of
>>OSF/Motif graphical user interfaces, written in Ada. I know the
>>product "ixbuild", but it produces C-code. Does anyone know about
>>interface builders which produce Ada code? Does anyone have experience
>>of using these interface builders?
>>
>	

>I too am interested in such! Pleas post if you have info.

>-donn hines     los alamos national laboratory

You should be aware of our products UIL/Ada and Ada/Motif which are a solid
and very standardized GUI development kit for Ada and which integrate with
most of the commercial GUI builder programs.  Contact me at any time for
details.

Best regards,
Richard N. Henault                Systems Engineering Research Corp.
                                  2555 East Charleston Road
                                  Mountain View, CA, USA 94043
                                  1-800-Ada-SERC (Voice CONUS)
                                  +415-962-8092 (Voice)
                                  +415-962-0330 (Fax)





>From widget!evb.com!debi@uunet.UU.NET Tue Apr 27 09:07:23 1993
Return-Path: <widget!evb.com!debi@uunet.UU.NET>
Received: from relay1.UU.NET by paloverde.lanl.gov (4.1/SMI-4.1)
	id AA08064; Tue, 27 Apr 93 09:07:21 MDT
Received: from spool.uu.net (via localhost.UU.NET) by relay1.UU.NET with SMTP 
	(5.61/UUNET-internet-primary) id AA25382; Tue, 27 Apr 93 11:06:12 -0400
Received: from widget.UUCP by spool.uu.net with UUCP/RMAIL
	(queueing-rmail) id 110423.17846; Tue, 27 Apr 1993 11:04:23 EDT
Received: from [192.9.3.8] by evb.com (4.1/SMI-4.1)
	id AA20529; Tue, 27 Apr 93 09:51:20 EDT
Message-Id: <9304271351.AA20529@evb.com>
Date: Tue, 27 Apr 1993 08:49:34 -0500
To: hines@paloverde.lanl.gov
From: debi@evb.com (Debrah Dunbar)
X-Sender: debi@192.9.3.2
Subject: Builder info.
Content-Length: 6662
X-Lines: 142
Status: RO


>Dear Mr. Hines,
>        EVB Software Engineering, Inc. markets a product called GRAMMI
>which is a graphical user interface builder that creates Ada code.  It uses
>motif compliant widget sets.  I've enclosed some data from a spec. sheet
>below, and would like to mail you some information and references on the
>product if you could provide me with your paper-mail address. 
>If you have any questions, please contact me at 301-695-6960.  My e-mail
>address is debi@evb.com
>
>Sincerely,
>
>Debra Dunbar
>Director of Sales and Marketing
>EVB Software Engineering, Inc.
>
>________________
>Technical Overview of GRAMMIT
>
>General Description
>
>GRAMMI (Generated Reusable Ada Modifiable Machine Interface) is an
>interactive interface construction tool for use with Ada programs. Written
>in Ada, GRAMMI uses the MIT X Window SystemT to produce graphical user
>interface software written in Ada with a Motif style. It employs a point
>and click construction style for specifying the appearance of an
>application screen. GRAMMI can be used both to prototype an application's
>user interface and to generate the implementing Ada source code for
>incorporation into the deliverable system.
>
>The usage paradigm for the construction of an application interface using
>GRAMMI involves a user (i.e., a software developer) interactively composing
>display screens employing elements from the GRAMMI Graphical Component 
>Library (GCL), tailoring them, and positioning them on the screen.
>Once a screen has been composed, it can itself be stored in the GCL,
>expanded into source code for use by the application, or both. The
>aggregate of software that GRAMMI supplies to an application is referred to
>as the user interface software. The combination of user interface software
>and application software is loaded into the target system, and the operator
>(i.e., the customer who uses the application) communicates with the
>application through the screens which were composed by the user.
>
>The major component of the GRAMMI system is the User Interface Editor (UIE)
>which is used to compose application screens interactively employing a
>powerful graphics editor. It provides access to the library of graphical
>components through standard palettes. The GCL objects may be screen objects
>or full screen descriptions. A screen object is the lowest level building
>block for composing a screen. It comprises a visual appearance as well as
>associated behavior. For example, a button is a screen object that might
>have a square appearance and will "depress" when clicked. Screen objects
>may also be composed using other screen objects and encapsulating their
>behavior within a single composite screen object.
>
>A screen description is an internal description that is utilized by the UIE
>to display and record a particular full screen image. The user constructs a
>display screen by interactively moving screen objects into the desired
>positions. Once satisfied with the appearance of a screen, the user may
>store a description of the screen back into the library. It may be recalled
>later for further updating or for use in other applications. Once a set of
>screens has been developed for an application, the Graphical Component 
>Interface Generator (GCIG) is used to convert a screen description or a set
>of screen descriptions into user interface software. The Applications
>Binder can then be used to combine this software with the application code
>to produce the target system software. The user interface software that is
>generated by GRAMMI and loaded into the target system is referred to as the
>GRAMMI Application Environment (GAE). The operator communicates with the
>application through the GAE.
>Additionally, the UIE may be extended by developing new objects (basic and
>composite) and installing them in the Graphical Component Library for use
>in composing screens. The GRAMMI system can thus be tailored for each new
>project.
>
>Benefits
>
>GRAMMI use results in reduced development time. By using a point and click
>construction style and composing screens at a higher conceptual level than
>hand coding, display screens can be built and modified far more easily.
>Other important benefits include:
>o       High level of Ada compatibility
>o       Fewer lines of source code to maintain
>o       Modification of screen attributes without recompiling
>o       Reusability
>o       Support for evolutionary prototypes
>o       Support for rapid prototyping
>o       Support for standard "look and feel" across multiple applications
>and           
>        systems
>o       User interface style enforcement
>
>Features
>o       The User Interface Editor provides:
>o       error message display area
>o       interactive window placement
>o       object palette for browsing available screen objects
>o       pallet objects and their ordering are user-editable
>o       pop-up attribute selection form for tailoring specific objects
>o       window and object duplication function
>o       Applications can utilize:
>o       automatic logging of errors
>o       automatic, overrideable exception handling
>o       fixed tiled window layout
>o       Motif Window manager
>o       Graphical components provided in the GCL  include:
>o       basic components such as:
>                label boxes     knobs
>                buttons pop-up menus
>                checkboxes      pull-down menus
>                dialog boxes    radio buttons
>                floating point fields   sliders
>                icons   text fields
>                integer fields  container fields
>o       composite components such as:
>                digital steps   graphical data plots
>                digital tuners  resource managers
>                forms   spectral display units
>                geographical maps       tables
>
>HOST Requirements
>GRAMMI is available for the following environments. It requires the
>indicated Ada compiler and operating system versions or later.
>        Hardware                Operating System        Compiler
>
>        Sun 4 (SPARC)           SunOS 4.1.1             Verdix 6.0
>        Silicon Graphics        IRIX 4.0                SGI Ada 3.1
>        HP 9000 Series 360/370  HP-UX                   HP/Alsys 4.3
>
>
>For further information, call 1-800-grammi-1
>
>GRAMMI is a trademark of ESL, Inc.  X Window System is a trademark of the
>Massachusetts Institute of Technology. HP-UX is a trademark of the Hewlett
>Packard Company.
>
>
>Debbie Dunbar                    
>Marketing/Sales Administration
>debi@evb.com

Debbie Dunbar                    
Marketing/Sales Administration
debi@evb.com

Re: Motif Bindings

[Joe Hildebrand]

> Question 1: Are bindings available to build Motif interfaces?

Yes.  Verdix sells them, and so does ICS.  We have used the ones
that Verdix sells, but they are buggy (note: we aren't using the
latest version, since we don't have SunAda 1.1).  With the ones
from ICS, you can use their BuilderXcessory, and have it generate
Ada code, using their bindings.  The Verdix bindings are based on
work done by AXI, and ICS's are based on SERC's bindings.  These
two schema are mutually incompatible, but mostly just in naming
conventions.  The AXI bindings are supposed to be "thinner", or
closer to the original C.  The SERC bindings are supposed to be
"thinner", or more Ada-like.
 

> Question 2: How are callbacks done without pointer to functions
>             (assuming that bindings do exist)?
In the AXI bindings, you just pass myfunction'address. 
Xt.AddCallback is expecting a System.address.


----------
Joe Hildebrand
hildjj@fuentez.com
Software Engineer
Fuentez Systems Concepts
(703)273-1447

Standard disclaimers apply

Motif bindings.

[Oren Amichay]

Hi,

I'm in urgent need for Public - Domain X/Motif binding in ada.
I'm working with Verdix (oops Rational...) Ada. So far I used some
ancient X-lib bindings form STAR, does anybody know of anything like
it for Motif ???

			Amichay.
-----------------------------------------------------------------------
Amichay Oren. Weizmann Institute of Science, Rehoovot, Tel-Aviv.
emal: amichay@wisdom.weizmann.ac.il, amichay@math.tau.ac.il
fax : 972-3-5469685
-----------------------------------------------------------------------

Re: Motif bindings.

[Bennett, Chip (KTR) ~U]

Oren Amichay <amichay@KALANIT.WEIZMANN.AC.IL> wrote:

> I'm in urgent need for Public - Domain X/Motif binding in ada.
> I'm working with Verdix (oops Rational...) Ada. So far I used some
> ancient X-lib bindings form STAR, does anybody know of anything like
> it for Motif ???

There is a document that might be of interest to you: The AdaIC's "Available
Ada Bindings".  This can be found on ajpo.sei.cmu.edu via anonymous ftp in
/public/dev-tool in either bindings.txt or bindings-ps.zip.  This document
has a section on X Window system bindings.  I only noticed one entry for
Motif that would be public domain, and it didn't look promising.  Hope this
helps.

*****************************************************************
* Chip Bennett, GDE Systems Inc | BennettC@j64.stratcom.af.mil  *
* USSTRATCOM/J64213             | Voice (402)294-7360           *
* 901 SAC Blvd, Suite 2B24      | FAX   (402)294-7912           *
* Offutt AFB, NE 68113-6600     | Opinions expressed are my own *
*****************************************************************