New Module Developement

[ranous]

I have ideas for a couple modules I'd like to write. Looking at allsky-modules code, I noticed there is a v2025.xx.xx branch and the modules are done a little bit different by being classes and inheriting from an ALLSKYMODULEBASE class. I'm assuming this branch is designed to work with the same named branch in the allsky repository. What's the state of the new stuff? Since I'm starting anew, I'd just do it the new way. Are you close to releasing this? I'll do it the old way if this new stuff is still getting lots of changes or not stable yet.

Alex

[Alex-developer]

@ranous

Well spotted :-)

I would use the new format in the v2025.xx.xx branch, we are in the final stages of bug fixing and testing

The current system is 100% compatible with the new as well, so if you write the module using the current system it will work in the new system as well.

The new system provides a lot of helper functions to make life easier, like getting params for the modules.

Look forward to seeing the new modules

Alex

[EricClaeys]

@ranous,

I agree with Alex. v2025.xx.xx is pretty stable so I'd go with it.

To use it, do a normal upgrade EXCEPT use git clone --branch v2025.xx.xx ... instead of the regular "git clone ...".

Eric