geez... our vendor broke their API call. Instead of requiring a date yyyymmdd, they now require a date/time yyyymmddhhmmss. Unfortunately, there was zero warning that this was coming, so I don't think that it was intentional - especially since it's taken them >2 weeks to identify the problem.
They're updating their API site to PHP7, so I wonder if it's a PHP thing...
Editor progress: I added a Rubberduck.Parsing project to the solution, and added a simple parser off the main grammar, that works off a TextReader stream from the TextDocument in the editor... and now whenever the text changes and remains unchanged for a configurable number of seconds, the module gets a quick parse and the VM gets an IParseTree... nothing else, just the tree.
2
From there I can update the list of members in the dropdowns, and the base ParserContext class has StartOffset and EndOffset lined up with the document.
Later we can just grab the parse trees from the editor VMs for the full processing (resolution, inspections, etc.)
The parser doesn't handle syntax errors yet - that's next, I think. We're getting these red squiggles!
VBA Rubberducking
VBA Rubberducking