For all the folks interested in The Adobe ColdFusi...
# adobe
m
For all the folks interested in The Adobe ColdFusion Builder for VS Code extension (phew, what a name) make SURE you sign up for Dev Week and watch Ketki & Nikhil (two of the vast team of engineers that worked on it) give you the low-down: https://adobe-coldfusion-devweek-2022.attendease.com/registration/form
👍 3
metal 1
🤘 1
s
As a VS Code user, I'm interested enough in seeing the new CF builder that I've registered 🙂 First CF event I've registered for in many, many years!
❤️ 2
m
I'm really excited for it. I had 3 demos last week to cover all the features (all over an hour each) and I saw it do things I didn't think it possible for VS Code to do.
s
@Mark Takata (Adobe) I'll remain skeptical until I see it: I'm used to some pretty amazing functionality in VS Code, via a combination of LSP, and complete scriptability of VS Code itself via a Clojure REPL (the Joyride extension). Plus I have a data visualizer directly in VS Code (another extension).
With the tooling I have already, I can do things like query a database, display the results in VS Code and navigate through the foreign keys into other tables.
And that's all based on OSS stuff, written by a handful of people, so I'll be very interested to see what the full might of Adobe's development team can bring to bear after all this time 🙂
m
OK, well you might be a touch more jaded than I lol. But I think you'll still like it.
👍🏻 1
g
Surely Adobe wouldn't waste their time on query tools ?
I'm also curious, how did Adobe gather information about what was critical or how the general community feel about what features are being included? Hopefully not too tied to the box ecosystem...
Just because it's free, doesn't mean people will use it, we have 10+ Devs still using sublime text
s
@Gareth My guess is that it will leverage RDS and require an ACF server for some stuff based on past CF Builder incarnations, but I think they did say at some point they were implementing LSP (Language Server Protocol) which allows for a lot of very cool in-editor code insight and provides support for refactoring, finding uses and definitions of symbols etc.
I have no idea whom they've asked about this in terms of community -- maybe there will be a prerelease program for it after DevWeek and we can sign up and provide feedback that way? But it seems like Adobe has been leveraging the prerelease programs less and less over the last few releases, compared to the length PR programs of old...
I'm looking forward to the sneak peek -- as I'm a heavy VS Code user.
g
LSP only really works well if you can define rules with annotations / comments, or if indexing is a bit more generic, sublime does this well
Oh, and linters, right ? Couldn't live without cflint or an equivalent
m
OK so I'm 2 margaritas in and its Friday night, but let me see if I can answer some of these: 1. Features. Basically this is a port of the Builder product to VS Code. That spec was, unfortunately, in place and far too along for me to have even a little bit of say in it. If the feature was in Builder, you're almost assured of seeing it in VS Code. 2. We're using a language server. 3. We're supporting RDS. 4. It is not reliant on Box products. Not at all, there's no integration there. Box is not an Adobe product, so we're not integrating into their functionalities. 5. To utilize this extension to the max you WILL need to be running a modern version of ACF. Can you use it with other CFML? Sure. But some of the stuff won't work. 6. There's no public prerelease. We're getting it out asap just so we can have as many people using it as possible. It is free so hopefully it will get a lot of use and feedback will continue to improve it, fix bugs, etc. 7. Query tools. We have connectors to DBs just the same as we did in Builder. You can hook up to the datasources you have set up on your server, see the structures, etc. Its neat. Hopefully that covers it. I'm gonna go watch a silly movie. Have a great weekend all!
s
1. Sorry (but parity with Builder is a reasonable goal). 2. Good. I'll be very interested to see what this brings. 3. Don't care (but "of course" on good ol' RDS 🙂 ) 4. See #3 ("of course") 5. Figured. It will be interesting to see what features depend on what 🙂 6. Free is good. And no prerelease is fine given #1. 7. Cool 🙂 Enjoy your movie and margs!
❤️ 1
d
Any further updates on this? I'd try it if I could (long-time IntelliJ user).
m
Super close. I know I keep saying that, but this is a daily thing i'm grinding away at. VS Code recently made a change that broke the heck out of one of our main features, and that's being worked on right now (but I literally just got a build that says it fixes the issue, so I'm going to be installing that and testing this afternoon). Well low likelihood folks will see this in their hands prior to the Dev Week talk, but the world is a weird place so who knows?
👍 1
d
Will RDS be required if all project files are on a network drive (\\someserver\some\path\)?
m
I'm not sure which of the features rely on RDS. I know RDS is required for the dataview features.
l
Hey Mark is there a link to where you can download/join the beta VS Code plugin?
p
@larryclyons currently it is not available in public. It is in private beta for testing.
@Dave Merrill RDS is not required for accessing the file system. it is mostly required for Datasource view and dataview as @Mark Takata (Adobe) mentioned.
l
@priyank_adobe Thanks for the feedback. Actually I was also requesting where I could join the beta.
p
Let me check and get back to you.
l
👍
m
Larry, the entry for the beta is currently closed. The launch of the publicly available product is coming soon. Thank you for your patience, you're going to like the VS Code extension.
p
Thanks Mark