|
midrange.com
You definitely should look at V5 first, because in V4 you essentially had
to use Code/400 for any kind of serious editing. In V5 probably the main
reason to use Code/400 would be if you already know it and still like it
better. There are a couple of wizards, like the convert to free format,
that still require Code/400. Other than that, the only definite time you
need to use it is when you want to use Code Designer. We all assume that
IBM intends to rewrite that in Java and make it a native editor in WDSC,
but I have not heard any definitive plans or time tables.
I think the best thing that any of us can do is document the things we do
on a daily basis that force us to leave WDSC and work in another tool,
such as Code/400. This sort of information could help IBM prioritze the
remaining work they have to do to "eliminate" the need for Code/400 and
those other tools.
Mark
"DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/02/2003 11:30 AM
Please respond to Websphere Development Studio Client for iSeries
To: "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
cc:
Subject: RE: [WDSCI-L] re: opening member
Mark,
<G> You got me.... V5--I haven't ordered it yet, cuz I want to order with
included service pack. I never heard if it's packaged with, now.......
Lets see, I still must use CODE for the Designer tool, all the neato stuff
like RPG to free conversion (that I've never been able to get to work,
btw)
and what-not. I agree, I'm mostly nit-picking, but my fears and concerns
are still justifiable, IMO. Just how much of what's in place will stay
and
how much will change? How many work-arounds must I learn, only to have to
re-train myself to NOT use the work-arounds once the problems are solved.
I
don't know about anyone else, but I really have to pick-and-choose what I
spend my personal time for learning new stuff. I have to learn that which
offers the most benefit for the time spent. How does learning a product
with features in transition help me? Nit, nit nit nit nit!
I want to use this stuff, I really do! I just resent the fact that I must
either wait til WDSCi is fully developed, or I must prolong the learning
curve.
Perhaps first I should look at V5......
Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863
-----Original Message-----
From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx]
Sent: Monday, June 02, 2003 10:09 AM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] re: opening member
Eric,
I assume we are talking about WDSC 5 and not 4.
Assuming that is the case, what is it about Code/400 that you feel you
have to learn? You do not need to use Code/400 at all in WDSC 5. The
only component you would possibly use is the Code Designer for WYSWIG
editing of DSPF and PRTF. This is pretty seamlessly integrated into WDSC
and for all we know it will never be migrated.
Mark
"DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/02/2003 10:53 AM
Please respond to Websphere Development Studio Client for iSeries
To: "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
cc:
Subject: RE: [WDSCI-L] re: opening member
Vern,
Just my view, but I am REALLY trying hard to NOT begin working too much
with
CODE/400, despite the limitations of RSE. I guess I feel that, since I
never developed a feel for Code, why would I want to learn it now, when
it's
about to be buried and forgotten. I get really frustrated with RSE
sometimes, just because it's still not rich enough to stand on it's own.
So
until it's fully developed, I have to make myself learn a product that's
scheduled for death???? I don't think so.....
To the development team: I like the goals that you've set for these
products, but the transtition from Code/400 to WDSCi is a real PITA. For
those that have long experience with CODE/400, there's no issue; they've
already made the investment in time to overcome the learning curve. They
can continue to use the parts of Code/400 that has the functionality they
need, learning the new tooling as it releases. Great! But for those of
us
that have no real expreience with the client based tooling, it seems (to
me,
anyway) that I'm wasting a lot of time and energy trying to learn this
stuff
during the transition. I guess I'm afraid I'll learn it now, only to have
to relearn it all over again each time a new release comes out and old
code/400 features are implemented in eclipse...
Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863
-----Original Message-----
From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, June 02, 2003 8:44 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] re: opening member
This is probably considered heretical, or at least ludditical, but if I
want to open a member I go Start->Run... and put in CODEEDIT. Then I go to
File->Open... from which I go to the top and put in a server name, a
library name, a file, and a member (or a wildcard spec). The list of open
specs is saved. The servers are listed on the left of the Open dialog. I t
will probably include those opened by RSE (R0xxxxx) if you get there from
RSE. Otherwise, you need to have run STRCODE.
Vern
At 09:18 AM 6/2/2003 -0400, you wrote:
>Another way to open a member without filter is from the iSeries Table
view.
>The Work with Members dropdown lets you specify a member directly. Once
>the member is in the table view, just double click it to open it in the
>editor. You can also do many other actions by using the right click to
>bring up the pop-up menu. For more information about the table view, see
>http://www.ignite400.org/html/News/news2003041403.htm
>
>Dave Cheng,
>905-413-4063 cheng@xxxxxxxxxx
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.
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.
