Source Migration of DSPF

[johnstagliano]

I am hoping for a recommendation with the following...

I am preparing a process to migrate our source from Source Files / Members to git, local development, deployed to IFS and Compiled with IBMi Bob. Most of our developers are still using PDM and SDA and some are resistant to change. I have the support of IT Leadership; therefore, we are moving forward with change.

Now, I am struggling with what to do with Screen formats, menus, and Print Files. If I leave them in Source Files/Members, we will not get the benefit of using git for code management, deployment, etc. If I migrate them with our RPG source, we lose development via sda / rlu.

I know there are other VS Code extensions for screen development (Christian Larsen's and Craig Pelkie's), but, they are not really a replacement.

My question... Do you all have any recommendations for this migration process.

• Should we wait for an official replacement for SDA and RLU before we migrate screen formats, menus, and printer files?
  -- If we wait to migrate, our source code repository will be incomplete.
  -- This delay will cause complexity to our plan for automating deployment to our staging and productions environments.
• Should we migrate our screen formats, menus, and print files knowing we don't have a good replacement for SDA & RLU?
  -- If we don't wait to migrate, screen format, menu, and print file development will be more difficult.
• What is the ETA of the official VS Code replacement for SDA?
  -- Knowing an ETA might help us determine when to migrate Screen formats, menus, and printer files.
  -- Spring 2026? Summer 2026? Fall 2026? 2026?

I really appreciate all the efforts you all are putting into VS Code. It's a great tool and the answer to what I have wanted to do with our development process for many years.

I am looking for some honest opinions of how to manage screen formats, menus, and printer files.

Thank you!

[johnstagliano]

@worksofliam
I know you probably get asked this question a lot...

I am planning to start migrating source code and changing our development process to use VS Code, git, local development, deployed to the IFS, and TOBi.

Having an eta for the screen designer will help us with the timing of when to migrate Screen formats, menus, and printer files. Without knowing an eta, I don't know what to plan. Do I wait until I am forced to change because we upgrade our OS? Do I migrate and use an alternative extension until the official one is ready? Do I need at least 1 copy of RDI?

Therefore, I will ask the question again...
Is there an ETA of the official VS Code replacement for SDA?
-- Spring 2026? Summer 2026? Fall 2026? 2026?

I also asked these questions in the "Help build the designer with your contributions!" discussion a couple months ago and did not receive a single response.