search

softwareCobbler / luceedebug

line debugger for lucee
GNU Lesser General Public License v2.1
45 stars 15 forks source link

Support for Other IDEs? #9

Open jamiejackson opened 1 year ago

jamiejackson commented 1 year ago

Lots of questions, since I've wanted an IDE-based step debugger for CFML for almost a quarter of a century now...

What made you choose VS Code as the IDE for luceedebug? Was it a personal preference for VS Code? Is VS Code inherently friendlier to CFML debugging than other IDEs?

Having an agent-based step debugger for Lucee in an IDE (VS Code) is going to be a game changer for me, versus the web app solutions (FusionReactor, coldbug) but I'll have to bounce around between my preferred IDE (IntelliJ) and VS Code in order to do step debugging. (Or I can obviously switch completely to VS Code, but I already tried them both a while back and landed on IntelliJ.)

softwareCobbler commented 1 year ago

There's nothing really strongly tying this to VS Code. The important part is the Java agent that hooks into Lucee internals, but its interface to/from the outside world is via DAP. I'd imagine other IDEs have similar (or in some cases exactly DAP) debugging interfaces.

jamiejackson commented 1 year ago

Thanks for the DAP pointer. It might end up being a hurdle for IntelliJ, but I posted a feeler on the topic.