@Mark Takata (Adobe) whats happening with the VSCode plugin ?

I know I sound like a broken record, but it is really close. I've had 2 long demos of it this week, with one more left. It looks really, really good. I'm using the latest build for all my demos, and its like... right there. There's like, one dumb bug that's probably already been fixed. Look for at least one deep dive engineering talk about VS Code during Developer Week (and I'm pushing for 2 talks because, frankly, an hour isn't enough time to cover everything this tool does). I'm trying so hard not to oversell it here, but I honestly think this is going to become the number 1 CFML IDE tool everyone uses.

I know in that other thread Adam had mentioned that it would be good to have community testing before its release. Is that something being discussed? (And if so, any chance I could get in on a closed beta? 😉)

Major CF releases get that, so it would be nice. Or at least there should be a good place to provide feedback/requests that isn't pinging Mark. For instance, LSP 3.17.0 was just released last week, and I'm assuming none of those new features would make the initial release.

Naw - Mark loves it when we bug him on slack 😂

I mean, it is kind of literally my job.

message has been deleted

Hey man, for all the grief and garbage I get tossed my way, the love I get more than makes up for it. The DMs I get with love and support are basically keeping me going. 🙂

I guess my point was mostly that Slack and a single-person bottleneck is not an ideal feedback mechanism. At least the bug tracker better be ready for the new product at launch. Although it's not like I've always had good experiences with that thing. 😅

Yeah... the bug tracker is kind of a black eye that has "politics" written all over it

I've only been involved in two, but I've found the pre-release product forums to be quite useful, though.

I feel like a pre-release test group would also make a lot of sense. Not just because I'm really intrigued, but also because there are a ton of ways people use an IDE and there's no way all the use cases will be well tested.

I mean, like, since this is a free release anyhow and we'll almost certainly be doing updates and bugfixes anyhow, just getting it into the extensions store asap actually might make some sense at this point. Its pretty much the Google Gmail model. And the extension really is quite good already, so I think it might help find those edge cases, vs just making sure it works. Spoiler alert: It works. 🙂

If you can convince anyone that needs convincing to let you add it, I'd love to get away from Eclipse provide early feedback 😄

Do you know if the language server or debug adapter will be available separately as well in case someone wanted to use them with another client? I know they wouldn't have all the features of the VS Code extension, but that might be fine for some people.

MT, I think the short answer is "no", but the longer answer is "people will probably figure out how to leverage it for use in other IDEs". I can tell you for sure we're not gonna actively support that, but once it is downloaded and you're using it someplace, I mean, not much we can do to stop you, you know? That said, you can absolutely expect the vast majority of the really, really cool stuff won't work elsewhere. Server control, debugging, etc. All that is built for use in VS Code, and I think it would take an incredible amount of work by someone to make any of it work elsewhere. Never gonna say never though, y'all are clever 🙂

I wouldn't expect server control, but debugging should be able to work elsewhere if it uses a debug adapter that conforms to the Debug Adapter Protocol -- that's the purpose of it.

Does the Language server rely on an instance of CF ? Its a bit of a shame there isn't some kind of prerelease, I know various CF plugins haven't worked well for us due to the scale of some of our products.