|
----- Message from MichaelQuigley@xxxxxxxxxx on Mon, 24 Aug 2009 08:However,
49:17 -0400 -----
To:
wdsci-l@xxxxxxxxxxxx
Subject:
Re: [WDSCI-L] 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.
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 nowin
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 somethingof
stops working, you have nothing and your investment in learning WDSC is
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.