|
IMO, there will always be cases where green screen will always be faster
for quickie changes and recompiles.
I still haven't seen WDSC run on a hand held device, but I have seen
someone modify and recompile a program using the keyboard of a Treo.
And CHAIN will always be faster than SQL for single record access.
--
Paul Nelson
Arbor Solutions, Inc.
708-670-6978 Cell
pnelson@xxxxxxxxxx
-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
From: "albartell" <albartell@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 12/15/2006 02:36PM
Subject: RE: Saving the System i: Fight Rather Than Switch
Just so everybody knows where I stand, I have been using WDSC since the
4.0
days. I ONLY use SEU if a clients machine just won't work with WDSC.
Note that I stated I compiled my programs by doing an F9 and ENTER
meaning I
typed it in on the command line and was not using PDM.
After using WDSC for many years I have gained perspective that doesn't
have
candy coating on it (or at least not nearly as much). I can leverage
and
justify it in my daily programming. I know certain features that aren't
up
to par for quick app development, and that often times heads me back to
the
command line.
I would like to know where Trevor was going with his statements because
it
seems he is still in the candy coated phase of thinking WDSC should ONLY
be
used in ALL cases.
Aaron Bartell
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of pnelson@xxxxxxxxxx
Sent: Friday, December 15, 2006 1:22 PM
To: Midrange Systems Technical Discussion
Subject: RE: Saving the System i: Fight Rather Than Switch
FWIW, Aaron, I saw Joe Pluta do a seminar on WDSC 10 days ago, and I
am
now convinced that WDSC is a better tool than PDM and SEU.
I'm waiting for my Christmas bonus to go buy a PC with more horsepower
to
run WDSC.
--
Paul Nelson
Arbor Solutions, Inc.
708-670-6978 Cell
pnelson@xxxxxxxxxx
-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
From: "albartell" <albartell@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 12/15/2006 01:49PM
Subject: RE: Saving the System i: Fight Rather Than Switch
>If you are still coding in "edit, compile, run, fail, debug, edit,
compile,
run, fail, debug, edit, compile" mode, then it would seem you are
using
WDSc
as you did with PDM - this is not a true Integrated Development
Environment.
Please humor me so I can update my coding style. How do you develop
RPG
programs using WDSC, Trevor? If there are better ways to do what I
am
doing
then I will happily change! Note that "better" in that previous
sentence
means time savings because in the end that is what I look for out of
WDSC.
There is enough time savings with the good things that it outweighs
the
bad
things.
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Trevor Perry
Sent: Friday, December 15, 2006 12:33 PM
To: Midrange Systems Technical Discussion
Subject: Re: Saving the System i: Fight Rather Than Switch
Aaron,
If you are still coding in "edit, compile, run, fail, debug, edit,
compile,
run, fail, debug, edit, compile" mode, then it would seem you are
using
WDSc
as you did with PDM - this is not a true Integrated Development
Environment.
In that case, you ~would~ expect CTRL+S to save your member to the
System i
- not to the PC where you are doing the actual development work.
Given that, I would have missed the point. WDSc is just a fancier
version of
PDM...
Of course, some of us stick to the "compile, now it works"
approach...
:-)
Trevor
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.