Framework for modular commands collection

[schoeller]

Thanks for PyRx.
Consider myself as a user who would like to write ye ol' script over the time of different project designs in order to ease workflows. This would mean I'd write command script by script without designing a global architecture but rather being driven by project needs. Thus my perspective does not dispose over the insight an experienced developer has.

Once the collection seems useful one might expose it on a public repo for others to use. Required is then to also document the usage of commands.

Undertaking my first steps I had once started out with BRXSDK, but I do not consider this being modular enough, since one has to update on several occasions once a new command is added.

What would be a useful modular setup to thrive for?

[CEXT-Dan]

In C++, I keep all my commands in one file. Usually, the commands don’t have any implementation, they are just used to forward the call to another function or class. Usually, the file is named acrxEntryPoint, the layout is almost exactly like the template. After that I usually break out the reusable stuff into their own files. Spaghetti code is almost always inevitable, I just try to minimize it.

Over the years, the stuff I drag around the most is jigs, I have a DragJig, RotateJig, ScaleJig and a DrawJig that are always handy

[schoeller]

Thanks for sharing.
Originally I was thinking of python script structure. Maybe one though also should keep it monolithic as you pointed out. Even shifting helper functions somewhere else would not make sense as long as one only sporadically manages it.

[schoeller]

Just stumbled over the sample by @gswifort and take this as an answer.