Describe the problem
Currently there are events everywhere, usually in the package they were created in to serve a related class.
It becomes nearly impossible to work out what events exist and what might be related to what you are working on.
This creates a bad user experience and extra work when a release goes out and someone complains that X isn't showing what it should.
The improvement you'd like to see
Bring all existing events used by MapToolEventBus into one package where they will be easy to find and determine their relevance to a current project.
Alternately, add a common interface that can be applied to event classes. Coders can then search for implementations to find them all.
Expected Benefits
Better experience for the user, the coder, and less hasty fixes post-release.
Additional Context
No response
Describe the problem
Currently there are events everywhere, usually in the package they were created in to serve a related class.
It becomes nearly impossible to work out what events exist and what might be related to what you are working on.
This creates a bad user experience and extra work when a release goes out and someone complains that X isn't showing what it should.
The improvement you'd like to see
Bring all existing events used by MapToolEventBus into one package where they will be easy to find and determine their relevance to a current project.
Alternately, add a common interface that can be applied to event classes. Coders can then search for implementations to find them all.
Expected Benefits
Better experience for the user, the coder, and less hasty fixes post-release.
Additional Context
No response