I've been working with the RDi plug-in for a few months now and find it quite useful ... that said, I do have a few recommendations for improvements.
- Move (or copy) the create object / compile option from the Team submenu, when you right click on an item in the RSE tree, to the top level. Strictly speaking, compile isn't a change control function and it's probably the most frequently used.
- Add an option to the popup menu to set the RDi connection jobs library list to the library list that would be used to compile the member. This will allow the outline view to find copy members. I currently have a command defined in RSE that runs ACMSLIBL to set the library list, but I have to define multiple commands and run the one that is appropriate for the program I'm working on.
- Avoid running operations on the Eclipse UI thread, as it causes RDi to lock up (even if only briefly). Spawn new threads or use the Eclipses job functionality. This applies to opening source members & saving dirty editors. I struggled with this issue in the past, as I developed the RDi integration for PTC Implementer in a past life.
- Add a new type of filter that will show tasks (based on criteria) and all the members associated with that task ... something to the effect of:
RDOi+ Tasks+ + XXX-1234+ + + PGM1.pgm.rpgle ...+ + + PGM2.pgm.rpgle ...+ + XXX-9876+ + + PGMA.srvpgm.rpgle...+ + + BD1.bnddir...
------------------------------
David Gibbs
Sr. Software Developer - Worldpac
Owner / Operator - midrange.com
------------------------------