TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
"Richard L. Conn" <[log in to unmask]>
Reply To:
Richard L. Conn
Mon, 13 Sep 1999 10:05:50 -0400
text/plain (42 lines)
Hi, Wesley,

Responses interwoven below.

Richard Conn, ASE and PAL Manager

> -----Original Message-----
> From: Team Ada: Ada Advocacy Issues (83 & 95)
> [mailto:[log in to unmask]]On Behalf Of W. Wesley Groleau x4923
> Sent: Monday, September 13, 1999 9:00 AM
> To: [log in to unmask]
> Subject: Re: Two interesting approaches to job hunting and more
> > > And Visual Basic is a LOT easier ... my students all ran
> > >their first GUI-oriented programs with various degrees of bells and
> > >whistles after 1.5 hours of instruction and 1.5 hours of lab.
> >   Do your Ada students use GUI Builders or thick bindings, and
> > it still takes them more than 3 hours till first GUI program?
> > p.s. In original BASIC "PRINT 2+2" was *really* quick to learn.
> Maybe it's like every GUI builder I ever had to use:  You can get a very
> attractive interface almost immediately--but it takes a lot of editing of
> the unreadable autogenerated code to get anything useful.  (And if you're
> a perfectionist about having things line up horizontally or vertically,
> you have to hand-edit the pixel coordinates in the GUI intermediate
> files.)

Actually, it's quite different from that.  You never see the generated code.
The students' programs were running with only typing a line or two of
code, and that was it.  The VB IDE integrated everything for you.  All you
had to do was press the RUN button if you wanted to run it interpretively
in debug mode or select File/Make EXE if you wanted to compile it and
produce an executable.

It's worth looking at ... there is material on the new CDROM and my KSU