SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 07 | August | 2003 ]

<< Previous Message << >> Next Message >>


Date: Thu, 7 Aug 2003 00:16:10 PDT7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Re: Warpstock 2003 Presentation

In <3F31F626.79AF@peterskye.com>, on 08/06/03
at 11:47 PM, Peter Skye said:

>capability supposed to be a part of the language definition? (Yes I know
>that such design tools just create tables which are interpreted at run
>time, but the method of implementation doesn't impact whether such a tool
>should be defined in the HLL.)

Actually, this may have been true at one time, but today most generate
code that is executed at run time. For typical examples this, see IBM's
Visual Builder for C++ and Java. If you study the implications of OO
style languages, you'll find they sort of force this implementation style.
THe GUI builder may have some sort of database description of the GUI
layout, but this is only used at design time.

>-- Suppose you're creating a typical match-merge program (read two sorted
>files and create a single sequenced file). Do you use PL/I-ish
>statements written in a text editor, or do you instead open a boilerplate
>match-merge template, import the file formats for the two source files,
>click on the fields to be matched, and let the PI do the rest?

The later is how the modern development tools work. Components can be
visual or non-visual. One just drops them on the workspace, draws lines
to hook up the interfaces and tells the tool to build code. Components
can be bought or built. Of course, you will want to position visual
components on the workspace. Non-visual components can be place whereever
convenient.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.37 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.org #scoug (Wed 7pm PST)
----------------------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 07 | August | 2003 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.