Re: justifying RDi when WDSCi 'still works'

Sorry it took me a few days to post this response.

We haven't done the WDSC to RDi upgrade yet--we're still on V5R4. However,
a big selling point I plan to use is the WYSIWYG screen designer. IIRC,
the screen part is out of 'Technology preview--do not use for production
development' status. From what I understand, the print designer is now in
the Technology preview stage. So you've got the WYSIWYG designer. Then
there's also the Application Diagram function. I had RDi installed for
evaluation and it worked well--giving a view into the structure and flow
of programs and applications. At times, the insight that can provide is
priceless.

In response to Tommy's point about learning WDSC not being worthless: I
agree the learning is beneficial to using RDi. However support for WDSC
is going to stop. (That's only about 8 months away now.) If something
stops working, you have nothing and your investment in learning WDSC is of
no benefit unless you spring for the $$ to get RDi.

For those of us who've made the complete jump to using the Eclipse-based
tooling, going back to SEU would be a very painful and
productivity-draining affair.

My 2 cents worth.

Michael

wdsci-l-bounces@xxxxxxxxxxxx wrote on 08/21/2009 01:00:09 PM:

----- Message from "Dave Shaw" <daveshaw@xxxxxxxxxxxxx> on Fri, 21
Aug 2009 11:59:41 -0400 -----

To:

<wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] justifying RDi when WDSCi 'still works'

The few of us who use WDSCi here are trying to convince management that

we

should purchase a few licenses for RDi now that we've gone to V6R1. The

pushback we're getting is that WDSCi still works fine, so we need to

justify

spending the money. Has anyone else successfully done this, and if so,

what

approach did you use?

Thanks!

Dave Shaw
Mohawk Industries