Code for IBM i and its RPGLE language tools have come a long way! I am excited to share some of the language tools improvements with you today. They are absolutely worth talking about. Language tools are what makes writing code fun and exciting, and we can be better developers with them.
With our latest version of Code for IBM i, developers have access to virtually everything they need when writing both RPG and open source applications, all in a single editor.
Version 0.8.4 provides your choice of a 5250 terminal or a PASE shell right in the editor—with a new, faster launch process.
A great IDE contains features that increase your coding speed and accuracy so you can focus on your program’s logic. One of my favorite productivity enhancers, content assist, has been bundled in Visual Studio Code for IBM i since its inception. Content assist gives you autocomplete options for code as you write it, reducing syntax errors.
Today we’re announcing a new killer productivity tool for Code for IBM i—a built-in linter!
Git has become the de facto standard for open source version control. Nevertheless, while your team may be using Git for open source code, your traditional IBM i programs and other code may use no version control at all, or be stuck in a repository that is difficult to access.
In this article, we’ll cover why you might want to move code to Git and suggest tools that make the move practical for IBM i teams.
Visual Studio Code is a widely used IDE in the non-IBM i world. Recently we released Code for IBM i, a freely available extension for VS Code that supports RPGLE and COBOL development for IBM i. You can read about the basics of Code for IBM i and about code coverage functionality in my previous posts.
Today I’m going to cover three additional tips for using Code for IBM i. Of course, for any of this to work, you need to install Code for IBM i.
Visual Studio Code is an IDE and platform for developers to write backend, progressive web apps, frontend, and everything on the spectrum of development. I have created an extension for VS Code, called Code for IBM i, that allows users to work on and maintain their IBM i code. VS Code is the best IDE for extensibility, which is why I wanted to take on such a task.
While Visual Studio Code was built to work with all languages, in my opinion it didn’t have much support for RPGLE or COBOL on IBM i until this point. We’re streamlining RPGLE development in terms of tools and speed for our users. We want to make developing RPGLE and COBOL easy for everyone in the most efficient way possible.
If you’re using Rational Developer for i (RDi) for most of your development tasks, you might want to use it for PHP, too. RDi is based on Eclipse, so we can use the Eclipse PHP Development Tools (PDT) with RDi.
However, there are some additional steps to take and quirks to be aware of. This post provides the steps for a trouble-free installation of PDT, with tips to resolve common issues.
IBM i integration via APIs has been central to many of our development projects, especially those involving web/mobile applications, software-as-a-service (SaaS) solutions, and cross-platform data sharing.
Lately we’ve been helping customers prepare for new state sales tax rules on internet sales by integrating APIs with their IBM i systems.