This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Power Systems Development - RDi team
Is there any plan of IBM, in which version of RDi this feature will be implemented?
The CAAC has reviewed this Idea and recommends that IBM view this as a high priority requirement that is important to be addressed. For RDi to remain viable as an IDE, it must be updated -- if eclipse were more up-to-date, it could be used for multi-language development.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual Ideas on the broader IBM i community, and has therefore reviewed your Idea.
For more information about CAAC, see www.common.org/caac
Nancy Uthke-Schmucki - CAAC Program Manager
Does IBM have an idea in which Version of RDi this requirment will be included?
RDi can't be installed on Windows 11 for ARM.
It was extremely hard to install it on Mac OS BigSur (after several hours of try and error and only after contact with IBM 2nd Level support).
IBM please realize that we have 2022 and update your product. It is not only annoying that this happens. It is also a very important step into the future of developing for IBM I because Developers who come from other languages / frameworks with other tools like Visual Studio or Visual Studio Code (or even modern eclipse) won't stay long when they have to work with this old software.
If they can't install it they won't use it at all and switch the job to a company without RPG... that is my experience in real life for many years now.
So modernizing RDi is not only important for existing customers who paid for it.
Any updates on this?
This will likely reduce the complexity of getting RDI 9.6 to work correctly on osx. Something I have been working on for the last several days.
The CEAC has reviewed this requirement and recommends that IBM view this as a HIGH priority requirement that is important to address.
RDi needs to be able to support the latest version of Eclipse to enable using the latest plugins available.
Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.
To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT
Therese Eaton – CEAC Program Manager, IBM
Thank you for considering the update.
Even if this update is not committed to the upcoming version, it would be nice if you could look at the API removal strategy of the Eclipse Platform.
Specifically, the following deprecated API's are REMOVED since Eclipse 4.17 [1] and break the installation of RDi in newer Eclipse versions. Please consider removing the usage of the REMOVED API for the next maintenance release. This will allow the adventurous to upgrade and provide you with valuable feedback like this.
Removed APIs in the Eclipse 4.17 release:
Remove Input and MInputPart
Removed org.eclipse.core.runtime.Platform#getJobManager()
Removed JFace and JFace text Assert
[1] https://www.eclipse.org/eclipse/development/porting/eclipse_4_17_porting_guide.html
We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.
Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.