Re: From My Wish List -- WDSCI-L

Hello everyone. I understand your frustration...A long time ago I added a couple of RFEs related to this, please check them out and vote:

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=28027

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=29405

And given that these requirements haven't seen the light, I started to write a plugin for this purpose. I'm creating a view in Rdi with a tree. This tree will represent the structure of the application in terms of modules, service programs, and programs. the programmer can add new components and relate them with source members. The plugin will generate and Ant script that can be executed from Rdi constructing the whole application. I just started this week, so most of the hard work is not done, if I manage to finish it, I'll gladly share it with you guys

My motivation for this is that I just had enough of writting cl for compiling for each of my Rpg projects!

Isaac Ramírez Herrera

El 31/03/2014, a las 15:53, Buck Calabro <kc2hiz@xxxxxxxxx> escribió:

On 3/31/2014 4:57 PM, Edmund Reinhardt wrote:

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.

I vote for Maven. Specifically, a Maven that's IBM i-aware, and can
tell that these 3 modules make up that service program and that this
module was compiled from that source member. It seems to me that the
strength of basing RDi on Eclipse is the ability to leverage the Eclipse
ecosystem. I'm not a Java developer, but it seems easier to me to write
a Maven plugin that's IBM i-aware than it is to write a whole new,
unique thing. Plus, any time we midrange programmers get to have a
shared development experience with the Java and C++ programmers, it's a
good thing. In my dreams, I use Maven and Mylyn alongside RPGUnit to
build and test functions, modules, programs and service programs
incrementally. One needs dreams...

I would be remiss if I failed to mention Ant. Which is also not IBM
i-aware. It is also very, very flexible, which means it is not easy for
beginners to grok.

--buck
--
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.