Re: websphere udate for 6.0.0.1

Buck;

It's slower for me than pdm probably because I've used it since around 89, 
when the iseris came out.  I get around it well since I use the mouse to 
move my cursor, or the tab, whichever is the proper tool at the time.
Color coding doesn't ring my bell, not anything I would ever use anyway.
I still haven't made it split the screen so I can see the same source in 
two views.  Probably don't have all the updates for 6.0.0.1
Haven't attempted to do anything "wild" like use the debugger.
I see on this forum, lots of people struggling with something that's 
supposedly been a working product for years.
Frankley, with the projects I currently have, I need to use green for now.

Appreciate your thoughts.


Darrell Lee
Information Technology
Extension 7127



Buck <kc2hiz@xxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
03/23/2007 12:38 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
wdsci-l@xxxxxxxxxxxx
cc

Subject
Re: [WDSCI-L] websphere udate for 6.0.0.1

I'm trying to force myself to use wdsc, but 
it's a really slowdown in production when
you only know how to enter and compile the
code, and don't know how to test it.

How is using WDSC for editing and compiling slower than using PDM for you?

I always end up back at the green screen 
for most of the real work.

Me too.  There's no reasonable way to use a GUI to test a 5250 green 
screen application.  And I don't mean that the IBMers can't figure it 
out, I mean how can you do 5250 emulation without emulating a 5250? :-)

At the moment, I'm not getting any 
of the joy you all are professing.

I myself don't get a big thrill out of the colour coding and I've only 
started to use the outline view.  The big thing for me is being able to 
see lots of lines of code on the screen, the ability to use regexes for 
searching, reasonable tab stops and bookmarks.

I personally got much better with a GUI editor when I stopped trying to 
make Brief act like SEU with a GUI accent.  The lesson being that in 
order to use LPEX, I have to edit the LPEX way.  I have been using GUI 
editors since the early 90s, so my experience is a bit different from 
some, but I find it noticeably slower to edit with SEU than LPEX just 
because of the time it takes to move the cursor around the code.
   --buck