RE: Re: Poll on using both WDSCi and ADTS

There have been major unresolved problems in CODE for years, including
issues with VERIFY and EVFCTCPD.EXE.  Even if CODE provided a cure for
cancer or was directing airplanes to fly into the CN Tower, I doubt it will
get another glance by IBM because it's not part of IBM's current "Stepford
wives"-like approach to ADT.  I like my milk homogenized, not my tools.   

In June 2001, I wrote a three-page letter to Buell Duncan (then iSeries GM)
alternately praising CODE and chastising IBM for its instability and lack of
support.  As a result of that executive contact, I spent a lot of time in
conference calls discussing, discussing, discussing, but nothing---not one
damn thing---was fixed.

Based on the useful life (if not the number of years until IBM releases
something new) of IBM ADT's (SEU, RLU :(, SDA), CODE has a long life ahead
of it...unless IBM kills it.  

While WDSCi has useful features, it's still a documentation-free product in
gamma test by customers.  CODE remains a much more useful tool to me (and
apparently to others also).  But I'm getting weary of diving into EVCACHE
and deleting entries so I can get programs to verify.  

I bleed blue-and-white stripes when cut.  However, to speak plainly, I'd
like to see some of the hot air holding WDSCi afloat used to blow some life
into CODE.  It's just a management decision and the stoke of a pen.

Frederick Brooks said, "Plan to throw one away."  IMHO, IBM's throwing the
*wrong one* away.

-reeve fritchman


> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-
> bounces@xxxxxxxxxxxx] On Behalf Of adrian
> Sent: Sunday, August 29, 2004 3:58 PM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: [WDSCI-L] Re: Poll on using both WDSCi and ADTS
> 
> Vern Hamberg wrote:
> 
> > OK, if I report this as a PMR, will it get fixed, or is CODE locked
> > down? I consider it a bug, not a feature.  ;-)
> 
> The CODE Editor is, so far as I know, in major-problems-only
> maintenance
> mode.  This particular restriction is there because of complex
> implementation details, which are quite impossible to tackle in the DBCS
> environment (among other)...
> 
> >>> BTW, another behavior that has always been a little irritating -
> >>> let's say that I have selected a few lines by dragging down while
> the
> >>> cursor is at the start of the lines. If I click on the line
> >>> immediately below the selection, and at the beginning of the line,
> >>> before the first character but not in the sequence number area, it
> >>> does not deselect - I need to click somewhere else.
> >>
> >> If the last line of the block is selected in its entirety, then most
> >> probably the cursor blinking at the start of the line that follows is
> >> actually the end point of the stream selection (you may verify this by
> >> entering, on the LPEX command line: block.bottomElement)...  Now
> >> clicking on that particular point (or even inside the SEU prefix area
> >> of that line) won't clear the selection.
> >
> > Kind of what I thought. Now I tried something - I clicked within the
> > selection and it cleared it - only when clicking at this location (at
> > the cursor when cursor is at end of selection) does it NOT clear the
> > selection. Same applies if the selection ends within a line.
> >
> > Seems odd to have this very specific exception. There are many times
> > I've needed this not to be how it works, usually when I've selected
> > something, then want to deselect right away, without having to move
> the
> > mouse or go to the keyboard.
> 
> The idea is to allow you to further extend the selection with the mouse.
>   Otherwise, you'll be forced to switch to Shift+arrow_key.
> 
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
> mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.