BEAUti beast.app.draw.InputEditor dependency

[rbouckaert]

BEAUti discovers input editors by scanning the beast.app.draw.InputEditor packages (for efficiency), which means every package that wants to provide an input editor needs to use that name space, preventing adoption of modules (#834). This should be relaxed to include any package. For performance reasons, we should probably cache results in beauti.properties, and only refresh when new packages are installed.

[alexeid]

There are many design alternatives to this surely? Just statically registering your class in some util package would be an obvious and easy pattern...

On 3/08/2020, at 7:22 PM, Remco Bouckaert [email protected] wrote:

BEAUti discovers input editors by scanning the beast.app.draw.InputEditor packages (for efficiency), which means every package that wants to provide an input editor needs to use that name space, preventing adoption of modules (#834 https://github.com/CompEvol/beast2/issues/834). This should be relaxed to include any package. For performance reasons, we should probably cache results in beauti.properties, and only refresh when new packages are installed.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CompEvol/beast2/issues/911, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAG5MSLPVJT2XIRNI3JBVYDR6ZQSDANCNFSM4PTBNY3A.