Day 7 of the 12 Days of BoxLang: Meet the BoxLang IDE

The official BoxLang IDE extension delivers a complete, modern development experience with IntelliSense, debugging, integrated tools, and AI-powered assistance — all inside VS Code and compatible editors. Whether you’re building new apps or migrating from CFML, everything you need is in one place.

:point_right: Read more:

BoxLang #12DaysOfBoxLang #DeveloperExperience #VSCode #IDE #ModernDevelopment

Hi Victor

Does this extension have any CFML capabilities?
Or is this a just Boxlang extension?
I think the reality is, that the vast majority of us, are still working on legacy Coldfusion apps, and we will be doing so, for many years to come. It took 20 years to build our Coldfusion app, and would take a similar amount of time to convert it, so I will be developing in CFML, for the forseable future.

I mean I see you offer:

  1. Transpile CFML → BoxLang using the official transpiler

But we have at least 250,000 lines of code, to deal with, that goes back to 2001, so there are a lot of custom tags etc.
What size of codebase, has your transpiler been tested on?

Hello @MrKodama

Our module supports both. We have cfml projects, hybrid projects and pure BoxLang projects. So our intent is to support cfml as much as our clients still use it.

Obviously, some features are BoxLang only. However, our intent is to support you in all capacities.

1 Like

I forgot to answer this. Our transpiler is incredibly fast and multi threaded. So go for it. It should be able to process it. You can also test with our compiler directly. This will tell you if your code has compilation issues.

1 Like

OK. I will give it a go.
It is a very bespoke legacy framework created back in 2000. With lots of custom tag use, rather than CFC. So, it will be interesting to see what happens!

@MrKodama Like Luis said, our VSCode 100% supports CFML code! It’s a fork of the popular KammassammaK extension. So yes, you can totally use our extension. And since BoxLang runs CFML, you can switch to BoxLang today to run your code and then slowly work your way over to using BoxLang source in the future to tap into the new features.

I like to chime in on threads like this where new folks are considering working with Ortus products. We were in the same spot you are today 3-4 years ago. Getting started down this path is work but we’ve found it to be well worth the effort, particularly as we’ve added more programmers. We’ve cut over most of our public facing systems to ColdBox at this point. There is a heck of a lot of old legacy code still executing under the hood. As time permits, we upgrade old code. The good news is it all keeps right on running. BoxLang is in the not-too-distant future for us. The only thing holding us back is too much work that has to be done yesterday.

2 Likes