Use Glutinum to generate bindings for VS Code

[NatElkins]

Session on Use Glutinum to generate bindings for VS Code

Nat Elkins, from NELKNET in Eastern (NYC) would like to tackle: https://github.com/glutinum-org/cli/issues/152 https://github.com/glutinum-org/cli/issues/153 https://github.com/glutinum-org/cli/issues/154

Extra

I am trying to bring .NET debugging to VS Code fork IDEs like Cursor and Windsurfer (among others). The Microsoft .NET debugger is licensed to only work in VS Code though. There is an alternative debugger, https://github.com/Samsung/netcoredbg which I got working in Cursor. But it's kind of a pain to use since you need to build it on your machine, or set up a custom kind of launch.json config, etc. I want to have an extension I can just install that will install and use the correct debugging package. And I want to write that extension in F# using Fable. I know there are some existing helpers for VS Code here (https://github.com/ionide/ionide-vscode-helpers) but they're somewhat outdated and Glutinum is allegedly the more up-to-date way of generating bindings. That's what led me down the route of trying to get Glutinum to generate VS Code bindings.

[nojaf]

Hello, thank you for your interest!

We had a session with Maxime at https://amplifyingfsharp.io/sessions/2024/01/19/ a while ago. This leads me to wonder: why is there a need for a new session? It seems like you might be moving a bit quickly here.

You opened Glutinum issues and then shortly after submitted this request. It's unclear where you're encountering difficulties. Have you tried addressing these issues? If so, why not ask Maxime for advice when you hit a roadblock? So far, I haven’t seen any conversation between you and Maxime, which makes it feel like you’re seeking a session without first putting in the effort to contribute.

What I want to convey is that there are simpler steps you can take to make progress. What’s holding you back from diving into the code or reaching out to Maxime?

[NatElkins]

That's fair, I haven't put more than a few hours into it. I can (and will!) put a bit more time in. I submitted this session since it seemed to me that it's something the community probably desires. In the Amplifying F# session with Maxime he even notes that one of his original motivations for Glutinum was the creation of VS Code bindings. And it's something that Ionide might benefit from as well.

I see Glutinum as a critical piece of the Fable/F# ecosystem and making the development of Fable apps seamless. Although there already was a session on it, I think a session with a newbie (yours truly) and trying to fix another issue would still be useful to the community. But your points make a lot of sense, and I will certainly work to progress independently on this as well.

[nojaf]

I submitted this session since it seemed to me that it's something the community probably desires.

I don't want to be mean, but community interest hasn't really spiked here:

Nor has the number of contributors:

https://github.com/glutinum-org/cli/graphs/contributors

These metrics are not a reason to avoid having a session; however, I find the sudden leap to amplifying F# a bit jarring. The first steps in contributing here involve understanding how the codebase works (which we have already covered) and attempting a draft PR. If you encounter difficulties with that draft PR, feel free to ask the maintainers for advice. However, jumping straight to a streamed session seems premature.

The key to contributing is to take action. Start with small steps, show your effort, and don’t hesitate to ask for help when you’re stuck. I’m sure Maxime would be happy to hop on a one-on-one call if you ask him politely.