|
I was just getting frustrated with the ILE support in RDi myself :-)
If you want a true dependency build, you have that in RTC or ARCAD
Or in i Projects you can make the equivalent of a makefile that manages
these.
But I agree that there should be better tooling support to set up the
initial build.
I was thinking of a split editor on the CL to build the CRTPGM command,
where you could drag in the modules and service programs you want to have
as input.
Of course you could build a binder source this way as well.
I would like some ideas just on how people would like to see the user
interface work for all of these things.
Of course I can't commit to doing this at any specific time schedule, but I
would to hear some brainstorming of how this should work.
Regards,
Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i
Phone: 1-905-413-3125 | Home: 1-905-854-6195 IBM
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: LinkedIn: Canada
http://ca.linkedin.com/in/edmundreinhardt/
From: "Mark Murphy/STAR BASE Consulting Inc."
<mmurphy@xxxxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>,
Date: 31/03/2014 03:33 PM
Subject: [WDSCI-L] From My Wish List
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
I really like the idea of an IDE. It should do all the keeping track of
things for me. It should help me with my builds, it should make debugging
easier for me, and RDI does a lot of that very nicely. But one place where
it falls short is in helping with ILE builds. I shouldn't have to remember
what modules are used to build which service programs. I shouldn't even
have to manage binder source, the IDE should be able to do that for me.
Maybe I am missing something, but this sort of build support should be a
minimum level of support. I was talking to a colleague about ILE, and he
told me that he hasn't done ILE because it is too hard. To hard in that
there are too many moving parts, and no tools that know how to manage them.
If I am missing something, please let me know, but I just don't see it in
RDi. I was hoping that an I Project would be the ticket, but not really. It
lets you write a biding program, but that is not the tool doing the work.
What would be nice is to be able to define a service program in some sort
of meta data. A dialog would let me attach modules to the service program,
and then tell which procedures were exported. It would also allow me to
attach binding directories, and work with the binding directory entries. It
would be smart enough to know whether to create or update the service
program based on source dates, and whether or not I have added a new
module. And I would simply have to tell RDI to build the service program,
and it would do it all correctly. That includes recompiling the sources
that have changed, and updating or replacing the service program.
Generating the appropriate binder source with a static signature.
Disallowing moving or removal of exports if at all possible, or making it
painful to do so because that would require a rebind of all dependent
programs and service programs. It would be nice though if RDi could handle
that though as well, automatically.
Now I realize that some of you are pretty sophisticated with ILE objects,
and have processes and procedures in place to handle them for you, but
don't you think that this is really the job of the IDE? This isn't Notepad,
or even SEU.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.