Rubberduck aims to improve every aspect of the VBE, to bring the developer experience for Visual Basic up to 21st century standards.
Often, this means providing better versions of existing toolwindows, for example the Code Explorer which encompasses most of the functionality of the (built-in) Project Explorer, whilst also massively extending it.
Before users can feel comfortable replacing built-in toolwindows, ours have to do everything they can, just better. This project aims to track issues which highlight any shortfalls. It also tracks requests for replacement functionality we haven't yet begun to tackle.
No description
With PR #3716, we are now able to gain much more metadata about VBA projects than we could originally. However, it's not enough to just have the API - we need to start implementing the API in various parts of the Rubberduck to put the API to use. The project is dedicated to tracking issues where we need to update Rubberduck's code to leverage the new API. At a high level:
- Improve the resolution of types defined within VBA-hosted classes (notably user forms and document classes)
- Parse the locked VBA projects that are referenced using the type information.
- Use new features such as ability to silently compile projects prior to parsing or obtain reference metadata.
Any issues that can be resolved by the new API should be tracked by this project.
This is a tough issue where we need to root down deeply into the COM interop. There has been intermittent reports of crashing on the exit, as well as possibly related case where Rubberduck add-in cannot be unloaded then reloaded in the same session without breaking everything. Several attempts has been done on to manage and we've succeeded at reducing the incidents. The project is dedicated to putting this punk away forever.
This projects lists all bugs that needs to be tracked and eventually fixed. We have to manually add any new bug reports to the project but once added, those will be automated for tracking and closing via referencing pull requests. Help us smash those bugs!
This project is aimed at providing a cohesive overview of the current status for the "we need to get this done next".
The current epic is the "Extract Method"-Refactoring, that's irritatingly complex and one of the best showcases where Rubberduck can prove it's worth to a professional audience
The file VBE7INTL.DLL contains the following:
STRINGTABLE
LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US
{
18080, "Tile Horizontally"
18081, "Tile Vertically"
18082, "Arrange Icons"
18083, "Microsoft Visual Basic for Applications Help Topics"
18084, "Search Reference Index..."
18085, "Obtaining Technical Support"
18088, "About Microsoft Visual Basic for Applications..."
18089, "Long Live the Cucumber"
18090, "Break On All"
18091, "Break In Ole Server"
18092, "Break On Unhandled"
}
So, long live the cucumber. This project is intended to organize long-standing and long-running issues that should be adressed sooner or later. Currently this applies to [label:technical-debt] issues and issues pertaining to the 3.0 architecture