[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
Re: SQR Workbench
- Subject: Re: SQR Workbench
- From: james rader <raderj@INTELSAT.INT>
- Date: Thu, 14 Mar 1996 08:20:00 -0500
- In-Reply-To: <E08E853001A91800>
- Organization: INTELSAT
Mara,
At INTELSAT our developers routinely develop SQR programs on our Windows
boxes and then FTP them to the UNIX boxes for execution. Beyond the fact
that this gives us such benefits of client server development as:
- Use of cheap boxes to develop
- Isolation of developing code from production
- Ability of developers to tailor their environments to fit their own
personnal quirks, etc
the Workbench environment provides a nifty windowing paradigm for our work.
We can see source, results, and errors all in a unified world. (I know UNIX
people are used to a lot of this but in the restrictive Microsoft Windows
3.1 world this is great.) The flip side for on-UNIX development is, how do
you explain cluttering up the process table and burning all those resources
to your system administrator? On a PC, we don't care.
The bottom line is that our gang always have a choice, vi or on-PC with
ReportMate and they've crossed over heavily to ReportMate. N.B. Even for top
programmers, ReportMate is great for generating quick-starts on development
jobs.
If you want to persue this further I am: Jim Rader
Internet Email: james.rader@intelsat.int
-------------
Original Text
>From MLWELLS@SMTPGATE (Mara L. Wells)
{mlwells%IX.NETCOM.COM.@intelsat1.intelsat.int}, on 13/3/96 9:16 PM:
To: SQR-USER@SMTPGATE (Multiple recipients of list SQR-USERS)
{SQR-USERS@USA.NET}
-- [ From: Mara L. Wells * EMC.Ver #2.5.02 ] --
The client I am currently working for is considering acquiring SQR Workbench
for the SQR report developers. Sometimes GUI front ends are more cumbersome
than those that use the command line as the interface. How does workbench
development compare with UNIX vi development?
All comments welcome.
Mara Wells
Senior Consultant
REALOGIC, Inc.