Re: [WDSCI-L] RE: WSSDa feedback

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Vernon,

You might want to consider training.  When we instituted code/400 around
here we hired Jon Paris to come on site for a few days to do training. And
maybe, after the new editor starts going full swing we might have a
refresher.

I wonder if IBM training (?Bob Slaney?) has training videos available on
the new editor.  Or if the people at ATS,  http://www.ibmuser.com have
training materials?

This might be an excellent topic for our user group.  I wonder who would
talk, and when would be a good time for the speaker, now, or later after
the new editor starts humming?

Actually, tomorrow I have a company coming on site to look at Code.  We
don't make a dime off of that.  We just do it as contributing to the
industry.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Vernon Hamberg <vhamberg@attbi.com>
Sent by: wdsci-l-admin@midrange.com
08/17/2002 10:04 PM
Please respond to wdsci-l


        To:     wdsci-l@midrange.com
        cc:
        Fax to:
        Subject:        Re: [WDSCI-L] RE: WSSDa feedback


Phil

Some more thoughts, if you please:

I'm a dyed-in-the-wool PDM user. I liked VA C++'s ability to precompile,
too. Nobody in his right mind would use it for editing, when other things
were so much easier, IMO. (Like TextPad or CodeWright, e.g.)

I have found that getting into using CODE400 does not have an obvious
path.
I installed WDSC, and when I ran CODE400 and tried to open a member, I
just
did not get how to change libraries or servers or I don't know what in
that
window.

I __really__ need a simple, uncomplicated way to go from PDM to even
CODE400, much less WDSC. The QuickStart for WDSC does not even talk about
ADTS stuff much.

There's an audience out here of green-screen developers that want to use
these things. There's another of us that don't know how much it'd help us,
and we are wary.

However, when you seem to start from attracting Windows developers (that
_is_one of the goals, right?), non-400 types, web developers,and don't
give
us much of a roadmap - and a bumpy one at that - it just doesn't help me.

I expect to start an application and be able to move around the menu
options and figure out what it's about. I've not been able to do this with
these things. There's presumably a lot of power in things like filters,
but
they have, if I remember, layers you have to get through to get what you
want. It's felt messy.

I've probably just got used to it, but the Visual Studio interface makes
sense, generally.

I wish some of these comments were more specific - it's been a few days
and
weeks since I looked at this thing again. The thing I want most is a
_straihgtforward- roadmap. You've heard about the confusion in place right
now. Let us have just a couple things - like installing only CODE. Some of
us just don't need VA Java and all the web stuff - yet.

Thanks

Vern

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l
or email: WDSCI-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.