| using wave widgets...motif and wave [message #803] |
Mon, 17 May 1993 15:17  |
Gary Leydon
Messages: 1
Registered: May 1993
|
Junior Member |
|
|
Hi,
I'm playing around with wave widgets on a VMS 5.5 system and pvwave
cl version 4.01. I'm wondering if using the Wt toolbox and/or wave
widget toolbox
is worth the effort. Has anyone done much with this and care to share
your
opinions? I'm beginning to think I should be going the other way...e.g
call wave
cl from my c program which handles all the motif stuff...that way I get
access to
all the motif convience routines not just the widgets. I'd like to see
some example code that would show how you tell wave (from a c program
using motif) to handle the drawing and updating from say a drawing area
widget.
thanks for any input
Gary Leydon
Bitnet Leydon@yalemed
Internet Leydon%bruce.decnet@venus.ycc.yale.edu
|
|
|
|
| Re: using wave widgets...motif and wave [message #1050 is a reply to message #803] |
Tue, 18 May 1993 02:01  |
glenn
Messages: 5
Registered: May 1993
|
Junior Member |
|
|
In article 20476@news.yale.edu, Gary Leydon <Leydon%Bruce@Venus.Ycc.Yale.Edu> writes:
> Hi,
> I'm playing around with wave widgets on a VMS 5.5 system and pvwave
> cl version 4.01. I'm wondering if using the Wt toolbox and/or wave
> widget toolbox
> is worth the effort. Has anyone done much with this and care to share
> your
> opinions? I'm beginning to think I should be going the other way...e.g
> call wave
> cl from my c program which handles all the motif stuff...that way I get
> access to
> all the motif convience routines not just the widgets.
I using the pv-wave widgets now to build a visualisation program and have
spent a fair amount of time learning how to use the wave widgets set and
wondering whether I shouldn't use our GUI builder (DevGuide in this case)
to write the code and then call wave from C. I've not used the Wt widgets
only the WaveWidgets toolbox. I've not yet found a case where I need a new
widget. However, I have had problems setting some attributes (for OpenLook)
like the colour of items. I have also found it awkward to position the
widgets exactly where I want them without lots of fiddling around. This is
of course something you take for granted with a GUI builder, taking no
time at all.
Having said that, once you get used to the style of working with the widgets
(which takes some time if you used to working with a GUI builder), programming
is quite quick. I've stayed with WaveWidgets because (a) I wasn't sure how
easy 2 way interaction was going to be between C and wave and I couldn't afford
the time to find out (b) my application will be distributed to other sites
with different hardware making a mixed C/wave environment less attractive
(c) I get nervous of mixed language programs(! 8-)
If I was starting again, for a smallish application, I'd stick with the
WaveWidgets. For a large application (assuming the C/wave interface did everything
I wanted), I use a GUI builder because I think it would be quicker and
much more flexible. I'd be interested to hear what others have to think
though.
---
------------------------------------------------------------ ------------
Dr Glenn Carver Email: glenn@atm.ch.cam.ac.uk
Centre for Atmospheric Science Phone: (44-223) 336521
Chemistry Department Fax : (44-223) 336362
Cambridge University
UK
------------------------------------------------------------ ------------
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
