VBA Rubberducking

« first day (3047 days earlier) ← previous day next day → last day (133 days later) »

Duga

00:05

REFRESH!

[Minesweeper] 130 Games Played. 86 Bombs Used. 19014 Moves Performed. 12 New Users

Duga

00:37

[rubberduck-vba/Rubberduck] 0O7UMXiu5hxujBzw starred us

3 hours later…

Duga

03:21

[rubberduck-vba/Rubberduck] Lx created comment on issue #6006: Microsoft .NET Framework : Unhandled exception as occured

> I'm getting a very similar intermittent error with a slightly different source. I then have to kill Excel via the Task Manager as it's still running in a hidden state and prevents reloading of a "visible" copy.

- Version 2.5.2.5906
- OS: Microsoft Windows NT 10.0.22000.0, x64
- Host Product: Microsoft Office x64
- Host Version: 16.0.15629.20156
- Host Executable: EXCEL.EXE

```text
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dia

15 hours later…

Greedo

18:30

Ooops was just testing the upload button didn't think it would send

Anyway, with all this RDv3 talk I was just thinking about some high level architecture of how all the bits could fit together. You can see I made a diagram of it gist, editable version in graphviz

Basically I'm very keen to get RD's capabilities to escape the host app. Microsoft's "Language Server Protocol" (LSP) has been mentioned seems to do a good job. Implementation-wise, RD would provide an LSP "Tool" interface to the VBE - capturing changes to the code, user events etc. There would then be an out-of-process LSP "Server" that actually parses the code, publishes diagnostics to the tool, even refactorings/changes to the source code.

THE diagram is work in progress btw, you can edit it yourself in that link which will always point to the latest version of the gist containing the graph source code

It would be great also to have the ability to run RD's static code analysis on strings/vba files passed in by a continuous integration service. E.g. I modify a file in Excel and sync it to the filesystem. I git commit which runs my pre-commit hooks. Those hooks call a tB exe that runs RD to ensure my code has no warnings before committing. It also auto-formats using the indenter. Finally, a custom script uses the RD tokeniser to add line continuations automatically.

Once happy I commit the code. I then re-sync the changed files in Excel. Maybe RD-tool in Excel has a file-system watcher so all the syncing to and from the filesystem is done automatically.

BZngr

19:36

@Greedo This is awesome. I too have been trying to wrap my head around the RDv3 descriptions and how it might be organized (with little success). Thanks for sharing.

Mathieu Guindon

20:25

woah what happened here?

quite the jump in that 8-hour span!

Mathieu Guindon

20:37

in other news, last Rubberduck release has passed 22K downloads

Greedo

21:22

@BZngr thanks:) this is just my theoretical "dream" architecture that would support some of the features I personally think are important. Need some sanity checking what's even feasible though

@MathieuGuindon any initial thoughts on that architecture? I've missed out unit testing because it made the graph more messy so I wanted to see if this is worth sketching out further before adding it?

Anyone else thoughts too ofc - you can play with the graph if you want is quite an easy to use online editor in the link