Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!sun-barr!newstop!jethro!looney!toone
From: toone@looney.Corp.Sun.COM (Nolan Toone)
Newsgroups: comp.windows.open-look
Subject: Re:  HELP! I need tool to make tools
Message-ID: <4404@jethro.Corp.Sun.COM>
Date: 16 Jun 91 00:51:40 GMT
Sender: news@jethro.Corp.Sun.COM
Reply-To: toone@looney.Corp.Sun.COM
Organization: Sun Microsystems
Lines: 31

Well, I am nobody official but let me clear up a few things.

 writes:
> 
> uunet!ECE.UCSD.EDU!dlou (Dennis Lou) writes:
> > Is there a tool that helps me make tools by dragging and dropping?
>
> and spit out C to be modified.  This general way of working falls apart
> when you later want to modify the user interface after heavily 
> modifying the original  code templates.  (Note I'm not saying GUIDE is
> any better or worse than the dozen or so other paint-the-screen-and-spit-
> out-a-template programs.)  If GUIDE doesn't come with Open Windows, I 
> think it is less than $300.

As mentioned in a previous followup Devguide produces a *.G file which
gxv parses and creates a *_ui.c and *_stubs.c files (along with a couple of
others). the *_ui.c file SHOULD NOT BE TOUCHED. The *_stubs.c file 
however is exactly that. It contains the calbacks(stubs) and the main routines
that you do want to edit. Then when you want to change your interface
you rerun guide then INSTEAD of useing gxv use gxv_merge (I am not
sure if it is documented or supported but it work fine and I believe in
the next release it will be built into gxv). gxv_merge redoes the files
and merges your changes back into them.

> 
> Sun's support of OLIT doesn't extend to devGUIDE, even though
> there seems to be no technical reason.  

As for this issue  . . . . .    who knows what the future may hold. ;-)

Nolan Toone