curious, who’s still around thats been doing CF fo...
# cfml-general
g
curious, who’s still around thats been doing CF for a while ?
r
Not me, I'm not here.
g
hi Rich, are you building websites, or apps? and how long have you been using CF ?
r
Since the Allaire CF4 days. 1998/1999. Big apps and gov work.
g
yeah, nice, I’ve been in it since around 2003
what editor are you using ?
r
These days, VS Code.
g
Adobe’s extension? or one of the opensource ones ?
r
KamasamaK, just for syntax highlighting really. Don't need anything more.
g
how do you find it?
do you use the remote CFdocs or local ?
r
On the regular occurrence that I can't remember which way around the arguments in datecompare() work, I invariably end up on the Adobe site documentation.
g
because the help in vscode doesn’t work ?
do you know KamasamaK ?
r
Dunno, never bother with the in-app help. I really don't find myself referring to it very much. It's really just datecompare(). I'm pretty much cool with everything else. I have no idea who KamasamaK is? Now you're making me wonder if I should.
g
lol, trying to drum up a little interest in my fork of the project, trying to iron out a couple of the small annoying bugs
r
I'll take a look!
r
Hey, been using CF since 1996. I use the cfml extension by KamasamaK as well using local cfdocs. I'm interested in your cfmleditor extension, especially if you get documentation and signature help for member functions to work.
r
does 2014 count?
d
Using CF since 1992. I use cfdocs.org fairly often, adobe docs occasionally. I use IntelliJ IDEA almost all the time. Anything else you'd like to know?
m
What's "a while"? I started in 2009...
s
I started when Macromedia bought Allaire and we got access internally to early builds of what became CFMX6 so... 2001-ish? I still maintain one small CFML app at work but we've rewritten almost everything else at this point. As for editing: VS Code with the K..K extension (and I don't use the Adobe product, just Lucee running on CommandBox, so a lot of Adobe's extension is useless to me). Also, my dev env is Windows + WSL2 which, last I checked, Adobe's extension doesn't even support.
c
I started around 2001 or 2002. Currently use VSCode with KamasamaK's extension (have done almost since VSCode and that extension were first available). Strictly Adobe CF for production (a tiny bit of Lucee for personal pet projects).
q
I've been using CF since about 1997. I use IntelliJ as my IDE, and cfdocs.org as my reference (although IntelliJ does a pretty good job of keeping up with function properties, etc)
g
I'm not as old school. I started around 2007. Good times.
t
I also started around 2006
👍 1
b
started around 1999 using 4.0. I now use VSCode and sometimes Dreamweaver (long story, but i hate it)
😢 1
c
I started with Allaire Cold Fusion 4.5 and Notepad, then CF Studio (I think that was what it was called), then Dreamweaver, tried CFEclipse, used CFBuilder for a while, then jumped on VSCode when the community CF extension was available.
s
Installed your cfmleditor extension @Gareth -- all looks good so far!
m
I started in 2000. I am mostly using vscode, but I still sneak open Homesite from time to time because it's so quick and painless.
g
Not planning anything game changing for the new fork of this extension and I welcome any contributors
👍🏻 1
j
Since 1999 - ColdFusion ( 4 / 4.5 ) - Using VS Code with CFML from KamasamaK.
@Gareth what are the things that your fork irons out?
g
Improves stability of cfdocs integration with use of fetch APIs, reduces a crash associated with function completion, support for use of the plugin with the web version of vscode.dev
👍 2
New setting for scope case, thanks to another contributor
Hoping to reduce dependence of local cfdocs
s
support for use of the plugin with the web version of vscode.dev
Nice! Does that mean it might work in GitHub CodeSpaces too?
g
Sean, as long as you don't want linting
👍🏻 1
Trying to get my head around some work being done for a language server by another community member that might add some stuff as well, but no promises
Pretty sure codespaces is a VM of some kind, vscode.dev is web based how ever
Codespaces is also not entirely free
s
Casual usage of Codespaces is free up to a fairly generous limit -- 120 core-hours of Codespaces compute per developer -- but, yeah, running the VMs for a long time could tip you into paid territory. It provides a VS Code web UI for editing on the VM -- which means you can run the code / connect from the editor / use terminals / etc. Some pretty sophisticated plugin setups work in Codespaces. Example: https://github.com/seancorfield/usermanager-example?tab=readme-ov-file#quickstart-via-devcontainers-or-github-codespaces -- this uses a Docker image with a bunch of tooling in it, and from the web editor you can start up the web application and browse it, as well as connect editor to the running program and modify it while it's running.
j
Awesome @Gareth, I will go ahead and install yours to try it out!